Restore a Virtualizor backup only after identifying the exact recovery point and target. An in-place restore replaces current guest data. Restoring to a new VPS, where supported, provides a safer place to inspect the result before moving production traffic.
IN THIS ARTICLE
Prepare for the change
Record the original VPS ID, backup date, destination and expected lost-change window. Preserve useful data written since the backup. Confirm the backup type and licensing, because native and Backuply recovery workflows are not interchangeable.
01 Restore a Virtualizor VPS backup safely
- Open Backup > Restore VPS Backups and select the correct active node or backup source. Locate the backup by VPS and date, or use the supported directory scan when appropriate.
- Inspect the target choice carefully: existing VPS, new VPS or another supported server. Confirm capacity and network compatibility before proceeding.
- Isolate a test restore from production mail, scheduled jobs and external transaction systems. For an in-place recovery, stop application writes and announce the maintenance window.
- Start the selected restore once and follow its task status. Preserve the backup and its metadata until the recovered guest has passed validation.
- Boot the result, use the console to check networking and run application acceptance tests. Reconcile post-backup transactions before changing DNS or replacing the live service.
Can I restore when the original host is offline?
A supported restore to another host can work when the independent backup and required metadata are available. Confirm destination compatibility and prevent the old host from later starting a duplicate authoritative guest.
Check the backup or recovered data
Check recovered file dates, database integrity, account access, certificates and a representative user workflow. Confirm that only the intended guest uses the production IP. Create a fresh backup after recovery and document the actual restore duration.
If the change does not work
If the backup cannot be found, verify directory structure, date selection, access permissions and required metadata. A standalone disk file may lack the information needed to recreate a deleted VPS. Inspect the restore log instead of repeatedly submitting the same action or renaming files speculatively.