Phase 6: Future-Proofing & Recovery

A senior System Administrator looks ahead. They evaluate current system trends to predict when resources will run out (Capacity Planning) and architect scaling solutions. Furthermore, they are the last line of defense during a disaster, responsible for bringing the business back online by performing complex system restores.

System Administrator: Phase 6 Guide

J.63SAM00.024.1

Evaluating System for Future Development

Detailed Explanation: This competency involves Capacity Planning and lifecycle management. By analyzing the monitoring data gathered in Phase 5, the administrator predicts when the server will hit 100% capacity. They must then propose a scaling strategy: Scaling Up (adding more RAM/CPU to an existing server) or Scaling Out (adding more servers to a Load Balancer pool).

Figure: Scaling Strategies (Scale Up vs. Scale Out)

Vertical Scaling (Scale Up) 4GB RAM 2 CPUs 16GB RAM 8 CPUs UPGRADE Horizontal Scaling (Scale Out) Server 1 Server 2 Server 3 Load Balancer ADD NODE
J.63SAM00.025.2

Performing System Restore

Detailed Explanation: Backups are worthless if they cannot be restored. System administrators must regularly test Disaster Recovery (DR) procedures. A system restore might involve recovering accidentally deleted files, rebuilding a corrupted database from a SQL dump, or rolling back a virtual machine to an earlier snapshot to meet the company's Recovery Time Objective (RTO).

Code Snippet: Restoring Web Files and a Database

This snippet demonstrates the two most common restore operations: pulling files from a remote backup server via rsync, and restoring a compressed MySQL dump back into the database engine.

#!/bin/bash
# System Restore Procedure

echo "Initiating Emergency Restore Procedure..."

# 1. Restoring Application Files
# Pulling the web directory back from the remote backup server
echo "Restoring /var/www/html from backup server..."
sudo rsync -avz --progress backup_user@10.0.0.50:/backups/webserver_latest/ /var/www/html/

# Ensure proper permissions after file restore
sudo chown -R www-data:www-data /var/www/html/

# 2. Restoring the Database
# Decompressing the gzip backup and piping it directly into MySQL
DB_NAME="production_db"
BACKUP_FILE="/backups/mysql/production_db_2026-03-20.sql.gz"

echo "Restoring Database: $DB_NAME..."
# Drop and recreate the database to ensure a clean slate (Use with extreme caution!)
mysql -u root -p -e "DROP DATABASE IF EXISTS $DB_NAME; CREATE DATABASE $DB_NAME;"

# Decompress and import
gunzip -c $BACKUP_FILE | mysql -u root -p $DB_NAME

if [ $? -eq 0 ]; then
  echo "Database restore completed successfully."
else
  echo "CRITICAL: Database restore failed!" >&2
  exit 1
fi

echo "System Restore sequence finished. Please verify application integrity."

Congratulations!

You have compiled the complete System Administrator Professional Handbook encompassing all 25 competencies defined by the Indonesian SKKNI Level 6 standards. You now have a comprehensive reference manual spanning Design, Deployment, Configuration, Security, Operations, and Disaster Recovery.