Sunteți pe pagina 1din 2

Hyper-V Guest processing skipped (check guest OS VSS state and integration compo nents version) KB ID: 1855

Product: Veeam Backup & Replication Version: 7.x Published: 2014-02-13 Created: 2014-02-12 Last Modified: 2014-04-10 Challenge: Guest VMs will fail to engage VSS when application-aware image processing is ena bled generating an error: Error Guest processing skipped (check guest OS VSS state and integration com ponents version) (System.Exception) Cause: This issue has multiple potential causes, usually related to the Integration Ser vices version of the failing guest server. This issue occurs when Application-Aw are image processing is utilized in the Backup or Replication job settings for t ransactional quiescence using Microsoft VSS Solution: Integration Services Make sure integration services are up to date. The Hyper-V Integration Services log in the event viewer of the Hyper-V host that maintains the failing VM. Look for the name of the failing server with any error events referencing the integr ation components being out of date. The following is an example of the event tex t. Hyper-V Volume Shadow Copy Requestor connected to virtual machine `VM-Name', but the version does not match the version expected by Hyper-V (Virtual machine ID). Fr amework version: Negotiated (3.0) - Expected (3.0); Message version: Negotiated (3.0) - Expected (4.0). This is an unsupported configuration. This means that te chnical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual m achine and select Insert Integration Services Setup Disk from the Action menu. If any Integration Service components are listed as out of date, update them on the guest server by following the Steps listed below. Please note this process a pplies to Windows Server 2008 R2, Server 2012 and Server 2012 R2 Server 2012 http://technet.microsoft.com/en-us/library/hh846766.aspx#BKM K_step4 Server 2008 R2 http://technet.microsoft.com/en-us/library/ee207413(v=WS. 10).aspx To determine the Integration services version on the guest: 2008R2: On the Hyper-V host server, browse to C:\windows\system32\vmms.e xe > open the proprieties of the file and go to the `details' tab. 2012 & 2012 R2: Run this powershell command on the host containing the V Ms as Administrator: o Get-VM | ft Name, IntegrationServicesVersion User-added image Guest OS Ensure Guest OS is running on the latest Windows service pack

Check the Shadow Storage on the guest using an administrative command prompt : vssadmin list shadowstorage Ensure that the `For Volume:' and `Shadow Copy Storage Volume:' values are the same for all partitions. User-added image Ensure the guest server does not contain any dynamic disks. Dynamic disks ca nnot utilize VSS and be backed up live. All of the Virtual machine volumes must be formatted with NTFS. In the case of a file server the Windows server 2012 ReFS Resilient File System is also accept able. If the guest OS has a system reserved partition, verify that it has at least 42MB of free space. If less than 42MB is free, test if a windows system state b ackup allows a shadow copy. User-added image Ensure the Hyper-V Shadow Copy Requestor service is started on the Guest. Ensure the guest has a SCSI controller attached in the VM settings (can be a ccessed in Hyper-V Manager or Failover Cluster Manager). There doesn't have to be a disk on the controller but it must be present. The error will present itself in the Hyper-V VMMS > Admin Event log. Example: The virtual machine Vm-Name cannot be hot backed up since it has no SCSI contr ollers attached. Please add one or more SCSI controllers to the virtual machine before performing a backup. (Virtual machine ID). Examine the Virtual Machine settings and verify the Backup (Volume Snapshot) integration service is enabled. Example: User-added image If the VM Guest OS is 2012 (R2) and the Host is 2008R2, examine the Guest OS Application Event logs for errors with source: vmicvss and Event ID: 13. If thi s error is present, add the DWORD ScopeSnapshots with a value of 0, in the registr y of the Key HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SystemRestore\