Rebuild without losing the important work

A rebuild replaces the server’s system disk in a real hosting environment. Files, local databases, installed software and credentials can be lost. A catalogue configuration change is not the same operation, and the account interface contains no live rebuild action.

Copy application data and a consistent database export to another failure domain. Keep decryption keys outside the machine. Test the backup on a separate destination before authorising disk replacement; a successful upload alone is not proof of recoverability.

Capture service configuration, package versions, firewall rules, DNS records, scheduled jobs and required secrets through a private channel. Note which data changes after the final backup and plan a maintenance window for that final copy.

Use a release offered for the actual product and a known installation path. A real platform should show the destructive effect and require an explicit action. No fixed rebuild duration is promised by this local guide.

The server may have new credentials or a different host key. Check them through the trusted console before connecting. Restore permissions and data, run an application test, inspect DNS and network exposure, then retain the previous recovery copy until the result is accepted.