Run Direct Restore

Requirements and Limitations

1. Run Direct restore can only be performed on one guest virtual machine at a time.

2. Restored guest virtual machines using Run Direct containing a saved state will not automatically power on. The saved state must be manually deleted in Hyper-V Manager and the guest must be powered on manually.

3. When a guest virtual machine is started in a Run Direct instance is stopped any changes made within the guest environment will be lost, if the guest virtual is not migrated to the Hyper-V Server using the “Auto migrate after Run Direct is running” option.

4. When a guest virtual machine is started using Run Direct Restore all backup jobs (manual, scheduled, and continuous) for the related backup set will be skipped.

5. When a guest virtual machine is started using Run Direct Restore the following features are not available for the backup set; Data Integrity Check, Space Freeing Up, and Delete Backup Data.

Procedures

Requirements and Limitations

1. CloudBacko Pro must be installed on the Hyper-V Host where you wish to restore the guest Virtual Machine.

2. The correct encryption key is required if the backup set was created with the encryption key feature enabled.

3. A guest virtual machine can only be restored to another Hyper-V server with the same version, i.e. backup of a guest on Hyper-V 2012 R2 server cannot be restored to Hyper-V 2008 R2 host or vice versa.

4. A guest virtual machine backed up from a standalone Hyper-V host can only be restored to another standalone Hyper-V host. A guest virtual machine backed up from a Hyper-V Cluster can only be restored to another Hyper-V Cluster.

5. Guest Virtual Machine backed up to local drive / mapped drive / removable drive on the original Hyper-V host, can be restored to another Hyper-V host only if the new machine has access to the original drive(s).

6. The network configuration and structure of the standby Hyper-V host must be same with the original Hyper-V host.

7. The default Java heap size setting on CloudBacko Pro is 1024MB for 32-bit machine, 2048MB for 64-bit machine. For Hyper-V restore it is highly recommended to increase the Java heap size setting to improve performance. Especially guest VM’s with many incremental delta files. (The actual heap size is dependent on amount of free memory available on your Hyper-V host).

8. The temporary directory should be set to a local drive for best restore performance. Also, the temporary directory must have sufficient free disk space for the guest VM restore, for example, the restore of a 500GB guest VM with 30 incremental files of around 5GB each (500GB + 150GB (30 x 5GB)), the temporary directory will require at least 650GB of free space.

9. Restore guest Virtual Machine to “Original Location” is possible only if the disk setup on the new Hyper-V host is the same as the original Hyper-V host, for example if the original guest VM was backed up on G: drive. Then restore to “Original location” can be selected if G: drive is setup on the new Hyper-V host. Otherwise, select “Alternate location”.

10. The Hyper-V management tools must be installed on the new Hyper-V host. For Hyper-V Cluster environments Hyper-V management tools must be installed on all Cluster nodes.

11. The Hyper-V services must be started on the host. For Hyper-V Cluster environment, the Hyper-V services must be started on all Cluster nodes.

12. The Microsoft Hyper-V VSS Writer must be installed and running on the new Hyper-V host and the writer state must be Stable. This can be verified by running the vssadmin list writers command.

Example:

C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
        Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
        Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
        State: [1] Stable
        Last error: No error

Writer name: 'VSS Metadata Store Writer'
        Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
        Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
        State: [1] Stable
        Last error: No error

Writer name: 'Performance Counters Writer'
        Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
        Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
        State: [1] Stable
        Last error: No error

Writer name: 'System Writer'
        Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
        Writer Instance Id: {8de7ed2b-8d69-43dd-beec-5bfb79b9691c}
        State: [1] Stable
        Last error: No error

Writer name: 'SqlServerWriter'
        Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
        Writer Instance Id: {1f668bf9-38d6-48e8-81c4-2df60a3fab57}
        State: [1] Stable
        Last error: No error

Writer name: 'ASR Writer'
        Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
        Writer Instance Id: {01499d55-61da-45bc-9a1e-76161065630f}
        State: [1] Stable
        Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
        Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
        Writer Instance Id: {a51919e3-0256-4ecf-8530-2f600de6ea68}
        State: [1] Stable
        Last error: No error

Writer name: 'COM+ REGDB Writer'
        Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
        Writer Instance Id: {7303813b-b22e-4967-87a3-4c6a42f861c4}
        State: [1] Stable
        Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
        Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
        Writer Instance Id: {d3199397-ec58-4e57-ad04-e0df345b5e68}
        State: [1] Stable
        Last error: No error

Writer name: 'Registry Writer'
        Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
        Writer Instance Id: {25428453-2ded-4204-800f-e87204f2508a}
        State: [1] Stable
        Last error: No error

Writer name: 'BITS Writer'
        Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
        Writer Instance Id: {78fa3f1e-d706-4982-a826-32523ec9a305}
        State: [1] Stable
        Last error: No error

Writer name: 'WMI Writer'
        Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
        Writer Instance Id: {3efcf721-d590-4e50-9a37-845939ca51e0}
        State: [1] Stable
        Last error: No error

Procedures