Restores for OpenStack

You can restore instances or images in place or to a new destination. You can also restore guest files and folders.

Restores are supported for both Windows and Linux clients.

Note

For both in-place and out-of-place restores, the restored instance is assigned a new instance ID that is different from the source instance.

Restore Processes

The stages of the restore process depend on how the source instance or image was configured.

Create a cinder volume that is the same size as the OS disk in the source VM.
Attach the cinder volume to the VSA proxy.
Restore data received from the MediaAgent into the attached volume.
Detach the volume.
Create a new image from the restored cinder volume.
For cinder data volumes, the restore process includes the following stages:
1. Create cinder volumes.
2. Attach volumes to the VSA proxy.
3. Restore data received from the MediaAgent into the attached volumes.
  
  Up to 25 volumes can be attached to the VSA proxy during restores, occupying device slots vdb- vdz.
4. Detach the volumes.
Launch an instance from the new image.
Attached the restored data volumes to the newly launched instance.
Delete the operating system volume and image that were created to perform the restore.

Create a cinder volume that is the same size as the OS disk in the source VM.
Create data volumes.
Attach volumes to the VSA proxy.
Restore data received from the MediaAgent into the attached volumes.

Up to 25 volumes can be attached to the VSA proxy during restores, occupying device slots vdb- vdz.
Detach the volumes.
Launch an instance from the restored operating system volume.
Attach the restored data volumes to the newly launched instance.