Snapshot Volume

[hmontalvo]

Dear Veeams,

I have problems using Veeam Backup 3.1.1 the error is:
(The VSS service was restarted but I can not fix this issue).

Releasing VM files VSSFr
eezer: -2147212529
Backup job failed. Di
scovery phase failed. Cannot add volumes to the snapshot set. Cannot add a volume to the snapshot set. Volume name: [\\?\Volume
{03a05626-f
c4c-11dd-92
ab-005056b1
5b02}\]. Cannot add volume to the set of volumes that should be shadowed.
VSS error: VSS_E_UNEXPECTED_PROVI
DER_ERROR. Code:0x8004230f

[Gostev]

Hello Hector, what is the OS version and service pack level, and is it 32-bit or 64-bit?

Also, please try running the following commands from the command prompt in the affected VM, and investigate output for any errors:

Code: Select all

VSSADMIN LIST WRITERS
VSSADMIN LIST PROVIDERS

Thank you!

[hmontalvo]

Hello,

OS Windows 2003 Standard Edition SP2 32 bits.


C:\Documents and Settings\Administrator>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

No items found that satisfy the query.

C:\Documents and Settings\Administrator>VSSADMIN LIST WRITERS
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {83976b8d-fbd6-421a-a953-e27ba0b9be8d}
State: [1] Stable
Last error: No error

Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {b72ee141-ca92-4236-8a08-a22d1d1efc06}
State: [1] Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {4f29816e-851e-4bfc-baa4-eff652704e58}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {856d1f82-eaf5-4253-9e49-c9f58f85fcf6}
State: [1] Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {1ecf1250-1ffa-4fac-9b88-336c2eb16eea}
State: [1] Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {914477bc-d287-499f-bbd2-e0be675d29ef}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {c0345f4f-1150-4675-a39c-1bd4b2ba8c12}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {94493061-2cd2-4c6b-92c2-32cf7920d5fc}
State: [1] Stable
Last error: No error


C:\Documents and Settings\Administrator>VSSADMIN LIST PROVIDERS
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Symantec Software VSS Provider'
Provider type: Software
Provider Id: {262b716e-bb23-41b5-aaef-e2c15e767167}
Version: 1.0

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7

Thanks!

[Vitaliy S.]

Hello Hector,

Please have a look at the following topic for the resolution:
http://www.veeam.com/forums/viewtopic.php?f=2&t=1924

Hope it helps. Thank you.

[Gostev]

That's what I thought. We had reports before when various 3rd party backup VSS providers were causing all sorts of VSS freeze issues. Please remove Symatec software from this computer, and try again - I am 99% sure that Symantec Software VSS Provider is what is causing this issue.

[Gostev]

Nooo I've been beaten by Vitaly again

[hmontalvo]

Dear gurus, =)

I have removed BESR from my server and now all is ok!!

Thanks again!

[Gostev]

No problems. This is exactly why Veeam Backup does not deploy persistent VSS agent on all VMs, and instead automatically pushes small temporary agent to VM at the time of freeze, removing it immediately afterwards. We do it to keep VM "clean" from our agents most of the time, so that other products do not complain about "that 3rd party agent from Veeam" preventing something.