AW: Drive in DOMAIN, but not backed up
I had such issue once,
my Q: drive had access rights set for administrator
but no rights at all for user "system".
Becuase the tsm scheduler run under system,
it could not see the drive at all so it neither
backed it up nor reported an error.
Von: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
Gesendet: Freitag, 02. April 2004 20:44
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Drive in DOMAIN, but not backed up
TSM Server 22.214.171.124 on Windows 2000
TSM Client 126.96.36.199 on Windows 2000
This client has a preschedule command to mount a filesystem. It's actually a
SNAPDRIVE on a Netapp appliance. The script runs CC=0 and is supposed to
mount the drive as Q:. The DSM.OPT file specifies DOMAIN Q:, but the last
incremental backup of that filesystem is listed as 3/8/04.
I thought that if you specified a domain and it wasn't available, you would
get an error on the backup?
There are no messages in the dsmerror.log file, and it's running with -QUIET
so there's not much in the DSMSCHED.LOG. I have changed it to run -VERBOSE
to see exactly what is being backed up.
"Experience is a comb that nature gives us after we go bald." - ??
|<Prev in Thread]
||[Next in Thread>|
- AW: Drive in DOMAIN, but not backed up,
Salak Juraj <=