#1 Global Leader in Data Protection & Ransomware Recovery

Hyper-V Guest processing skipped (check guest OS VSS state and integration components version)

KB ID: 1855
Product: Veeam Backup & Replication
Version: Any
Published: 2014-02-13
Last Modified: 2023-07-11
Languages: DE | FR
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Guest VMs will fail to engage VSS when Application-Aware Processing is enabled, generating the error:

Error Guest processing skipped (check guest OS VSS state and integration components version) (System.Exception)

Cause

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

Solution

Please Note:

  • 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:

  1. Integration Services
  2. Within the Guest
  3. VM Configuration
  4. Verification

Part 1: Integration Services

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.

  1. 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.
    User-added image
  2. 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.
    User-added image
     

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.

  1. Open Hyper-V Manager.
  2. Right-click the virtual machine and click Connect.
    User-added image
  3. From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk.
    User-added image
    Depending on the guest operating system, you may need to start the installation manually.
    User-added image
  4. After the installation finishes, you may be prompted to restart.
    User-added image

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.

  1. Ensure that the latest OS updates are installed.
  2. Ensure that the VSS Storage Area and Volume Match
    1. From an Administrative Command Prompt, run the command ‘VSSUIRUN.exe”
      User-added image
    2. Check the [Settings] for each Volume and ensure that the Volume and the Storage area match.
      User-added image
  3. Ensure there are no Dynamic disk or FAT\FAT32 volumes
    1. Open Disk Management (diskmgmt.msc)
    2. Review the Type and File System columns
    3. 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.
      User-added image
      All volumes must be NTFS or ReFS
  4. Check that the System Reserved partition free space.
    1. System Reserved partition must have more than 42MB of space free.
    2. If less than 42MB is free, try creating a shadow copy for the volume.
      User-added image
    3. Remember to delete the Shadow Copy if it is successful.
  5. Start\Restart the “Hyper-V Volume Shadow Copy Requestor
    1. Open Services (services.msc)
    2. Find the Hyper-V Volume Shadow Copy Requestor service.
    3. 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.)
    4. 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.

  1. 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:
    User-added image
    “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).”
  2. Verify that the “Backup (Volume Snapshot)” option is enabled within the Virtual Machine settings.
    User-added image

    User-added image

  3. 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.

    User-added image

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.

  1. Open an Administrator Command Prompt.
  2. Run the command:
    Diskshadow /L C:\writers.txt
    
    User-added image
  3. Run the command:
    list writers
    
    User-added image
  4. Open the file that was created.
  5. 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

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.