Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Guest VMs will fail to engage VSS when application-aware image processing is enabled generating an error:
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
The solution section of this knowledge base article has been split into four different sections. Please review each step of the following sections.
Click here for a list of Hyper-V Integration Services and their corresponding build numbers.
1. Using Event Viewer
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.
If Hyper-V Integration Services are out of date 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.
2. Using PowerShell (Server 2012 or newer)
Run the follow command in an Administrative PowerShell prompt on the host where the VM that failed to backup resides.
Get-VM | select VMName, IntegrationServicesState
The results of which will list out each present VM, and the state of its integration services.
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 prior to Windows Server 2016 you'll need to manually perform install the update from within the guest operating system. These steps cannot be automated or executed within a Windows PowerShell session.
The following steps and checks are to be performed within the Guest OS of the VM that is failing to backup.
The following steps and checks are to be performed from the Hyper-V host level.
Performing the following will allow you to determine if the steps performed above have corrected the issue without the need to run the Veeam Backup & Replication job again.
Diskshadow /L C:\writers.txt
list writers
Open the file that was created and and locate the VM name in the section for the Hyper-V writer. For each VM there's a "Caption" entry. The caption should read "online" or "child partition", and not "offline" or "saved state".
Recommended hotfixes for Hyper-V servers:
Your feedback has been received and will be reviewed.
Please try again later.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.