I have a physical Hyper-V Server (2012R2) running a virtual instance of SLES 11 SP3.
I also have a physical backup server running Veeam B&R 9.
I want to backup the VM using Veeam with Hyper-V quiescence. That works roughly like this:
[LIST=1]
[]Veeam tells Hyper-V it wants to backup SLES
[]Hyper-V tells SLES that it wants to grab a snapshot using VSS integration services
[]SLES uses an agent to prepare a shadow copy and handing it to the Hyper-V VSS
[]Hyper-V returns the backup to Veeam
[/LIST]
My problem is that at step 3 SLES freezes short after initiating the backup and I have no idea how to further troubleshoot the issue!
I made sure package ‘hyper-v’ is installed and up2date:
[QUOTE]BOOSTER:~ # zypper info hyper-v
Refreshing service ‘nu_novell_com’.
Loading repository data…
Reading installed packages…
Information for package hyper-v:
Repository: SLES11-SP3-Updates
Name: hyper-v
Version: 5-0.11.1
Arch: x86_64
Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Support Level: Level 3
Installed: Yes
Status: up-to-date
Installed Size: 46.0 KiB
Summary: Microsoft Hyper-V tools
Description:
This package contains the Microsoft Hyper-V tools.[/QUOTE]
I made sure the system is up2date:
[QUOTE]BOOSTER:~ # zypper lu
Refreshing service ‘nu_novell_com’.
Loading repository data…
Reading installed packages…
No updates found.[/QUOTE]
I made sure the services ar running:
[QUOTE]BOOSTER:~ # /etc/init.d/hv_vss_daemon status
Checking for service Hyper-V VSS daemon running
BOOSTER:~ # /etc/init.d/hv_kvp_daemon status
Checking for service Hyper-V KVP daemon running
BOOSTER:~ #[/QUOTE]
I checked the system usage with “iostat -x 1” before and during the backup. The system is almost idle before and while the backup is running up to the point where it freezes. Which is like after some minutes of it running.
I looked in /var/log/messages but was unable to find anything related to any hyper-v tools, except for that the service mentioned above were started successfully and are running.
I contacted the Veeam technicians and provided all the logs. They try to help me, but basically say that the issue is within the virtual machine and not related to Veeam.
I tried to create a normal snapshot using the Hyper-V console, but that also makes the VM freeze.
Upgrading SLES unfortunately is not an option.