Differences

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

--- public:microsoft_hyper-v [2019/08/16 17:50]
ronnie.chan
+++ public:microsoft_hyper-v [2019/09/09 16:47]
ronnie.chan
@@ Line 8: / Line 8: @@
 The following high level system architecture diagram illustrates the major elements involved in the backup process of a Hyper-V host with AhsayOBM and AhsayCBS.
-{{public:ahsay_wiki_module_hyper-v_architecture_1.png?800}}
+{{public:content_components_hyperv.png?800}}
 ----
@@ Line 14: / Line 14: @@
 ===== Requirements =====
-==== AhsayOBM ====
+==== Hardware Requirement ====
+Refer to this article for the list of hardware requirements for AhsayOBM: [[public:8000_faq:ahsay_hardware_requirement_list_hrl_for_version_8.1_or_above|Ahsay Hardware Requirement List (HRL) for version 8.1 or above]]
+==== Software Requirement ====
+Refer to this article for the list of compatible operating systems and Hyper-V platforms: [[public:8001_faq:ahsay_software_compatibility_list_scl_for_version_8.1_or_above|Ahsay Software Compatibility List (SCL) for version 8.1 or above]]
+==== Antivirus Exclusion Requirement ====
+To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to the [[public:8014_faq:suggestion_on_antivirus_exclusions
+|list of processes and directory paths that should be added to all antivirus software white-list / exclusion list]].
+==== AhsayOBM ====
 <WRAP indent>
@@ Line 74: / Line 83: @@
 </WRAP>
-==== Hyper-V Server ====
+==== Hyper-V Server Requirements ====
 <WRAP indent>
 === Hyper-V management tools ===
@@ Line 169: / Line 178: @@
 </code>
-</WRAP>
 === Integration Service ===
@@ Line 219: / Line 227: @@
       * Hyper-V on Window Server  \\ [[https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-on-windows-server]]
+</WRAP>
+</WRAP>
 === Hyper-V 2008 R2 ===
@@ Line 228: / Line 238: @@
 For Run Direct Hyper-V Cluster backup sets the storage destination must be accessible by all Hyper-V nodes.
-==- Hyper-V Cluster ===
+=== Hyper-V Cluster ===
 For Hyper-V Cluster backup sets the guest virtual machines must be created and managed by the Failover Cluster Manager.
+</WRAP>
+==== Hyper-V Backup Methods ====
+AhsayOBM v8 supports two methods for Hyper-V guest VM backup, VM Snapshot and Saved State.
+<WRAP indent>
+=== VM Snapshot ===
+The VM snapshot method is the preferred backup option, as it supports live guest VM backups. This means guest VM will not be put into a saved state when a VSS snapshot is taken during a backup job. So it will not affect the availability of any applications or services running on the guest VM every time a backup job is performed.
+<WRAP info>If the VM Snapshot method cannot be used, AhsayOBM will automatically use the Saved State method.</WRAP>
+<WRAP indent>
+Requirements
+. The guest VM must be running.
+. Integration services must be enabled on the guest VM.
+. The Hyper-V Volume Shadow Copy Requestor service is running on the guest VM installed with Windows operating system. Please refer to the following article for further details: [[https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/integration-services#hyper-v-volume-shadow-copy-requestor]]
+. For guest VMs installed with Linux / FreeBSD operating systems, the VSS Snapshot daemon is required for live backups, not all Linux / FreeBSD versions support live backup on Hyper-V. For example, only FreeBSD 11.1 supports live backup while for Ubuntu, version 14.04 LTS to 17.04 LTS supports live backups. Please refer to the following article for further details: [[https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-linux-and-freebsd-virtual-machines-for-hyper-v-on-windows]]
+. The guest VM volumes must use a file system which supports the use of VSS snapshots, for example NTFS.
+. The guest VMs snapshot file location must be set to the same volume in the Hyper-V host as the VHD file(s).
+. The guest VM volumes have to reside on basic disks. Dynamic disks cannot be used within the guest VM.
+<WRAP info>Some older Windows operating systems installed on guest VM's which do not support either Integration Services or the Hyper-V Volume Shadow Copy Requestor Service, will not support VM snapshot method, for example, Microsoft Windows 2000, Windows XP, or older Linux/FreeBSD versions. </WRAP>
 </WRAP>
+=== Saved State ===
+If any of the VM Snapshot method requirements cannot be fulfilled, AhsayOBM will automatically use the Save State method. When the Saved State method is used, the guest VM is placed into a saved state while the VSS snapshot is created (effectively shut down), and the duration is dependent on the size of VM and performance of Hyper-V host. The downside is it may affect the availability of any applications or services running on the guest VM every time a backup job is performed.
+</WRAP>
+==== CBT Requirement ====
+CBT Cluster Services (Ahsay Online Backup Manager) is installed and enabled upon installation / upgrade to version AhsayOBM v8.1.0.0 or above.
+{{public:ahsay_wiki_module_hyper-v_requirement_8.png}}
- </WRAP>
+. CBT (Changed Block Tracking) is used to optimize incremental backups of virtual machines by keeping a log of the blocks of data that have changed since the previous snapshot making incremental backups much faster. When AhsayOBM performs a backup, CBT feature can request transmissions of only the blocks that changed since the last backup, or the blocks in use.
+<WRAP info>CBT service is supported on all the backup destinations for AhsayOBM.</WRAP>
+. CBT cluster service is only installed on Windows x64 machine.
+. Check if CBTFilter is enabled.
+Example:
+<WRAP indent>
+i. This can be verified by running the net start CBTFilter command.
+<code>
+C:\Users\Administrator>net start CBTFilter
+The requested service has already been started.
+More help is available by typing NET HELPMSG 2182.
+</code>
+ii. **Note:** For Windows Server 2008 R2, if the following error is displayed
+<code>
+C:\Users\Administrator>net start CBTFilter
+System error 577 has occurred.
+Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrect or damaged, or that might be malicious software from an unknown source.
+</code>
+The issue may be related to the availability of SHA-2 code signing support for Windows Server 2008 R2 ([[https://technet.microsoft.com/en-us/library/security/3033929]]).
+To resolve the issue, install the following patch from Microsoft
+[[https://www.microsoft.com/en-us/download/confirmation.aspx?id=46083]]
+Restart the affected server afterward for AhsayOBM to operate properly.
+</WRAP>
+. CBT Cluster Service and CBTFilter will NOT be installed on Windows Server 2016 where a built-in system called Resilient Change Tracking (RCT) will be used instead. For details of RCT, please refer to Windows Server 2016 and 2019 RCT Requirement.
+==== Windows Server 2016 and 2019 RCT Requirement ====
+<WRAP indent>
+=== RCT Requirement ===
+. AhsayOBM would not install CBT Cluster Services (Ahsay Online Backup Manager) but use the native built-in RCT (Resilient Change Tracking) feature of Windows server 2016 and 2019 instead.
+. The guest virtual machine version in Hyper-V must be 8.0 or above.
+Example:
+<WRAP indent>
+i. This can be verified by using Windows PowerShell.
+<code>
+get–VM | format–table name, version
+</code>
+{{public:ahsay_wiki_module_hyper-v_requirement_9.png?640}}
+ii. If the version is not 8.0 or above, then need to upgrade the virtual machine configuration version.
+<code>
+Update-VMversion <vmname>
+</code>
+{{public:ahsay_wiki_module_hyper-v_requirement_10.png?640}}
+</WRAP>
+Please refer to the following link of Microsoft for details about virtual machine version: [[https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server]]
+=== Guest VM Dependencies Requirements ===
+To get full use of Hyper-V, install the appropriate linux-tools and linux-cloud-tools packages to install tools and daemons, e.g. VSS Snapshot Daemon, for use with virtual machines. Please refer to the following link for the details of requirements for Ubuntu relating to Hyper-V daemons: [[https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v]]
+</WRAP>
 ===== Documentation =====

User Tools

Site Tools

Differences

Page Tools