Error Guest processing skipped (check guest OS VSS state and integration components version) (System.Exception)
This issue has multiple potential causes, usually related to the Integration Services version of the failing guest server. This issue occurs when Application-Aware image processing is utilized in the Backup or Replication job settings for transactional quiescence using Microsoft VSS
A list of supported Guest OSes for each version of Hyper-V can be found here.
On 2008 R2 hosts, Application-Aware Processing during backups is not supported for guest VMs running Server 2012 R2 or later due to integration components incompatibility.
If the Host is 2008 R2 and the VM Guest OS is 2012:
View the Guest OS Application Event logs for errors with source: vmicvss and Event ID: 13.
If this error is present, open the Registry Editor (regedit) and navigate to: HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SystemRestore\ Within that key, create a new DWORD Name: ScopeSnapshots Value: 0
Note: If the SystemRestore key is not present, you must create it.
The solution section of this knowledge base article has been split into four different sections. Please review each step of the following areas:
Click here for a list of Hyper-V Integration Services and their corresponding build numbers.
How to identify:
This section will provide directions on ensuring the Hyper-V Integration Services are up to date within the Guest OS of the VM that is failing to backup.
Using Event Viewer If Hyper-V Integration Services are outdated, you will find Event ID 4000 within the Hyper-V-Integration section of the Event Viewer on the Hyper-V host where the VM is located.
Using PowerShell (Server 2012 or newer) Run the following command in an Administrative PowerShell prompt on the host where the VM that failed to backup resides.
Get-VM | select VMName,IntegrationServicesState
The results will list each present VM and the state of its integration services.
How to correct:
Note: A reboot of the virtual machine will most likely be required to complete the Integration Services update.
The following information is from the Microsoft page found here.
Install or Update Integration Services
For hosts running Server 2012 R2 or older, you'll need to manually install the update from within the guest operating system. These steps cannot be automated or executed within a Windows PowerShell session.
Open Hyper-V Manager.
Right-click the virtual machine and click Connect.
From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk.
Depending on the guest operating system, you may need to start the installation manually.
After the installation finishes, you may be prompted to restart.
Part 2: Within the Guest
The following steps and checks are to be performed within the Guest OS of the VM that is failing to backup.
Ensure that the latest OS updates are installed.
Ensure that the VSS Storage Area and Volume Match
From an Administrative Command Prompt, run the command ‘VSSUIRUN.exe”
Check the [Settings] for each Volume and ensure that the Volume and the Storage area match.
Ensure there are no Dynamic disk or FAT\FAT32 volumes
Open Disk Management (diskmgmt.msc)
Review the Type and File System columns
VSS is not compatible with Dynamic disks or FAT\FAT32 Note: The VHD(X) that the VM runs off can be dynamic; the volume within the Guest OS cannot.
All volumes must be NTFS or ReFS
Check that the System Reserved partition free space.
System Reserved partition must have more than 42MB of space free.
If less than 42MB is free, try creating a shadow copy for the volume.
Remember to delete the Shadow Copy if it is successful.
Start\Restart the “Hyper-V Volume Shadow Copy Requestor
Open Services (services.msc)
Find the Hyper-V Volume Shadow Copy Requestor service.
If it is Stopped, Start it. (If the service will not start, check in the VM settings under Integration Services, and ensure the “Backup (volume Checkpoint)” option is enabled.)
If it is Running, restart it.
Part 3: VM Configuration
The following steps and checks are to be performed from the Hyper-V host level.
Make sure the VM has a SCSI controller. A SCSI controller must be present, even if there are no devices to use the SCSI controller.
If a SCSI controller is absent, an error will be present in the Hyper-V VMMS > Admin event log. Example:
“The virtual machine ‘Vm-Name’ cannot be hot backed up since it has no SCSI controllers attached. Please add one or more SCSI controllers to the virtual machine before performing a backup. (Virtual machine ID).”
Verify that the “Backup (Volume Snapshot)” option is enabled within the Virtual Machine settings.
Ensure that the virtual machine files (VHD files) are not sitting in the root folder of the CSV, as this may prevent correct snapshot creation due to permission restrictions. We strongly recommend keeping virtual machine files in separate folders. More information regarding this can be found here.
Part 4: Verification
The following steps will allow you to determine if the actions performed above have corrected the issue without the need to run the Veeam Backup & Replication job again.
Perform the following steps on the Hyper-V host the VM is running on.
Open an Administrator Command Prompt.
Run the command:
Diskshadow /L C:\writers.txt
Run the command:
Open the file that was created.
Locate the VM name in the section for the Hyper-V writer. For each VM, there's a "Caption" entry. For Application-Aware Processing to function correctly, the caption must read "online" or "child partition" and not "offline" or "saved state".
To submit feedback regarding this article, please click this link: Send Article Feedback To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Your feedback has been received and will be reviewed.