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

Activity on a volume is preventing all volumes from being snapped

Created: 03 Jul 2009 • Updated: 22 May 2010 | 8 comments
T35216's picture

Hi All,
I am having problems with a job consistently failing with the following error.

V-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
VSS Snapshot error. Activity on a volume is preventing all volumes from being snapped. Try selecting the option 'Process logical volumes for backup, one at a time' , and then run the job again.
 
I am not using AOFO and this error is  constantly being generated by 2 win2k3 server, one a dc the other the backup server.  I have gone through the following document in an effort to resolve but no  joy.

http://seer.entsupport.symantec.com/docs/312068.htm

Any help would be appreciated.

Regards,
Peter

Discussion Filed Under:

Comments 8 CommentsJump to latest comment

Masti24by7's picture

Hi,

please check the option Process logical volumes one at time is selected or not.

You can find that option in Job properties | Advance open File |

process logical volume one at a time.

If the option is not selected please select the option and rerun the job....

Dev T's picture

Hello Peter,

The Shadow Copy Componant will by default use VSS for Backing up.

The Volume Shadow Copy Service is not able to quice the Volume at the time of backups as its throwing the error.

There are many reasons for the same, One of the Reasons is high activity on the volume, secondly; Unstability of the VSS Writers and many more.

One of the resolutions :
1  : Install the VSS rollup Patch http://support.microsoft.com/kb/940349 (Reboot Required) on both the 2003
      Servers. This Patch is applicable only Windows SP2 is installed.

2  : Open the Job Properties...Go to Resource Order and Move the "Shadow Copy Componants" at the TOP.

Please let me know the results.

Its a best practice to have a "Support Contract" with Symantec...
 

T35216's picture

Hi DevT
I cannot make the Shadow Copy Components first in the resource order, only the drives can have their order altered.  i will apply the hotfix you recommend
Regards,
peter

Masti24by7's picture

Hi,

Well tats right you cannot make the move shadowcopy components to the top in the resource order, u can only change the server order in the resource order and not the indivisual resource.

however if you are not able to backup the shadow copy components please check the VSS writer status
using the command promp

command : VSSadmin list writers.

please follow the technote http://support.veritas.com/docs/312068

and reregister the DLL's mentioned in the technote.

and than restart the BE services, that should resolve this issue.

T35216's picture

Thanks masti,
but as originally posted this sometimes clears the issue only for it to resurface later.
Regards,
Peter

RahulG's picture

Please make sure of the following points
1) Make sure you have all the vss patches applied on the server on which you get the above error .
2) make sure there no antivirus scan running at the same time when you have the backup job scheduled

T35216's picture

Hi RahulG,
I have recently installed the above sp to both problematic servers, I intend installing the following as I cannot see it rolled up into sp2

http://support.microsoft.com/kb/940349

Regards,
Peter

RahulG's picture

installing the rollup patch will require a reboot as well .