On-demand system backups
As automated deployments and Infrastructure-as-Code (IaC) services become increasingly popular, a system backup is essential. That's why your instances at OVH can be backed up at any time. The server will export the instance’s disk, enabling you to industrialise your deployments.
Secure and resilient
Instances run on hypervisors, and their system disk is located locally on them. The backup instance copies this data to another storage system, and guarantees triple replication, to ensure reliability.
Simplified backup and restore methods
Backup instances behave like elements of the Private Image Catalog. Once they have been added to it, you can use them to restore the original instance, or even serve as a system image for other instances based on the same boot schemas.
Create a single backup instance
openstack server image create --name inst01-bkp01 inst01
Create a rolling backup, with a log of seven entries
openstack server backup create --rotate 7 inst01
In accordance with our reversibility policy, we offer you the ability to recover your backup without any hassle, using standard tools like the OpenStack CLI.
System migration to other locations
Once the backup has been created, you can perform an instance system migration by exporting it, then importing it to the Private Image Catalog of another location.
OpenStack incorporates a rolling backup system. By specifying the number of elements included in the rotation, the system will automatically maintain its history, deleting the oldest backup when a new one is created.
What SLA does OVHcloud offer for accessing the Instance Backup service?
The SLA guarantees 99.9% monthly availability for accessing the Instance Backup service. For further information, please refer to the Terms & conditions.
What SLA does OVHcloud offer for data resilience on the Instance Backup service?
The data resilience rate is 100% for the Instance Backup service. For further information, please refer to the Terms & conditions.
Can I automate instance backups?
Yes, you can use a scheduler (OpenStack Mistral) to trigger backups on a regular basis. You can schedule them manually, or you can use pre-configured, standard routines.
How long does it take to restore a backup?
The time will vary depending on the disk size of the instance you are restoring. An instance with a 50GB disk will take less time to restore than an instance with a 800GB disk.
Is the instance configuration (flavor size, assigned network port) backed up?
Some data is stored and attached to the backup, such as the instance model ID, the volume of RAM, and the disk size. Network information is not stored. However, all operating system configurations are stored.
Are the additional volumes also backed up?
No. Volumes attached to an instance must be backed up separately from the instance itself.