Video Screencast Help

volume snapshots

Created: 11 Aug 2012 • Updated: 12 Aug 2012 | 5 comments
This issue has been solved. See solution.

 

11/2012 19:06:51 - Warning bpbrm (pid=5768) from client win23: WRN - can't open directory: E:\esp\data\data_fixml\Set_0070e5 (WIN32 2: The system cannot find the file specified. )
08/11/2012 19:06:51 - Warning bpbrm (pid=5768) from client win23: WRN - Snapshot Error: will continue backup without any volume snapshots
08/11/2012 19:06:51 - Error bpbrm (pid=5768) from client win23: ERR - Snapshot Error while opening directory: GLOBALROOT\Device\HarddiskVolumeShadowCopy156\esp\data\data_fixml\Set_0070e5
08/12/2012 00:36:46 - Error bpbrm (pid=5768) from client win23: ERR - failure reading file: E:\esp\var\log\indexer\index_producer_3.log (WIN32 13: The data is invalid. )
 
Backup is completing with error 1.
 
What the above logs means.and how to correct this.

Comments 5 CommentsJump to latest comment

NIKHIL2346565959's picture

We have disable snapshot and continue settings on this client.

Marianne's picture

WRN - Snapshot Error: will continue backup without any volume snapshots

See my comments in your other post: https://www-secure.symantec.com/connect/forums/snapshot-0#comment-7528001

What the above logs means.and how to correct this.

It means you have to troubleshoot the snapshot provider - normally VSS.

bpfis log as well as VSS errors in Event Viewer on the client are needed to find the reason for the snapshot failure.

Only when the reason for the failure is determined can a solution be found....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

NIKHIL2346565959's picture

 

The shadow copies of volume E: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
 
 
Getting below in the error logs.
Marianne's picture

The error log that you have found gives you the reason for snapshot failure plus recommended solution.
There is too much activity on the volume during backup and not enough space to create snapshot.
Speak to system owner to find out what is on that volume. If database, use agent to backup data and exclude database files from normal MS-Windows policy.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION