From the Rapid Recovery Core, you can export a recovery point of a Windows or Linux machine from a repository to a virtual machine (VM). If the original machine protected on the Core fails, you can boot up the virtual machine to quickly replace it temporarily, allowing you time to recover the original protected machine without substantial downtime. This virtual export process results in a VM with all of the backup information from a recovery point, as well as the operating system and settings for the protected machine. The VM becomes a bootable clone of the protected machine.
|
|
NOTE: The recovery point used must be part of a complete recovery point chain. For more information about recovery point chains, see the topic Recovery point chains and orphans. |
You can perform a virtual export from the Virtual Standby page in the Core Console, or by selecting VM Export from the ![[Restore]](/ja-jp/technical-documents/image/56500b3c-a695-4573-bbe5-32228070e16f)
Restore drop-down menu on the button bar.
When you perform a virtual export from Rapid Recovery Core, you have two choices:
- You can perform a one-time virtual export, which creates a bootable VM representing a single snapshot in time from the information in the selected recovery point. The export job is queued immediately, and when it completes, the cloned VM exports to the location you specified. The configuration information used for a one-time export is not saved.
- You can set up continual export. This process creates a bootable VM for the protected machine you specify, saving the VM in a location you designate. The configuration information for performing that virtual export is saved in the Virtual Standby page in the Core Console. Subsequently, each time a new snapshot of the protected machine is captured, the Core queues a new virtual export job, and the bootable VM is refreshed with the updated information. Because this creates a high-availability resource for data recovery, this feature is also called virtual standby.
In between the time a virtual export job queues and is completed, the job is listed on the Export Queue pane of the Virtual Standby page in the Core Console.
The following diagram shows a typical deployment for exporting data to a virtual machine.
Virtual standby deployment
![[Virtual standby deployment]](/ja-jp/technical-documents/image/70a32732-676d-4e69-90ff-092b631109f8)
|
|
NOTE: In a continual export configuration involving replication set up between two Cores (source and target), you can export from either Core. However, you can only perform virtual export from the target Core after the initial replication is complete.
Subsequently, each time a new snapshot of the protected machine is captured, replication from a source Core queues a new virtual export job after each snapshot is captured. Replication from a target Core queues a new virtual export job after replication job. |
Compatible VM hypervisors include vCenter/ESXi, VMware Workstation, Hyper-V, Oracle VM VirtualBox, and Azure. For information about supported versions of these hypervisors, see the topic " Hypervisor requirements" in the Rapid Recovery System Requirements Guide.
For ESXi, VMware Workstation, or Hyper-V, the virtual machine version must be a licensed version of these virtual machines, not the trial or free versions. Exporting to Azure requires you to have an account on Azure, with other prerequisites.
|
|
NOTE: Working with Azure involves aspects unique to that cloud service provider. Like all other Azure features in Rapid Recovery, virtual export now uses the Azure Resource Management (ARM) deployment method. Azure setup steps and prerequisites to performing virtual export from the Rapid Recovery Core Console have changed accordingly. For details on Azure prerequisites prior to export, see Before virtual export to Azure. |
Related Topics
In Rapid Recovery, you can export data to ESXi by performing a one-time export, or by establishing a continual export (for virtual standby). Complete the steps in the following procedures for the appropriate type of export.
Topics include:
Complete the steps in this procedure to perform a one-time export to ESXi.
- From the Rapid Recovery Core Console button bar, click the Restore
![[Expand drop-down menu]](/ja-jp/technical-documents/image/fcc6fb73-d892-4cc3-9284-89b907583757)
drop-down menu, and then select ![[VM Export]](/ja-jp/technical-documents/image/48b3556a-66c4-475c-8df4-a16fd5007114)
VM Export.
The Virtual Machine Export Wizard appears.
- In the wizard, select One-time Export, and then click Next.
- On the Machines page, select the protected machine that you want to export, and then click Next.
- On the Recovery Points page, select the recovery point that you want to use for the export, and then click Next.
- On the Destination page, in the Export a virtual machine to drop-down menu, select vCenter/ESXi, and then enter the parameters for accessing the virtual machine as described in the following table.
Table 113: Virtual machine parameters
|
Host name |
Enter a name for the host machine. |
|
Port |
Enter the port for the host machine. The default is 443. |
|
User name |
Enter the user name for logging on to the host machine.
|
|
NOTE: Optionally, you can select credentials for a user in the Credentials Vault, or you can save credentials you add here to the vault. For more information, see Credentials Vault. | |
| Password |
Enter the password for logging on to the host machine. |
- Click Next.
- On the Virtual Machine Options page, enter the information described in the following table, and then Click Next.
Table 114: Virtual machine options
|
Resource pool |
Select a resource pool from the drop-down list. |
|
VM configuration location |
Select a data store from the drop-down list. |
|
VM name |
Enter a name for the virtual machine you want to export.
The VM name that automatically appears by default is the name of the machine from which the recovery point originated. |
|
Amount of RAM |
Specify the memory usage for the virtual machine by clicking one of the following:
|
|
Number of processors |
Enter the number of virtual CPUs you want for the exported virtual machine. The minimum is 1. |
|
Cores per processor |
Enter the number of cores to use for each processor. The minimum is 1. |
|
Disk provisioning |
Select the type of disk provisioning from the following options:
- Thin. Thin provisioning creates a virtual disk the size of the used space on the original volumes, rather than the entire volume size. For example, if the original volume is 1 TB, but contains only 2 GB of used space, Rapid Recovery creates a virtual disk of 2 GB.
- Thick. Thick provisioning creates a new disk or volume that is the same size as the original volume from the protected server, even if only a portion of the original volume is being used. For example, if the volume is 1 TB large but contains 2 GB of used space, Rapid Recovery creates a virtual disk of 1 TB.
|
|
Disk mapping |
Specify the type of disk mapping as appropriate. You can choose from:
- Automatic. Using this option, the VM is exported to any available datastore with sufficient space.
- Manual. Select this option to manually specify the datastore onto which to export the VM.
- With VM. Select this option to export all virtual disks to the same datastore as the VM configuration.
|
|
Version |
Select the version of the virtual machine. |
|
Network adapters |
Optionally, specify network adapter options for the VM to be exported.
|
|
NOTE: This option appears when exporting to a hypervisor of the same type (in this case, when exporting to ESXi). |
You can choose from:
- Same as source machine. If you select this option, the VM include the same amount of network adapters as on the source, and they are assigned to the default network on the host.
- Specific. Select this option to see the Network Adapters page of the Virtual Machine Export wizard. Here you can add one or more network adapters to the VM and assign a specific network to each adapter.
|
|
Secure boot |
Optionally, choose the secure boot option for the exported VM.
|
|
NOTE: This option appears only when secure boot is configured for the source protected machine. | |
|
Restore all configuration data |
If you want to recover all VM configurations for volumes being recovered, select this option. If you want to restore data only and not the VM configurations, clear this option.
This option appears only when performing virtual export of an agentless VM and after a resource pool is selected.
For more information on the VM configuration backup and restore feature of Rapid Recovery, see VMware VM configuration backup and restore. |
- Optionally, on the Network Adapters page of the wizard, if you want to add a virtual network adapter to the VM to be exported, click + Add, and then from the Available Networks drop-down menu, select the name of a network available on the hypervisor host.
- Optionally, to add additional network adapters, click + Add, and then from the Available Networks drop-down menu, select the name of another network available on the hypervisor host.
- Click Next.
- On the Volumes page, select the volumes from the source recovery point that you want to export to the VM, and then click Finish to complete the wizard and start the export.
|
|
NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events pages. |
- On the Summary page, click Finish to complete the wizard and start the export.
|
|
NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events pages. |
Complete the steps in this procedure to set up continual export to an ESXi virtual machine (VM) using Rapid Recovery. This process is also known as setting up virtual standby.
- In the Rapid Recovery Core Console, do one of the following:
- From the Core Console, in the button bar, click the Restore drop-down menu, and then select VM Export.
- In the Virtual Machine Export Wizard, select Continual export (virtual standby).
- Click Next.
- From the Core Console, in the icon bar, click
![[Virtual Standby]](/ja-jp/technical-documents/image/2daca3d8-96f0-427e-b6b3-a5abe639975e)
(Virtual Standby).
- On the Virtual Standby page, click Add to launch the Virtual Machine Export Wizard.
- On the Machines page of the Virtual Machine Export Wizard, select the protected machine that you want to export, and then click Next.
- On the Destination page of the Export Wizard, in the Export a machine to drop-down menu, select vCenter/ESXi.
- Enter the information for accessing the virtual machine as described in the following table, and then click Next.
Table 115: ESXi credentials
|
Host name |
Enter a name for the host machine. |
|
Port |
Enter the port for the host machine. The default is 443. |
|
User name |
Enter the credentials for the host machine.
|
|
NOTE: Optionally, you can select credentials for a user in the Credentials Vault, or you can save credentials you add here to the vault. For more information, see Credentials Vault. | |
| Password |
Enter the credentials for the host machine. |
- On the Virtual Machine Options page, enter the information described in the following table.
Table 116: Virtual machine options
|
Resource pool |
Select a resource pool from the drop-down list. |
|
VM configuration location |
Select a data store from the drop-down list. |
|
VM name |
Enter a name for the virtual machine you want to export.
The VM name that automatically appears by default is the name of the machine from which the recovery point originated. |
|
Amount of RAM |
Specify the memory usage for the virtual machine by clicking one of the following:
|
|
Number of processors |
Enter the number of virtual CPUs you want for the exported virtual machine. The minimum is 1. |
|
Cores per processor |
Enter the number of cores to use for each processor. The minimum is 1. |
|
Disk provisioning |
Select the type of disk provisioning from the following options:
- Thin. Thin provisioning creates a virtual disk the size of the used space on the original volumes, rather than the entire volume size. For example, if the original volume is 1 TB, but contains only 2 GB of used space, Rapid Recovery creates a virtual disk of 2 GB.
- Thick. Thick provisioning creates a new disk or volume that is the same size as the original volume from the protected server, even if only a portion of the original volume is being used. For example, if the volume is 1 TB large but contains 2 GB of used space, Rapid Recovery creates a virtual disk of 1 TB.
|
|
Disk mapping |
Specify the type of disk mapping as appropriate. You can choose from:
- Automatic. Using this option, the VM is exported to any available datastore with sufficient space.
- Manual. Select this option to manually specify the datastore onto which to export the VM.
- With VM. Select this option to export all virtual disks to the same datastore as the VM configuration.
|
| Version |
Select the version of the virtual machine. |
|
Network adapters |
Optionally, specify network adapter options for the VM to be exported.
|
|
NOTE: This option appears when exporting to a hypervisor of the same type (in this case, when exporting to ESXi). |
You can choose from:
- Same as source machine. If you select this option, the VM include the same amount of network adapters as on the source, and they are assigned to the default network on the host.
- Specific. Select this option to see the Network Adapters page of the Virtual Machine Export wizard. Here you can add one or more network adapters to the VM and assign a specific network to each adapter.
|
|
Secure boot |
Optionally, choose the secure boot option for the exported VM.
|
|
NOTE: This option appears only when secure boot is configured for the source protected machine. | |
|
Restore all configuration data |
If you want to recover all VM configurations for volumes being recovered, select this option. If you want to restore data only and not the VM configurations, clear this option.
This option appears only when performing virtual export of an agentless VM and after a resource pool is selected.
For more information on the VM configuration backup and restore feature of Rapid Recovery, see VMware VM configuration backup and restore. |
|
Perform initial one-time export |
Select this option to queue the export job immediately. Clear this option if you want the Core to wait until the next forced or scheduled backup snapshot. |
- Click Next.
- Optionally, on the Network Adapters page of the wizard, if you want to add a virtual network adapter to the VM to be exported, click + Add, and then from the Available Networks drop-down menu, select the name of a network available on the hypervisor host.
- Optionally, to add additional network adapters, click + Add, and then from the Available Networks drop-down menu, select the name of another network available on the hypervisor host.
- Click Next.
- On the Volumes page, select the volumes to export (for example, C:\ and D:\), and then click Finish to close the wizard and start the export.
|
|
NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events pages. |
