Differences

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

--- public:microsoft_hyper-v [2018/05/04 16:17]
yuk.cheng
+++ public:microsoft_hyper-v [2019/08/26 11:13]
ronnie.chan
@@ Line 1: / Line 1: @@
-=====Microsoft Hyper-V=====
+====== Microsoft Hyper-V Backup Set ======
-[[public:5071_issue:cannot_restore_a_hyper-v_virtual_machine_with_run_direct_enabled_microsoft_security_advisory_3033929_update_not_installed|ISSUE: Cannot restore a Hyper-V virtual machine with Run Direct enabled (Microsoft Security Advisory 3033929 update not installed)]]
+AhsayOBM allows you to back up individual Guest VMs in your Microsoft Hyper-V Host with the MS Exchange Mail Level Backup Set.
+{{public:ahsay_wiki_hyper-v_backup_set.png?640}}
-[[public:5073_issue:incorrect_error_message_another_backup_job_is_still_running_is_displayed_hyper-v_vm_backup|ISSUE: Incorrect error message 'Another backup job is still running' is displayed (Hyper-V VM backup)]]
+===== System Architecture =====
-[[public:5084_issue:hyper-v_vm_backup_job_cannot_run_to_completion_for_backup_set_with_backup_schedule_disabled|ISSUE: Hyper-V VM backup job cannot run to completion (for backup set with backup schedule disabled)]]
+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:5124_issue:scheduled_continuous_backup_jobs_of_hyper-v_cluster_vm_backup_set_are_not_running_run_scheduled_backup_on_computers_named_setting_is_incorrect|ISSUE: Scheduled / continuous backup jobs of Hyper-V Cluster VM backup set are not running (Run scheduled backup on computers named setting is incorrect)]]
+{{public:content_components_hyperv.png?800}}
-[[public:5175_doc:ahsayobm_v7_user_guide_-_microsoft_hyper-v_backup|DOC: AhsayOBM v7 User Guide - Microsoft Hyper-V Backup & Restore]]
+----
-[[public:5221_fail_to_load_cbt_will_perform_normal_in-file_delta_hyper_v_warning|ISSUE: Hyper-V VM backup job completes with warning - Fail to load CBT, will perform normal in-file delta]]
+===== Requirements =====
-[[public:5227_issue:when_attemtping_a_hyper-v_run_direct_restore_with_failed_to_open_driver:error_system_error_577_has_occurred._windows_cannot_verify_the_digital_signature_for_this_file._error|ISSUE: When attemtping a Hyper-v Run Direct restore with “Failed to open driver: Error = System error 577 has occurred. Windows cannot verify the digital signature for this file." error]]
+==== AhsayOBM ====
-[[public:5251_issue:vhd_mounter_-_operating_system_platform_not_support_error_when_performing_a_granular_restore_on_a_hyper-v_guest_vm|ISSUE: “VHD Mounter - Operating System (Platform Not Support)” error when performing a granular restore on a Hyper-V guest VM]]
+<WRAP indent>
-[[public:5253_issue:vhd_mounter_-_administrator_privilege_no_error_when_performing_a_granular_restore_on_a_hyper-v_guest_vm|ISSUE: "VHD Mounter - Administrator Privilege (No)" error when performing a granular restore on a Hyper-V guest VM]]
+=== Use the Latest Version ===
+The latest version of AhsayOBM must be installed on the Hyper-V server. For Hyper-V Cluster environment the latest version of AhsayOBM must be installed on all Cluster nodes.
-[[public:5254_issue:failed_to_mount_virtual_disk_virtual_disk_name_.vhd_no_valid_partition_found_when_performing_a_granular_restore_on_a_linux_or_unix_guest_vm_on_hyper-v|ISSUE: "Failed to mount virtual disk "%virtual_disk_name%.vhd" (No Valid Partition Found)" when performing a granular restore on a Linux or Unix guest VM on Hyper-V]]
+=== Modules ===
+AhsayOBM user account created on AhsayCBS must have sufficient Hyper-V add-on modules or CPU sockets assigned. Hyper-V Cluster backup sets will require one AhsayOBM license per node.
-[[public:5255_issue:failed_to_list_file_the_volume_does_not_contain_a_recognized_file_system._please_make_sure_that_all_required_file_system_drivers_are_loaded_and_that_the_volume_is_not_corrupted_when_performing_a_granular_restore_on_hyper-v_guest|ISSUE:"Failed to list file (The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted)" when performing a granular restore on Hyper-V guest]]
+{{public:ahsay_wiki_module_hyper-v_requirement_1.png}}
-[[public:5256_issue:volume_shadow_copy_service_error:unexpected_error_querying_for_the_ivsswritercallback_interface._hr_0x80070005_access_is_denied._error_is_shown_in_windows_event_viewer_for_hyper-v_backup_restore_job|ISSUE:"Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied." error is shown in Windows Event viewer for Hyper-V backup/restore job]]
+=== Sufficient Quota ===
+AhsayOBM user account has sufficient quota assigned to accommodate the storage of the guest virtual machines. (Please contact your backup service provider for details).
+Hyper-V guest virtual machines contain three types of virtual disks:
+  * Fixed Hard Disk.
+  * Dynamic Hard Disk.
+  * Differencing Hard Disk.
+When AhsayOBM backs up a Hyper-V guest virtual machines for an initial or subsequent full backup jobs:
+  * Using fixed Hard Disks it will back up the provisioned size, e.g. for a 500GB fixed virtual hard disk 500GB will be backed up to the storage designation.
+  * Using Dynamic Hard Disk or Differencing Hard Disk it will back up the used size, e.g. for a 500GB fixed virtual hard disk, 20GB will backed up to the storage designation if only 20GB are used.
+=== Proper Java heap size configured ===
+The default Java heap size setting on AhsayOBM 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).
+Delta generation of large VHD files is a memory intensive process; therefore, it is recommended that the Java heap size to be at least 2048MB - 4096MB. The actual required Java heap size is subject to various factors including files size, delta mode, backup frequency, etc.
+Refer to this KB article for [[public:8011_faq:how_to_modify_the_java_heap_size_of_ahsayobc|how to configure Java heap size]] on your AhsayOBM.
+=== Temporary directory ===
+For stand-alone Hyper-V server, AhsayOBM 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>
+<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.
+</code>
+</WRAP>
+=== AhsayOBM UI during Run Direct restore or migration ===
+AhsayOBM 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.
+{{public:ahsay_wiki_module_hyper-v_requirement_2.jpg?800}}
+=== 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 ====
+<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.
+{{public:ahsay_wiki_module_hyper-v_requirement_3.jpg?800}}
+=== 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.
+Example: Windows 2008 R2 Hyper-V
+{{public:ahsay_wiki_module_hyper-v_requirement_4.jpg?800}}
+=== 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.
+Example:
+<code>
+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
+</code>
+=== 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.
+  * Installing or updating Integration Services guest virtual machine(s) may require a restart of the guest virtual machine to complete the installation. \\ <WRAP indent>
+    * To install Integration Services
+    * In Hyper-V Manager connect to the guest virtual machine and select Action > Insert Integration Services Setup disk \\ Example: Windows 7 Enterprise guest \\ {{public:ahsay_wiki_module_hyper-v_requirement_5.png?400}}
+    * If the guest operating system supports live virtual machine backup the Backup (volume snapshot) is enabled.  \\ {{public:ahsay_wiki_module_hyper-v_requirement_6.png?800}}
+    * The related Integration Services are running on the guest virtual machine: \\ Example: Windows 7 Enterprise guest \\ {{public:ahsay_wiki_module_hyper-v_requirement_7.png?800}} \\ Example: CentOS 6.4 Linux guest \\ To check if Linux Integration Services is running on the Linux guest: \\ <code> # lsmod | grep hv
+hv_netvsc            23667  0
+hv_utils             7012  0
+hv_storvsc           10022  2
+hv_vmbus             91567  4 hv_netvsc,hv_utils,hid_hyperv,hv_storvsc
+# ps -ef|grep hv
+root       267     2  0 18:07 ?        00:00:00 [hv_vmbus_con/0]
+root       268     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       269     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       270     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       271     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       272     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       273     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       274     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       275     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       276     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root       277     2  0 18:07 ?        00:00:00 [hv_vmbus_ctl/0]
+root      1174     1  0 18:07 ?        00:00:00 /usr/sbin/hv_kvp_daemon
+root      1185     1  0 18:07 ?        00:00:00 /usr/sbin/hv_vss_daemon
+root      1332  1316  0 18:11 pts/0    00:00:00 grep hv
+</code>
+    *  	Please refer to the following articles for further details on: <WRAP indent>
+      * Considerations for backing up and restoring virtual machines \\ [[https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn798286(v=ws.11)]]
+      * Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012  \\ [[https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792028(v=ws.11)]]
+      * Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012 R2  \\ [[https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792027(v=ws.11)]]
+      * Supported Linux and FreeBSD virtual machines for Hyper-V on Windows \\ [[https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows]]
+      * Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V  \\ [[https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-centos-and-red-hat-enterprise-linux-virtual-machines-on-hyper-v]]
+      * Supported Ubuntu virtual machines on Hyper-V  \\ [[https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v]]
+      * Linux Integration Services Version 4.0 for Hyper-V  \\ [[https://rlevchenko.com/2015/08/18/linux-integration-services-version-4-0-for-hyper-v/]]
+      * Managing Hyper-V Integration Services  \\ [[https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/managing_ics]]
+      * 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 ===
+For Hyper-V 2008 R2 server in order to use Run Direct restore feature the "Microsoft Security Advisory 3033929" security update must be installed.
+Please refer to the following KB article from Microsoft for further details: [[https://support.microsoft.com/en-us/kb/3033929]]
+=== 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>
+===== Documentation =====
+  * [[https://www.ahsay.com/download/download_document_v8_obm-user-guide-hyper-v.jsp|Microsoft Hyper-V Backup and Restore Guide]]
+===== Issues =====
+  *  [[public:5071_issue:cannot_restore_a_hyper-v_virtual_machine_with_run_direct_enabled_microsoft_security_advisory_3033929_update_not_installed|Cannot restore a Hyper-V virtual machine with Run Direct enabled (Microsoft Security Advisory 3033929 update not installed)]]
+  * [[public:5073_issue:incorrect_error_message_another_backup_job_is_still_running_is_displayed_hyper-v_vm_backup|Incorrect error message 'Another backup job is still running' is displayed (Hyper-V VM backup)]]
+  * [[public:5084_issue:hyper-v_vm_backup_job_cannot_run_to_completion_for_backup_set_with_backup_schedule_disabled|Hyper-V VM backup job cannot run to completion (for backup set with backup schedule disabled)]]
+  * [[public:5124_scheduled_hyper-v_cluster_vm_backup_are_not_running|Scheduled / continuous backup jobs of Hyper-V Cluster VM backup set are not running (Run scheduled backup on computers named setting is incorrect)]]
+  * [[public:5221_fail_to_load_cbt_will_perform_normal_in-file_delta_hyper_v_warning|Hyper-V VM backup job completes with warning - Fail to load CBT, will perform normal in-file delta]]
+  * [[public:5227_issue:when_attemtping_a_hyper-v_run_direct_restore_with_failed_to_open_driver:error_system_error_577_has_occurred._windows_cannot_verify_the_digital_signature_for_this_file._error|When attemtping a Hyper-v Run Direct restore with “Failed to open driver: Error = System error 577 has occurred. Windows cannot verify the digital signature for this file." error]]
+  * [[public:5251_issue:vhd_mounter_-_operating_system_platform_not_support_error_when_performing_a_granular_restore_on_a_hyper-v_guest_vm|"VHD Mounter - Operating System (Platform Not Support)" error when performing a granular restore on a Hyper-V guest VM]]
+  * [[public:5253_issue:vhd_mounter_-_administrator_privilege_no_error_when_performing_a_granular_restore_on_a_hyper-v_guest_vm"|VHD Mounter - Administrator Privilege (No)" error when performing a granular restore on a Hyper-V guest VM]]
+  * [[public:5254_issue:failed_to_mount_virtual_disk_virtual_disk_name_.vhd_no_valid_partition_found_when_performing_a_granular_restore_on_a_linux_or_unix_guest_vm_on_hyper-v|"Failed to mount virtual disk "%virtual_disk_name%.vhd" (No Valid Partition Found)" when performing a granular restore on a Linux or Unix guest VM on Hyper-V]]
+  * [[public:5255_issue:failed_to_list_file_the_volume_does_not_contain_a_recognized_file_system._please_make_sure_that_all_required_file_system_drivers_are_loaded_and_that_the_volume_is_not_corrupted_when_performing_a_granular_restore_on_hyper-v_guest|"Failed to list file (The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted)" when performing a granular restore on Hyper-V guest]]
+  * [[public:5256_issue:volume_shadow_copy_service_error:unexpected_error_querying_for_the_ivsswritercallback_interface._hr_0x80070005_access_is_denied._error_is_shown_in_windows_event_viewer_for_hyper-v_backup_restore_job|"Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied." error is shown in Windows Event viewer for Hyper-V backup/restore job]]

User Tools

Site Tools

Differences

Page Tools