What to do after provisioning a server

Start with an inventory

Record the operating-system version, disk layout, network addresses and allocated resources. Do not equate virtual CPUs with physical cores when comparing against the catalogue. For managed services, establish which operations belong to the provider. These Linux commands inspect basic state without modifying the system; output may contain details such as network addresses.

cat /etc/os-release
lsblk
free -h
df -h
ip address

Improve security without locking yourself out

Use strong, unique credentials and prefer key-based SSH and multi-factor management access where supported. Limit privileges to the task. Keep the current connection open while changing firewall rules, test access in a second session and learn how the recovery console works. Do not close all management ports without checking recovery access.

Establish updates and monitoring

Check distribution support and security updates. Assess compatibility and rollback before applying changes. Define alerts for disk usage, memory pressure, CPU use and application errors. Test not only that an alert is generated but also that it reaches the right person.

Test a restore

Plan to keep backups independently of production. Use application-aware methods for database and file consistency. Restore into a separate test environment and verify service startup and data readability. A snapshot or RAID alone is not an independent backup; manage retention and permissions separately.