Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

VOLSNAP ERROR 36

Created: 01 Aug 2011 • Updated: 02 Aug 2011 | 1 comment
nutshell's picture
This issue has been solved. See solution.

Hi Folks,

I am using Backup Exec 2010R2 on Windows Server 2008R2. The server uses a FC-Connection to connect to an IBM-DS-3400.

Here's my Diskconfig:

Driveletter/ Size/ Free Space/ Remark

C:/97GB/57GB/ Systemdrive local

D:/38GB/33GB/BE-Programdirectory local

F:/12,7TB/3,7TB/Backuplocation fiberchannel

When I make a Full-Backup of F: the job fails. In the System-eventlog I found the error Source Volsnap, Eventid:36; The shadow copies of volume <F:> were aborted because the shadow copy storage could not grow due to a user imposed limit.

Here is the result of the command vssadmin list shadowstorage: (german)

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2005 Microsoft Corp.

Schattenkopie-Speicherassoziation
   Fr Volume: (F:)\\?\Volume{6c40210f-e947-4285-9c26-007d626dd5df}\
   Schattenkopie-Speichervolume: (E:)\\?\Volume{fb4942bd-c7e4-4e14-802e-d4cf9d393794}\
   Verwendeter Schattenkopie-Speicherbereich: 513.688 MB (1%)
   Zugewiesener Schattenkopie-Speicherbereich: 1.27 GB (3%)
   Max. Schattenkopie-Speicherbereich: 19.531 GB (51%)

I wonder if it could help to resize the Shadowstorage with this command:

vssadmin add shadowstorage /for=f: /on=e: /maxsize=80%

Because of the significant difference in size between F: and E: I think the problem with still exist.

Is the only chance to eleminate this error to add more diskspace?

Thanks to all who spend some time on this!

Background:

Before I get the volsnap error 36 I received the error volsnap 25 which indicates corrupt data. I performed a chkdsk on F: but now the I receive a Volsnap 36.

Greetings nutshell

Comments 1 CommentJump to latest comment

nutshell's picture

Hi folks,

actual I was able to solve the volsnap error. Here are the commands that helped me out:

;Deleting old Shadows on Drive F: (nesseccary to delete the whole Shadowstorage)

vssadmin delete shadows /for=f:

;Deleting the Shadowstorage for Drive F: that existed on Drive E:

vssadmin delete shadowstorage /for=f: /on=e:

 ;Creating a new Shadowstorage with enough space on the same Drive

vssadmin add shadowstorage /for=f: /on=f: /maxsize=10%

One less problem to worry about ...

Greeting nutshell

SOLUTION