# Restoring Full Instances for OpenStack

You can restore instances or images to the original location or to a different location. By default, an instance is restored to the original hypervisor, using the same proxy as the backup.

Consider the following information:

- If the OS disk was filtered from the backup of an instance, the base image that the instance was based on must be available for the instance to be restored.

- If an instance or image is added to VM group content or to a filter by browsing and selecting the display name, discovery is performed based on the GUID for the instance or image. If that instance or image is later restored in place from a backup, a new GUID is generated, and that instance or image is no longer identified correctly. To identify that instance or image, you must remove the old rule, then add a new rule or use a name pattern to select the instance or image.

- If the user specified for the virtualization client does not have permission to create or delete network ports, the restore fails with error "Failed to create port with request".

- When restoring public images for a project, the user performing the restore should have the Admin role for that project. When a user only has the Member role for a project, that user does not have permission to create public images and can only restore an image as a private image. In that situation, an Admin user could later make the restored image public.

## Prerequisites

- If a passkey is configured for restores, you must have the passkey.

- If you want to restore data using a specific MediaAgent and/or copy, review the information in MediaAgent and Copy Precedence Considerations for Virtualization Restores.

## Procedure

1. From the Command Center navigation pane, go to Protect > Virtual machines.

   The Overview page appears.

2. On the VM groups tab, for the VM that you want to restore, click the action button (...) and then select Restore.

   The Select restore type page appears.

3. Click Full instance.

   The Full instance page appears.

4. To select a specific access node and/or source for the restore, in the upper-right area of the page, click the Settings.

   1. For MediaAgent, decide whether to have the Commvault software automatically select the MediaAgent or to specify a MediaAgent:

      - Automatic: By default, the Commvault software selects the MediaAgent for the restore operation based on availability and environment.

      - To restore data using a specific MediaAgent, from the list, select a MediaAgent.

   2. For Source, decide whether to have the Commvault software automatically select the copy of backup data or to specify the copy:

      - Automatic: By default, the restore operation searches for the requested data in the primary copy and selects a different copy if the data is not found in the primary copy.

      - To restore from a specific copy of backup data, from the list, select a backup copy.

   3. Click Save.

5. Select the content to restore, and then click Restore.

   The Restore wizard appears.

## Perform an In Place Restore

1. For Type, select In place.

2. For Access node, select Automatic, an access node, or an access node group.

   If you are restoring multiple VMs, select Automatic to distribute the workload across the access nodes that are assigned for the destination hypervisor. First, the VMs are assigned to the access nodes that are in the same region. If no access nodes are available in the same region, the VMs are assigned to access nodes using the round-robin method. The Automatic option is available for full restore and conversion operations from both streaming backups and IntelliSnap backup copies.

   If you select an access node group to restore VMs, the Commvault software distributes the workload across the access nodes that are available in the access node group.

3. Click Next.

   The Virtual Machines page appears.

4. Select the VMs to restore.

5. Click Next.

   The Restore Options page appears.

6. Specify the following settings:

   - Power on VMs after restore: Automatically restart VMs after they are restored.

     The power state of the VM does not affect subsequent backups. If the VM is powered on during backups, by default, the VM is powered on again after the restore completes (unless you clear this check box).

     Note

     If this option is not selected during the restore, Openstack instances will power on after creation and will immediately power off. This is due to the limitations of the Openstack APIs that are used for restores.

   - Unconditionally overwrite if it already exists: Delete an existing VM and replace it with the restored VM.

   - Notify user on job completion: Receive an email notification that the restore is complete.

7. Click Next.

   The Summary page appears.

8. Review the summary, and then click Submit to start the restore.

## Perform an Out of Place Restore

1. For Type, select Out of place.

2. For Restore as, select the platform to restore the VMs to.

3. For Destination, select the virtualization client for the cluster from the list.

4. For Access node, select Automatic, an access node, or an access node group.

   If you are restoring multiple VMs, select Automatic to distribute the workload across the access nodes that are assigned for the destination hypervisor. First, the VMs are assigned to the access nodes that are in the same region. If no access nodes are available in the same region, the VMs are assigned to access nodes using the round-robin method.

   If you select an access node group to restore VMs, the Commvault software distributes the workload across the access nodes that are available in the access node group.

5. Click Next.

   The Virtual Instance page appears.

### Restore content for single or multiple VMs

1. Select the VM to restore and configure the following settings.

   - For Change display name, click the pencil icon and enter another name for the restored instance.

     If an existing instance with the same name exists on the destination host and you do not select Unconditionally overwrite if it already exists, the restore job fail

   - For Availability zone, browse the defined availability zones and select a host.

   a. For advanced restore configuration options, click Edit.

   The Configure restore options page appears.

   - If multiple VMs are selected to restore, provide the following information:

     - For Add a prefix to the VM name, if you are restoring multiple VMs, to add a prefix to the VM display names, move the toggle key to the right and enter the prefix.

     - For Add a suffix to the VM name. if you are restoring multiple VMs, to add a suffix to the VM display names, move the toggle key to the right and enter the suffix.

   - For Availability zone: browse the defined availability zones and select a host.

   - For VM display name, if you are restoring a single insts, enter another name for the restored VM.

   - For Volume type, select a volume type that is defined for the zone of the source volumes.

   - For Flavor, select a flavor that is at or above the original configuration. If you choose Automatic (the default option), the instance type is selected based on the corresponding settings for the source VM.

   - For Security group, select a predefined security group that defines the required network access.

     - Key pair: Select a key pair that identifies the ownership for the converted instance.

       Note

       An OpenStack key pair is associated with a specific OpenStack user. If a hypervisor client is created using User A, only the key pairs associated with that user will be visible in the key pair browsing interface during restore or replication; key pairs belonging to other users will remain hidden. To access those, they must first be uploaded through the OpenStack console under the correct user account. Once uploaded, the key pairs will appear in the key pair browsing interface within the Commvault software.

     - Network interface: Select a network interface that is available in the destination.

     - Image: If the image is unselected and if it's available in the Openstack environment, the source VM image will be used as a base image for the restore. If you select an image from the list, it must be compatable with the VM you are restoring.

       Consider the following information when creating an instance:

       - If the instance was created from an image, the restored instance will use the selected image to set up its OS disk.

       - If the instance was created from a volume, the restored instance will boot from the selected image rather than attaching the original boot volume. This means the OS disk of the restored instance will be based on the selected image, not the original source volume.

   - Power on instances after restore: (Optional) Start the instance automatically when the restore completes.

     Note

     If this option is not selected during the restore, Openstack instances will power on after creation and will immediately power off. This is due to the limitations of the Openstack APIs that are used for restores.

   - Unconditionally overwrite if it already exists: (Optional) Delete an existing instance that has the same name, and replace it with the restored instance.

   - Reuse existing VM client: Reuse the existing VM client and map its information, such as Client Name, Host Name, and Client id to the source VM.

2. Click Submit to run the restore job.

×

Loading...