server 2008 64 bit woes

[bruboy]

Hello

I've searched these forums but can't find an answer for my particular problem.

My 64bit server 2008 VMs are failing to backup - I get errors like these in VCB or network mode:

Code: Select all

Total VM size: 25.00 GB
Processed size: 3.72 KB
Avg. performance rate: 0 KB/s
Backup mode: agentless

Start time: 07/10/2009 22:52:47
End time: 07/10/2009 22:53:46

Releasing VM files
VSSFreezer: -2147212529 Backup job failed.
Discovery phase failed.
Cannot add volumes to the snapshot set.
Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{50f4c08f-a415-11dd-a8e8-806e6f6e6963}\].
Cannot add volume to the set of volumes that should be shadowed.
VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

CreateSnapshot failed, vmRef vm-812, timeout 1800000, snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory False, quiesce True
Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

I have file sharing enabled and can browse and write to \\machine\admin$ which seemed to be a problem for some people.

I can create a quiesced snapshot of this machine in vSphere Client.

Any help appreciated.

[Vitaliy S.]

Hello Alastair,

Could you please clarify what version of Windows Server 2008 you're trying to backup with VSS (SP1,SP2,R2)? Judging by the error It seems like there are some issues with VSS, so please check the following on the Guest OS (Windows 2008):

1. What's the status of Volume Shadow Copy Service (VSS) writer status, you can check that by running the command:
VSSADMIN LIST WRITERS

2. After that please review the output and ensure that the writers are all showing a State of "[1] Stable" and that Last Error is showing "No error."

3. Finally, please check the Event Log at Windows 2008 VM for any VSS error events.

Also, you can open a support case with us by emailing to support@veeam.com, so we could help you with resolving this issue.

Thank you.

[bruboy]

Thanks for the reply - the error was indeed with our VSS.

There weren't any problems in 'VSSADMIN LIST WRITERS' but running 'VSSADMIN LIST PROVIDERS' revealed an old Acronis VSS component was still lurking in our systems.

Removing any references to it via regedit and rebooting has resolved the problem (see also here: http://www.wilderssecurity.com/showthread.php?p=855502).

Cheers

BB

[Gostev]

Thanks a lot for updating the topic with the resolution!