afokkema Windows

Event ID: 7001 VSS


image

After extending a VMDK file from a Windows file server. The following Event ID entered the Application log:

image

In the print screen above, you see a VSSVolumeGUID. You can check with the vssadmin command which volumes are active.

Open a command prompt en run the commando: vssadmin list volumes

image

As you can see in the previous print screen, the volume \\?\Volume{df695619-3a35-11de-a195-806e6f6e6963}\ doesn’t exist anymore.

So how can I remove this error? The solution is simple, open the Scheduled Tasks folder in the Control Panel and remove the ShadowCopyVolume task with the VSSVolumeGUID that doesn’t exist anymore.

image

Source: KB833779

Advertisement
afokkema Veeam

Veeam: Snapshot creation failed: Could not quiesce file system


 

A couple of days ago, I was testing with Veeam backup and a new created VM. The backup stops with the following error:

image

In the Veeam Backup release notes (veeam_backup_2.0.1_release_notes.pdf) and the known errors section, you’ll find the following text:

If you attempt to backup a VM with VMware Tools VSS support module installed with Veeam Backup job having VSS option enabled, the backup would fail with the following error: VCB error: Error: Other error encountered: Snapshot creation failed: Could not quiesce file system. An error occurred, cleaning up…. To resolve this, disable VMware Tools quiescence in the backup job properties, or uninstall VSS support module.

So I checked de VM and uninstalled the VSS option.

Go to Control Panel –> Add/Remove Programs –> VMware Tools. The VMware Tools Setup starts and in this screen press modify.

image

Disable the VSS Support feature in the VMware Tools.

image

Finish the setup wizard and reboot the VM.

 

After a reboot, the following error might popup:

image

The fix was a little bit funny. When I pressed the right mouse button on My Computer or any other directory, the Symantec Antivirus installer starts with a repair job.

image

After the repair job is done and the VM is back online after a reboot, the VM acts normal again :-S