Configure VPS backup servers and backup plans in Virtualizor (admin)

Virtualizor can back up whole virtual machines on a schedule and keep several versions. As an administrator you define where backups are stored (backup servers) and how often they run (backup plans), then attach plans to VPS. Customers can then create and restore backups themselves, as described in VPS backups for customers.

Before you start

• Virtualizor admin access.
• Backup storage, ideally on a separate machine: a storage server reachable over SSH (SFTP) or FTP, with enough space for several full copies of your VPS disks.
• Network bandwidth between nodes and the backup server – full-disk backups move a lot of data.

Add a backup server

1. In the admin panel, go to Backup → Backup Servers → Add Backup Server.
2. Enter a name and choose the type: SSH (recommended) or FTP.
3. Enter host, port, user name and password or SSH key, and the remote directory, for example /backups/virtualizor.
4. Click Test if available, then save.

A Local directory on the node is possible, but it does not protect against the node's disk failing.

Create a backup plan

1. Go to Backup → Backup Plans → Add Backup Plan.
2. Name it, for example Daily-7.
3. Choose the Backup Server and directory.
4. Set the Frequency (hourly, daily, weekly, monthly) and the time to run – spread plans across the night to avoid all nodes backing up at once.
5. Set Rotation (how many backups to keep), for example 7.
6. Choose Compression (gzip or none) and an optional I/O or bandwidth limit so backups do not slow down customer VPS.
7. Decide whether end users may create manual backups and how many.
8. Save.

Assign the plan

• New VPS: select the backup plan in the VPS plan settings so every new server gets backups. See create plans and VPS.
• Existing VPS: open Virtual Servers → List VPS → Manage and choose the backup plan, or use bulk edit for many servers.

Run and monitor backups

• Trigger a test from Backup → Backup Plans with Backup Now.
• Check Tasks and the backup logs for errors and duration.
• Verify files arrive on the backup server and test a restore of a non-critical VPS.

Selling backups

You can include backups in a VPS plan or sell them as an addon. With WHMCS, map a configurable option to the backup plan so customers can order it; see WHMCS Virtualizor module.

Troubleshooting

• Backups fail with connection errors: credentials, firewall or SSH host key problems between node and backup server.
• Backup server full: lower rotation, enable compression or add storage.
• VPS slow during backups: set I/O limits and move schedules to quieter hours.

Next steps

• Add more nodes.
• File-level backups with restic.
• Install Virtualizor.