public:microsoft_hyper-v
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:microsoft_hyper-v [2019/09/09 17:23] ronnie.chan |
public:microsoft_hyper-v [2022/11/28 11:11] (current) kirk.lim Last modified: 2019/12/06 13:50 by yuk.cheng |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Microsoft Hyper-V Backup Set ====== | ====== Microsoft Hyper-V Backup Set ====== | ||
| + | |||
| + | Last modified: 2019/12/06 (Note: Content written for AhsayCBS v7+v8, and still generally apply to latest product release) | ||
| AhsayOBM allows you to back up individual Guest VMs in your Microsoft Hyper-V Host with the MS Exchange Mail Level Backup Set. | AhsayOBM allows you to back up individual Guest VMs in your Microsoft Hyper-V Host with the MS Exchange Mail Level Backup Set. | ||
| Line 63: | Line 65: | ||
| <code> | <code> | ||
| NOTE | NOTE | ||
| - | For Hyper-V server in Failover Cluster environment, the temporary folder must be set to a network shared path accessible to all cluster nodes, or a Cluster Shared Volume. | + | For Hyper-V server in Failover Cluster environment: |
| + | - Hyper-V server 2008 / 2008 R2 and 2012 / 2012 R2 the temporary directory must be set to a local drive of the cluster node. | ||
| + | - Hyper-V server 2016 / 2019 the temporary directory must be set to the Cluster Shared Volume (CSV). | ||
| </code> | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 389: | Line 393: | ||
| The following steps are taken when a Run Direct restore is initiated: | The following steps are taken when a Run Direct restore is initiated: | ||
| + | |||
| + | <WRAP indent> | ||
| 1. **Delete Guest Virtual Machine** - AhsayOBM will delete the existing guest virtual machine on the original or alternate location (if applicable). | 1. **Delete Guest Virtual Machine** - AhsayOBM will delete the existing guest virtual machine on the original or alternate location (if applicable). | ||
| Line 403: | Line 409: | ||
| 7. **Delete VSS Snapshot** - The VSS snapshot will be deleted after the Run Direct restoration is completed. | 7. **Delete VSS Snapshot** - The VSS snapshot will be deleted after the Run Direct restoration is completed. | ||
| + | |||
| + | </WRAP> | ||
| The restored virtual machine, at this stage (e.g. before the restore is finalized) is in a read-only state to avoid unexpected changes. All changes made to the virtual disks (e.g. operation within the guest virtual machine) are stored in a VSS snapshot created for the Run Direct restore. These changes are discarded when Run Direct is stopped, where the restored guest virtual machine will be removed and all changes will be discarded, or the changes will be consolidated with the original virtual machine data when the restore is finalized. | The restored virtual machine, at this stage (e.g. before the restore is finalized) is in a read-only state to avoid unexpected changes. All changes made to the virtual disks (e.g. operation within the guest virtual machine) are stored in a VSS snapshot created for the Run Direct restore. These changes are discarded when Run Direct is stopped, where the restored guest virtual machine will be removed and all changes will be discarded, or the changes will be consolidated with the original virtual machine data when the restore is finalized. | ||
| Line 420: | Line 428: | ||
| ==== How does Granular Restore work? ==== | ==== How does Granular Restore work? ==== | ||
| - | {{public:ahsay_wiki_module_hyper-v_requirement_11.png}} | + | {{public:ahsay_wiki_module_hyper-v_requirement_11.png?800}} |
| ==== Benefits of using Granular Restore ==== | ==== Benefits of using Granular Restore ==== | ||
| Line 443: | Line 451: | ||
| === Operating System === | === Operating System === | ||
| AhsayOBM must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system. AhsayOBM must be installed on the following Windows Operating Systems: | AhsayOBM must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system. AhsayOBM must be installed on the following Windows Operating Systems: | ||
| - | | Windows 2012 | Windows 2012 R2 | Windows 2016 | | + | | Windows 2012 | Windows 2012 R2 | Windows 2016 | Windows 2019 | |
| - | | Windows 8 | Windows 8.1 | Windows 10 | | + | | Windows 8 | Windows 8.1 | Windows 10 | | |
| === Temporary Directory Requirement === | === Temporary Directory Requirement === | ||
| - | For Hyper-V 2008 and 2012 in both Non-Cluster and Cluster environment, the temporary directory __must be__ set to a local drive. | + | 1 . For Hyper-V server 2008 / 2008 R2 / 2012 / 2012 R2 / 2016 / 2019 in a Non Cluster environment, the temporary directory must be set to a local drive on the Hyper-V server. |
| - | + | ||
| - | For Hyper-V 2016 or above in a Non-Cluster environment, the temporary directory can be set to a local drive, network drive or a cluster storage. | + | |
| - | For Hyper-V 2016 or above in a Cluster environment, the temporary directory must be set to a network drive or cluster storage accessible to all cluster members. | + | 2. For Hyper-V server in Failover Cluster environment: |
| + | - Hyper-V server 2008 / 2008 R2 and 2012 / 2012 R2 the temporary directory must be set to a local drive of the cluster node. | ||
| + | - Hyper-V server 2016 / 2019 the temporary directory must be set to the Cluster Shared Volume (CSV). | ||
| The temporary directory should have at least the same available size as the guest VM to be restored. | The temporary directory should have at least the same available size as the guest VM to be restored. | ||
| Line 458: | Line 466: | ||
| One spare drive letter must be available on the Windows machine for the granular restore process, as the VHD virtual disk is mounted on Windows as a logical drive. AhsayOBM will automatically take the next available drive letter in alphabetical order for the mounted virtual disk. | One spare drive letter must be available on the Windows machine for the granular restore process, as the VHD virtual disk is mounted on Windows as a logical drive. AhsayOBM will automatically take the next available drive letter in alphabetical order for the mounted virtual disk. | ||
| <WRAP info> | <WRAP info> | ||
| - | 1. The Windows drive letters A, B, and C are not used by granular restore. | + | 1. The Windows drive letters A, B, and C are not used by granular restore. \\ |
| 2. The granular restore assigned drive letter(s) will be released once you exit from AhsayOBM UI. | 2. The granular restore assigned drive letter(s) will be released once you exit from AhsayOBM UI. | ||
| </WRAP> | </WRAP> | ||
public/microsoft_hyper-v.1568021008.txt.gz · Last modified: 2019/09/09 17:23 by ronnie.chan