Santiago videla
asked on
Is safe to take a TSM Backup without snapshot option? (tsm 6.4 - 2008 r2 wintel server)
Hi Everyone.
I have a recursive backup error.:
ANS0361I DIAG: GetRootAttrib(): Root directory \\?\GLOBALROOT\Device\Hard diskVolume ShadowCopy 2461\ not found
ANS1999E Incremental processing of '\\hostxx\e$\mountxx\vol1' stopped.
ANS1999E Incremental processing of '\\hostxx\e$\mountxx\vol2' stopped.
ANS5056E The specified directory path could not be found.
ANS1512E Scheduled event 'XXXX' failed. Return code = 12.
IBM documentation sugest do not use the snapshot: by setting client option "snapshotproviderfs=none.
My question is: is this option safe? what could be the consecuenses (good or bad) for my backups?
Thanks in advance.
Santiago.
I have a recursive backup error.:
ANS0361I DIAG: GetRootAttrib(): Root directory \\?\GLOBALROOT\Device\Hard
ANS1999E Incremental processing of '\\hostxx\e$\mountxx\vol1'
ANS1999E Incremental processing of '\\hostxx\e$\mountxx\vol2'
ANS5056E The specified directory path could not be found.
ANS1512E Scheduled event 'XXXX' failed. Return code = 12.
IBM documentation sugest do not use the snapshot: by setting client option "snapshotproviderfs=none.
My question is: is this option safe? what could be the consecuenses (good or bad) for my backups?
Thanks in advance.
Santiago.
ASKER
WMP,
Thanks for your help. the volsnap 33 are not present on the event log instead i have this:
Volsnap 36 The shadow copies of volume D: were aborted because the shadow copy storage could not grow due to a user imposed limit.
Just one more question: what do you mean with "splitting my large domain backup in several parts" ? should i create diferent schedules to take diferent segments of data? or Windows experts should make diferent partitions with less data?
Thanks in advance
Thanks for your help. the volsnap 33 are not present on the event log instead i have this:
Volsnap 36 The shadow copies of volume D: were aborted because the shadow copy storage could not grow due to a user imposed limit.
Just one more question: what do you mean with "splitting my large domain backup in several parts" ? should i create diferent schedules to take diferent segments of data? or Windows experts should make diferent partitions with less data?
Thanks in advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
WMP,
Thanks a lot for your amazing help.
Santiago.
Thanks a lot for your amazing help.
Santiago.
Please do not confuse these files with locked Windows system files, such as the Windows system state. The TSM client has its own mechanism (BACKUP SYSTEMSTATE or the option " include.systemstate ..." in dsm.opt) to safely backup these entities.
So please find out if you have applications running which use to lock their files.
If in doubt consult the respective docs.
If there are no such applications then using "snapshotproviderfs=none" should be safe.
On the other hand, if there are such applications try to find out if you can quiesce them during the backup, for example by means of pre- and postschedule commands.
Since the error messages seem to indicate that the shadow copy storage location might have too few space (do you see "volsnap 33" messages in the Windows system event log?), you could consider splitting your large domain backup in several parts (as recommended by IBM), or you could try to enlarge the shadow copy space - but please don't ask me how this could be done, I'm not at all a Windows expert.