Virtualizor backup plans connect a schedule and retention policy to individual VPSs or VPS plans. Establish a working recovery destination before relying on the schedule. Local copies on the same host do not cover loss of that host or its storage.
IN THIS ARTICLE
What you need before you begin
Identify the required recovery point and restore time for each workload. Confirm licensed features and supported destination types in the installed version. Prepare an independent destination with sufficient storage, restricted credentials and secure transport.
01 Schedule a Virtualizor VPS backup
- Add the destination through Servers > Add Backup Server or the supported storage integration. Test connectivity using the credentials and path the backup service will use.
- Create a plan under Plans > Add Backup Plan. Set a realistic schedule, retention and destination directory, accounting for peak workload and competing jobs.
- Assign the plan explicitly to the intended VPS, or set the VPS to inherit its VPS plan backup policy. Do not assume changing a plan retroactively changes every overridden guest.
- Review customer-initiated backup and restore allowances separately from scheduled backups. Allow only the intended operations and capacity.
- Run one controlled backup and inspect its completion log. Restore to an isolated test VPS and verify application data before relying on unattended runs.
Why is a VPS missing its scheduled backup?
Check whether it inherits the intended plan, whether that plan is enabled, and whether its destination and schedule are valid. The presence of a backup-plan name alone does not prove that the guest is covered.
Check the backup or recovered data
Confirm the next scheduled backup occurs at the expected timezone and the newest recovery point is discoverable. Observe destination capacity and rotation. Verify application consistency using database-aware backups or a documented quiescence procedure when a live disk copy is insufficient.
Troubleshoot unexpected results
Investigate job errors in the per-VPS backup log and task interface. Check destination authentication, path ownership, free space and schedule inheritance. Do not delete arbitrary files from a backup chain or force many simultaneous retries. Correct the cause, retain the last usable recovery point and repeat one controlled job.