In short: Reinstalling or rebuilding a server normally replaces its operating-system disk and can permanently erase data. Verify backups, record the network and licence details, and plan how access will be restored before starting.
Decide whether rebuilding is appropriate
A rebuild is suitable for a clean operating-system deployment or a system that cannot be trusted. It is not a substitute for diagnosing a small application fault, and it will not repair underlying hardware problems.
Before the rebuild
- Take and test backups stored outside the server.
- Record IP addresses, prefixes, gateways, reverse DNS and firewall requirements.
- Export application configuration, databases, certificates and licence information.
- List required users, SSH keys, packages and scheduled tasks.
- Notify affected users and agree a maintenance window.
Perform the rebuild
Use the service's rebuild facility if one is provided, or arrange the work with Virgo Networks. Select the correct server and supported operating system. Do not reuse compromised passwords or unknown configuration files.
After installation
- Patch the operating system.
- Configure named administrator access and test SSH keys.
- Apply the firewall before exposing applications.
- Restore data and configuration in a controlled order.
- Validate IPv4, IPv6, DNS, TLS, monitoring and backups.
- Keep the maintenance record and remove temporary access.
Ask before acting
If the rebuild option, storage layout or retained-data behaviour is unclear, open a support ticket before confirming it.
