Hi, I'm backing up cifs shares from netapp filers by snapdiff by using a cmd script scheduled by windows scheduler:
-------------
set DSMC="C:\Program Files\Tivoli\TSM\baclient\dsmc.exe"
set LOG="C:\Program Files\Tivoli\TSM\log\backup.log"
set LOG2="C:\Program Files\Tivoli\TSM\log\backupshares.log"
set OPT="C:\Program Files\Tivoli\TSM\baclient\dsm_snapdiff.opt"
net use g: \\netapp04\cifs_shares$ /persistent:no
%DSMC% inc -optfile=%OPT% -snapdiff g: > %LOG2%
net use g: /delete
exit
---------------
Disadvantage of this solution is, of course, I do not see success or failure of the schedule if I have no time to check it manually.
New solution: schedule the job by TSM server:
action: inc
options: -snapdiff -presc="net use g: \\netapp04\cifs_shares$" -postsched="net use g: /delete"
objects: g:
This works fine if I start the TSM client like this: "dsmc sched", but not with dsm scheduler started by windows. What the hell is going wrong...
-------------
set DSMC="C:\Program Files\Tivoli\TSM\baclient\dsmc.exe"
set LOG="C:\Program Files\Tivoli\TSM\log\backup.log"
set LOG2="C:\Program Files\Tivoli\TSM\log\backupshares.log"
set OPT="C:\Program Files\Tivoli\TSM\baclient\dsm_snapdiff.opt"
net use g: \\netapp04\cifs_shares$ /persistent:no
%DSMC% inc -optfile=%OPT% -snapdiff g: > %LOG2%
net use g: /delete
exit
---------------
Disadvantage of this solution is, of course, I do not see success or failure of the schedule if I have no time to check it manually.
New solution: schedule the job by TSM server:
action: inc
options: -snapdiff -presc="net use g: \\netapp04\cifs_shares$" -postsched="net use g: /delete"
objects: g:
This works fine if I start the TSM client like this: "dsmc sched", but not with dsm scheduler started by windows. What the hell is going wrong...
Last edited: