Accidental deletion
Choose an available point from before the deletion or overwrite and initiate the restore yourself in the customer area.
Backup & disaster recovery
All WVG cloud services are backed up automatically, included in the service price. We keep backups at separate sites from production, together with standby servers for infrastructure recovery.
Standard backups every 24 hours with 5 days of retention. Hourly backups and longer retention are available by commercial agreement.
A separate place for recovery data
Production site
Cloud servicesRunning applications and their dataA different site
Backup storageCompleted versions on ZFSWhen something goes wrong
Backups help address both data mistakes and more serious outages. Recovery starts from available, successfully completed restore points.
Choose an available point from before the deletion or overwrite and initiate the restore yourself in the customer area.
If an application or configuration change disrupts your service, an earlier backup can provide a starting point for recovery.
You can initiate restoration of your virtual server’s disk data yourself. Once complete, check the operating system, applications and dependent services.
Our backup sites also house standby servers. They allow us to restore infrastructure from backups even when production is unavailable; the process and timing follow the DR plan and SLA.
From a running service to a restore point
Automatic backups are included in the price of all cloud services. We retain completed versions outside production, and customers can initiate a restore from them.
VM disks are automatically backed up every 24 hours at block level while running. Data goes to a separate site; hourly backups are available by commercial agreement.
Once copying completes, ZFS retains a version of the disk data. Standard retention is 5 days and can be extended by commercial agreement.
Choose an available completed point and initiate the restore in the customer area. For disaster recovery, we also maintain standby servers at our backup sites.
The last successful backup matters, not just the planned interval. If a backup does not complete, the available restore point may be older.
The recovery process
Start a routine restore directly in the customer area. Support can help you choose the right approach; WVG coordinates larger infrastructure recovery on standby servers.
Open the customer areaBackups every 24 hours with 5 days of retention are included. Hourly backups and longer retention are available by commercial agreement; recovery timing follows the service and SLA.
Select the service and VM in the customer area. In the VM overview, open the snapshots section and choose the restore snapshot action.
Choose an available completed backup from the required period. Check the service and recovery point before confirming; older points do not contain later changes.
Once restoration completes, check your data, applications and their dependencies. Contact WVG support if you need help or are dealing with a larger incident.
Set recovery expectations in advance
The cloud service price includes backups every 24 hours with 5 days of retention. Hourly backups and longer retention are available by commercial agreement; RPO and RTO follow the service and SLA.
RPO is the maximum acceptable loss of recent changes, measured in time. It is the gap between the data state at the recovery point and the incident; the target is agreed according to the needs of the service.
RTO is the target time for restoring a service. It accounts for recovering data, preparing the environment and the steps needed to resume operations.
QEMU controls disk copying through QMP, with data transferred over NBD. The backup contains disk images, not VM memory. This process does not include VSS or guest-freeze coordination.
Backups use full synchronisation of source data. On the backup server, a filter compares incoming blocks with the target data and skips rewriting identical parts. This reduces target writes; it does not provide incremental network transfer.
ZFS snapshots of the disk data are created after copying completes. Recovery requires an available, successfully completed version and all disks needed by the service.
Customers initiate restores in the customer area. The platform also supports RAW export, read-only NBD access and temporary writable overlays for data inspection. Disaster recovery can use standby servers at our backup sites.
Plan your recovery
Your cloud service already includes backups every 24 hours with 5 days of retention. Talk to sales about hourly backups, a longer history and your disaster recovery requirements.
Arrange hourly backups or longer retentionExplore WVG infrastructureIncluded backups every 24 hours with 5 days of retention, customer-initiated restores and standby servers. A technical specification for you and your clients.
Download the PDF overview