Differences

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

--- public:module:hyper-v:requirements [2019/09/09 17:36]
ronnie.chan
+++ public:module:hyper-v:requirements [2019/09/20 15:09] (current)
ronnie.chan
@@ Line 1: / Line 1: @@
 ====== Requirements ======
+----
+{{INLINETOC}} \\
 ===== CloudBacko Pro =====
+----
 <WRAP indent>
 ==== Use the Latest Version ====
+----
 The latest version of CloudBacko Pro must be installed on the Hyper-V server. For Hyper-V Cluster environment the latest version of CloudBacko Pro must be installed on all Cluster nodes.
 ==== Modules ====
+----
 CloudBacko Pro must have sufficient Hyper-V add-on modules (per CPU socket) purchased. Hyper-V Cluster backup sets will require one CloudBacko Pro and Hyper-V module licenses per node.
 ==== Sufficient Storage ====
+----
 Hyper-V guest virtual machines contain three types of virtual disks:
   * Fixed Hard Disk.
@@ Line 22: / Line 28: @@
 ==== Proper Java heap size configured ====
+----
 The default Java heap size setting on CloudBacko Pro is 2048MB, for Hyper-V backups it is highly recommended to increase the Java heap size setting to improve backup and restore performance. (The actual heap size is dependent on amount of free memory available on your Hyper-V server).
@@ Line 29: / Line 36: @@
 ==== Temporary directory ====
+----
 For stand-alone Hyper-V server, CloudBacko Pro uses the temporary folder for storing backup set index files and any incremental or differential delta files generated during a backup job. To ensure optimal backup / restore performance, it should be located on a local drive with plenty of free disk space. It should not be on the Windows system C:\ drive.
 <WRAP prewrap>
@@ Line 37: / Line 45: @@
 ==== CloudBacko Pro UI during Run Direct restore or migration ====
+----
 CloudBacko Pro UI must be running when a guest virtual machine is started using Run Direct Restore or when migration process is running.
 ==== NFS server ====
+----
 Make sure NFS service has started for Run Direct to operate. If the backup destination is located on network drive, the logon account must have sufficient permission to access the network resources.
@@ Line 45: / Line 55: @@
 ==== Administrator permission ====
+----
 The operating system account for setting up the Hyper-V / Hyper-V Cluster backup set must have administrator permission (e.g. administrative to access the cluster storage).
 ==== Windows User Account Control ====
+----
 For Granular Restore, Windows User Account Control (UAC) must be disabled.
 ==== Compression ====
+----
 For local, mapped drive, or removable drive storage destinations with Run Direct enabled, the compression type will always be set to No Compression and data encryption is disabled to ensure optimal backup and restore performance. The backup set compression type and data encryption settings will only be applied to CBS, SFTP/FTP, or Cloud storage destinations.
 ==== Backup whole VM ====
+----
 For ease of restore it is recommended to back up the whole guest machine (all the virtual disks) rather than individual virtual disks.
 </WRAP>
-----
+\\
-===== Hyper-V Server Requirements =====
+===== Hyper-V Server =====
+----
 <WRAP indent>
 ==== Hyper-V management tools ====
+----
 The Hyper-V management tools are installed on the server. For Hyper-V Cluster environments Hyper-V management tools is installed on all Cluster nodes.
@@ Line 68: / Line 84: @@
 ==== Hyper-V services ====
+----
 The Hyper-V services are started on the server. For Hyper-V Cluster environments the Hyper-V services are started on all Cluster nodes.
@@ Line 75: / Line 92: @@
 ==== Hyper-V VSS Writer ====
+----
 The Microsoft Hyper-V VSS Writer is installed and running on the Hyper-V server and the writer state is Stable. This can be verified by running the vssadmin list writers command.
@@ Line 157: / Line 175: @@
 ==== Integration Service ====
+----
   * If Integration services is not installed / updated on a guest virtual machine or the guest operating system is not supported by Integration Services, the corresponding virtual machine will be paused or go into a saved state during the snapshot process for both backup and restore, and resume when the snapshot is completed. Furthermore, the corresponding virtual machine uptime will also be reset to 00:00:00 in the Hyper-V Manager.
@@ Line 208: / Line 227: @@
 ==== Hyper-V 2008 R2 ====
+----
 For Hyper-V 2008 R2 server in order to use Run Direct restore feature the "Microsoft Security Advisory 3033929" security update must be installed.
@@ Line 213: / Line 233: @@
 ==== Run Direct Hyper-V Cluster ====
+----
 For Run Direct Hyper-V Cluster backup sets the storage destination must be accessible by all Hyper-V nodes.
 ==== Hyper-V Cluster ====
+----
 For Hyper-V Cluster backup sets the guest virtual machines must be created and managed by the Failover Cluster Manager.
  </WRAP>
@@ Line 221: / Line 243: @@
 ----
-===== CBT Requirement =====
+===== Changed Block Tracking (CBT) =====
+----
 CBT Cluster Services (CloudBacko Pro) is installed and enabled upon installation / upgrade to version latest version.
@@ Line 266: / Line 289: @@
 . 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 RCT Requirement ====
+==== Windows Server 2016 RCT ====
+----
 <WRAP indent>
-=== RCT Requirement ===
+=== RCT ===
+----
 . CloudBacko Pro would not install CBT Cluster Services (CloudBacko Pro) but use the native built-in RCT (Resilient Change Tracking) feature of Windows server 2016 instead.
@@ Line 296: / Line 321: @@
 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 ===
+=== Guest VM Dependencies ===
+----
 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>
-==== Limitations ====
+\\
-. Backup of guest machines located on a SMB 3.0 shares is not supported.
-. Backup of virtual machine with pass through disk (directly attached physical disk) is not supported.
+===== Granular Restore =====
+----
+<WRAP indent>
+==== Supported Backup Modules ====
+----
+Granular Restore is supported on Hyper-V backup sets created and backed up using CloudBacko Pro installed on a Windows platform with the Granular Restore feature enabled on the backup set.
-. For backup of individual virtual disks, the restored virtual machine does not support the reversion of previous snapshots, if the snapshot contains disks which are not previously backed up by CloudBacko Pro.
+==== 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.
-. A guest virtual machine can only be restored to the Hyper-V server with the same version, e.g. backup of a guest on Hyper-V 2012 R2 server cannot be restored to Hyper-V 2008 R2 Server or vice versa.
+==== Operating System ====
+----
+CloudBacko Pro must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system. CloudBacko Pro must be installed on the following Windows Operating Systems:
+| Windows 2012 | Windows 2012 R2 | Windows 2016 |
+| Windows 8 | Windows 8.1 | Windows 10 |
-. The guest virtual machine will not start up if the virtual disk containing the guest operating system is not restored.
+==== Temporary Directory ====
+----
+For Hyper-V 2008 and 2012 in both Non-Cluster and Cluster environment, the temporary directory __must be__ set to a local drive.
-. Run Direct Restore of VM containing .VHDS shared virtual disk(s) is not supported.
+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.
-. Restore of individual virtual disks is only supported using the Restore raw file option for a virtual disk with no snapshots.
+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.
-<WRAP info>This will require modification of Hyper-V guest configuration files, and this only should be done if you have in-depth knowledge and understanding of Hyper-V, otherwise the guest virtual machine may not startup properly.</WRAP>
+The temporary directory should have at least the same available size as the guest VM to be restored.
-. Replication must be disabled for the VM selected for backup, otherwise there may be following error occurring during backup job:
+==== Available Spare Drive Letter ====
-<code>Failed to backup virtual machine "guest_guid"., Reason = "Failed to take VM snapshot. Error = [CreateVirtualSystemSnapshotV2] Error="The method call failed." (32775)".</code>
+----
+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. CloudBacko Pro 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 CloudBacko Pro UI.
+</WRAP>
-Refer to [[public:5349_failed_to_backup_hyperv_virtual_machine_with_replication_enabled|here]] for more details.
+==== Network ====
+----
+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 CloudBacko Pro 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 CloudBacko Pro 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 cloud storage over the internet can be slow depending on network bandwidth and CBS server load.
 </WRAP>
+</WRAP>
+\\

User Tools

Site Tools

Differences

Page Tools