Differences

This shows you the differences between two versions of the page.

--- public:microsoft_hyper-v [2019/09/09 17:14]
ronnie.chan [Table]
+++ 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 ======
+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.
@@ Line 63: / Line 65: @@
 <code>
 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>
 </WRAP>
@@ Line 389: / Line 393: @@
 The following steps are taken when a Run Direct restore is initiated:
+<WRAP indent>
 . **Delete Guest Virtual Machine** - AhsayOBM will delete the existing guest virtual machine on the original or alternate location (if applicable).
@@ Line 403: / Line 409: @@
 . **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.
@@ Line 420: / Line 428: @@
 ==== 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 ====
@@ Line 430: / Line 438: @@
 ^ Cons         | **No Encryption and Compression**  - To ensure optimal restore performance, the backup of the guest VM will NOT be encrypted and compressed, therefore, you may have to take this factor in consideration when using this restore method.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | **Slower Recovery** - As the entire guest VM has to be restored before you can access any of it’s file(s) or data, the restore time could be long if the guest VM size is large.\\ **Two Backup Sets and CALs Required** - If you only wish to restore individual files from VM, two separate backup sets are required, one for the VM image and the other for the individual files, and therefore two CALs (client access licenses) are required.  |
+==== Requirements ====
+<WRAP indent>
+=== Supported Backup Modules ===
+Granular restore is supported on Hyper-V backup sets created and backed up using AhsayOBM installed on a Windows platform with the Granular Restore feature enabled on the backup set.
+=== License Requirements ===
+An OpenDirect / Granular restore add-on module license is required per backup set for this feature to work. Contact your backup service provider for more details.
+=== Backup Quota Storage ===
+As compression is not enabled for Granular backup sets, to optimize restore performance, the storage quota required will be higher than non-Granular backup sets. Contact your backup service provider for details.
+=== 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:
+| Windows 2012  | Windows 2012 R2  | Windows 2016  | Windows 2019  |
+| Windows 8     | Windows 8.1      | Windows 10    |               |
+=== Temporary Directory Requirement ===
+. 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 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.
+=== Available Spare Drive Letter ===
+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>
+. The Windows drive letters A, B, and C are not used by granular restore. \\
+. The granular restore assigned drive letter(s) will be released once you exit from AhsayOBM UI.
 </WRAP>
+=== Network Requirements ===
+Recommended minimum network speed is at least 100Mbps download speed.
+The network bandwidth requirements will increase in proportion to the size of the guest VM and or the incremental delta chain length to ensure optimal performance. Working with limited network bandwidth may severely affect the granular restore performance.
+You can use an online network speed test website (e.g. www.speedtest.net) to get an idea of the actual bandwidth of the machine.
+=== Other Dependencies ===
+The following dependencies are required for restore and therefore they are verified by AhsayOBM only when a granular restore is performed. Absence of these dependencies will not affect the backup job but would cause the granular restore to fail.
+  * Microsoft Visual C++ 2015 Redistributable (x86) / (x64) \\ [[https://www.microsoft.com/en-us/download/details.aspx?id=48145]]
+  * Update for Universal C Runtime in Windows \\  [[https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows]]
+=== Permissions ===
+The Windows login account used for installation and operation of the AhsayOBM client machine requires Administrator privileges.
+<WRAP info>
+**Recommendation** - It is recommended that a local destination is added to the backup set for faster granular restore.  Since granular restore of large guest VM from CBS server over the internet can be slow depending on network bandwidth and CBS server load.
+</WRAP>
+</WRAP>

User Tools

Site Tools

Differences

Page Tools