VSS

[Guest Schmeg]

Windows Server 2003 R2 SP2 with all patches to date.

 

Prior to SP2, no issues. After SP2 some intermittent VSS issues during

backup.

 

BackupExec v11 fully updated fails on shadow copy components and system

state using MS VSS sometimes, sometimes it backs up fine.

 

When it fails I get a VolSnap Event ID 39 that states:

 

When preparing a new volume shadow copy for volume C:, the shadow copy

storage on volume F: could not be located in non-critical space. Consider

using a shadow copy storage volume that does not have any shadow copies.

 

I have tried moving the location of the shadow copy, by default it was on

C:, I moved it to D: where I had 60G free space and then to F: where I have

500G free space. I found a description of a similar event that suggested it

may be a size issue. I also adjust the the maximum size to unlimited.

However, right before the event 39 are two events that say previous shadow

copies were removed to avoid maximum setting. I have it set to no limit

though.

 

Doing a vssadim list writers shows all writers in a [7] failed or [5]

waiting for completion, but last error states no errors. A reboot will clear

the vsswriters back to normal, the backup will then run for some period of

time then before this repeats. ntbackup still works fine though.

 

My vss components all show newer versions than reflected in any of the

various VSS hotfixes with the exception of

http://support.microsoft.com/kb/940252/en-us which relates to a leak. The

reboot clearing the problem for some time period suggests this might be the

case for me, though sometimes it clears on its own without a reboot. Can

anyone tell me what levels and activity one should normally see on the

virtual and private bytes referenced in the that kb.

 

Any other info or suggestions appreciated too!