Record the delivered baseline
Record the server hostname, operating system, CPU, memory, disks, primary IPv4 and IPv6 addresses, boot mode and network configuration. Compare them with the order before installing an application. This baseline is essential when diagnosing a later hardware, routing or capacity problem.
Secure administrative access
Create an individual SSH key for each administrator, verify the server host fingerprint and disable password login only after key-based access has been tested in a second session. Restrict firewall rules to required services, keep an out-of-band console path available and store recovery instructions outside the server.
Set up a recovery plan
Activate the included backup storage when available, allow only the required source address and protocol, and configure the backup application. Then restore a representative file or workload to a safe location. A successful backup job without a successful restore is not proof of recoverability.
- Keep at least one recovery copy outside the server's local disks.
- Record the normal boot mode and the steps for reaching rescue mode.
- Define who can authorise a restore or operating-system reinstall.
Complete acceptance testing
Confirm remote access, DNS, time synchronisation, disk health, monitoring, expected open ports and backup delivery. Reboot once during the acceptance window and verify the server returns to normal service without manual intervention. Only then should production data or public traffic be moved.
