x360Recover supports instant virtual disk exports in Microsoft Azure VHD format.
This feature allows relatively easy virtual machine recovery - directly into Azure from your x360Recover backup data.
Essentially, all you do is export the virtual disk(s) from backup, upload them to Azure, and create a new virtual machine.
- STEP 1. Export the protected system disks to Azure VHD format
- STEP 2. Check the virtual disk export
- STEP 3. Manually import virtual disks into Microsoft Azure
- STEP 4. Upload virtual disk(s) to Azure
- STEP 5. Create an Azure virtual machine Disk Image
- STEP 6. Create an Azure virtual machine (may take up to 30 minutes)
To restore an Azure VM from Axcient x360Recover, the disk volumes for the protected system must be exported in the Azure VHD image format.
There are two methods available to complete this export:
Disk images can be
- exported from the x360Recover vault or
- generated from Recovery Center
Which export method should I use?
- Use the Recovery Center method if you have a Local Cache repository available for the protected system. For more details on using Recovery Center, see Virtual Disk Export with Recovery Center.
- Otherwise, it will be faster to download the images directly from the vault using FTP. For best FTP download performance see: LFTP Client for Windows. For more detailed information on performing exports, see Instant Disk Exports.
Method #1: Use a vault to export to Azure VHD format
Instant virtual disks exports are available within the x360Recover appliance or vault for all major Hypervisor platforms.
1. Log in to your vault and navigate to the Protected System Details page of the protected system you wish to recover.
2. Select the desired snapshot recovery point and click Export.
You may optionally choose to include or exclude disks to be exported.
3. Choose VHD for Azure, enter the protected system encryption passphrase if present, and click Start.
Exported virtual disks will immediately be available for download from the File Browser or via FTPS.
For more detailed information on performing exports, see Instant Disk Exports.
For more details on using FTPS, see FTPS for File and Folder Recovery.Delete
Method #2: Use Recovery Center to generate Azure VHD format
Use this Recovery Center method if you have a Local Cache repository available for the protected system.
Recovery Center can be download from our download page at https://help.axcient.com/General-Axcient-Information/downloads/ (or you can download Recovery Center from the Downloads page on your x360Recover appliance or vault.)
1. Within Recovery Center, start a new recovery.
2. For Recovery Type, select Virtual Disk Export.
3. For Virtual Disk Type, choose VHD - Microsoft Azure.
You will then select the desired client, data source, (vault) protected system, and recovery point.
Finally, execute the recovery job.
Once the recovery job is running, your VHD disk image is available to be copied or uploaded to Azure.
For more details on using Recovery Center, see Virtual Disk Export with Recovery Center.Delete
Before uploading the virtual disk to Azure, it is a good idea to verify the integrity of the disk export images.
1. Open the Disk Management utility on the Windows machine.
2. Press the Windows key + R simultaneously to open the run dialog.
3. Enter diskmgmt.msc and click OK.
4. Click Attach VHD from the Action menu and select the exported Azure disk image.
5. Verify the virtual disk mounted, and all volumes are readable by Windows.
Note: Mounted virtual disks are highlighted with a different color within Disk Manager.
6. Once you have verified the disk integrity, remove the virtual disk from the local system. Right-click the virtual disk and select Detach VHD.
Once you have downloaded your virtual disks, you need to upload them to Azure and create a virtual machine.
Prepare the Azure environment
1. Go to https://portal.azure.com/#home
2. Log in with your Microsoft account or common Azure account.
3. Enter ‘resource groups’ in the search bar and click on the Resource Groups service.
4. If you have an existing Resource Group you wish to use for the new virtual machine, select it and skip to #9.
Otherwise, you will need to create a new Resource Group.
5. Click Create.
6. Choose the Subscription to which this Resource Group will belong.
7. Enter a name for the Resource Group and select a data center Region.
8. Click Review + create. Review the details then click Create to complete creation of the Resource Group.
9. Click the name of your Resource Group to open it.
10. Click Create.
11. Enter ‘Storage Account’ in the search field, then click into Storage Account.
12. Click Create.
13. Choose a Subscription and Resource group. Enter a Storage account name and select a data center Region. All other settings can remain at their defaults. Click Review + create. Review the selections then click Create.
Note: Deployment of the storage account can take up to 40 minutes.
1. Open the Storage Account and click Open in Explorer. If you have not yet installed Azure Storage Explorer, click the provided link to download and install it.
2. Within Azure Storage Explorer, expand your Subscription, expand Storage Accounts, expand the Storage Account you created for this virtual machine, and right-click on Blob Containers. Click Create Blob Container.
Note: If you don’t see your subscription within Azure Storage Explorer, you may need to sign in. Click sign in from the top toolbar. A new browser window will open for you to sign in with your Azure subscription. When finished, return to Azure Storage Explorer.
3. Click to select your new Blob Container, then click Upload. Click Upload Files.
Note: You can select multiple virtual disks to store all disks in a single blob.
4. Click the Blob type dropdown and select Page Blob. Select your VHD image file(s) and click Upload.
Uploading your virtual disk images may take some time.
Note: If you are uploading a virtual disk image created with Recovery Center, you may have to first set permissions on the file. (Recovery Center exports are set with permissions by default to allow only Hyper-V administrators to access the data.)
- Right-click the file and click Properties. Navigate to the security tab and click Advanced, Permissions, Continue, then Add. Click Select Principle.
- Type 'Users’ and click Check Names, then click OK.
- Select Full Control and click OK.
1. Log in to Azure and open your Resource Group. Click Create.
2. Enter ‘Image’ in the search and click to select Image.
3. Click Create.
4. Enter a Name for the virtual machine and select a data center Region.
For OS type, select Windows.
For VM generation:
- For Legacy BIOS / MBR protected systems, select Gen1.
- For Modern EFI protected systems, select Gen2.
Select the Storage Blob containing your protected system boot disk.
For Account type, Standard HDD is recommended.
For Host caching, Read/write is recommended.
Select an option for Encryption Type.
If your protected system has additional disks, specify additional disk LUN numbers as needed and select the blob object representing each disk.
Click Review + create.
5. Review your selections and click Create.
1. Go to your Azure Image and click Create VM.
You may search for ‘Image’, click image, then click your image name to open the Image.
2. Enter a Virtual machine name, choose an Image and a Size, and specify Administrator account credentials.
3. Specify firewall inbound ports. RDP is recommended to enable easy remote access to the protected system virtual machine.
Specify Windows OS license type and click Next: Disks >.
4. Specify disk options; you may specify disk types, and add or remove additional disks to the VM if necessary.
On the Management tab, you can also disable boot diagnostics and/or OS updates.
Click Review + Create then click Create. Deployment may take about 30 minutes.
Note: It’s possible your deployment will time out and fail with an error similar to this:
This is OK, check back later and verify that the deployment succeeded in the background.
Once the virtual machine is created and running, it will be assigned a public IP address. Find this IP address on the VM details page and use it to connect via Remote Desktop Connection (RDP).