Yeah, I've run into that before. It's actually not really netware's
fault. They have a switch in the SMS modules so that backup software
can tell SMS to force an uncompress of files before they get backed up.
That way, the files can get restored anywhere. Arcserve, for instance,
supports this.
It would be nice **HINT HINT IBM**, if the TSM netware client also
supported it. As it stands now, in a disaster situation, we'd have to
remember what type of volumes each server had (NSS, TFS, compressed,
uncompressed), and recreate them EXACTLY, before we'd be able to restore
anything. Yes, it's in our documentation, but still.Yuck.
At any rate, I don't think that's the problem here, as the files I'm
interested in are not getting compressed. Compression's turned on at
the volume level, but only 244K is actually being compressed on the
entire drive. The dsmsched.log, by the way, just says File
blah\blah.bla exists, skipping for everything. It completes, and
seems to think everything is fine.
--Troy
[EMAIL PROTECTED] 6/29/2004 10:54:22 AM
NetWare is notorious for not allowing files backed up with NSS or
compressed volumes to restore to volumes that are otherwise. Try
running
the process manually and see what happens, and also take a look at the
schedule log dsmsched.log.
--
Mark Stapleton
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Troy Frank
Sent: Tuesday, June 29, 2004 9:23 AM
To: [EMAIL PROTECTED]
Subject: Scheduled restore not working
I've got a schedule that backups up certain ServerA directories at
noon. Another schedule is supposed to then restore those
directories to
ServerB at 1PM. The restore seems to be going to ServerA ,
instead of
ServerB. Server A B are both Netware6. However, serverA is
Traditional Volumes, and serverB is NSS volumes.
In the web administration for TSM the restore looks like this
(abbreviated)...
Action - Restore
Options - -ifnewer -subdir=yes
Objects - Vol1:\data\share\* serverB/vol1:\data\
I also tried it with different variations of quotes/no quotes around
the Objects, which didn't seem to matter. Both schedules, the backup
and the restore, are associated with ServerA.
Troy
UW Medical Foundation
Confidentiality Notice follows:
The information in this message (and the documents attached to
it, if any)
is confidential and may be legally privileged. It is intended
solely for
the addressee. Access to this message by anyone else is
unauthorized. If
you are not the intended recipient, any disclosure, copying,
distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may
have
created and notify me immediately by replying to this email. Thank
you.
Confidentiality Notice follows:
The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.
