Oops.. forgot to mention that.. yeah. we did a restore to a specific
location, with the default path setting. It does look like it is just
reading through the entire tape. This was a backupset of a single
filespace, not everything on the server. So I would hope that it is
merely file/folders on the tape, and nothing fancy.
However (and not to derail my initial plea for help), how can the restore
process on my NT server (test box) force a restore TO my Netware server
(production box) across the net work? That entire last statement of yours
concerns me. I didn't think that was possible, but perhaps I am
misinterpreting what you mean there.
Ted Byrne <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/29/2003 11:52 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Fax to:
Subject: Re: BackupSet creativity
Todd,
I'm guessing that you will eventually end up with an error message stating
that there was no match found, or something to that effect. It may take
a
long time to get to that point. Backupsets can be very slow to process;
you typically wind up reading through the entire tape before the command
completes (or errors out).
There may also be inherent client compatibility issues that will prevent
this from working at all. For one thing, the filespace naming format is
completely different between NT and Netware.
If you did not specify a destination for the restore, there will be no
filespace/drive that matches the source on the server that you are running
the restore from.
It's always a good idea to specify a destination on a restore like this,
anyway - prevents nasty things like overwriting data on the production
server across the network, rather than restoring data to the test box that
the restore is running on.
Ted
At 10:23 AM 9/29/2003 -0500, you wrote:
>Although this shouldn't matter, I am running TSM 5.1.7.1 on AIX 4.3.3.
>
>We are moving a large number and size of files from a Netware server to
an
>NT server, and I am trying to come up with a way to help the process so
we
>don't have to use a workstation to copy files from a Netware mount to a
>Windows mount (which really slows things down because the data has to
>travel from the Netware server to the workstation and then to the NT
>server all on one network connection).
>
>I can't give client access rights to an NT server for Netware backups
>because of the file/folder rights/properties/attributes issues. So, my
>bright idea was to generate a backupset of the Netware volume to the TSM
>server, delete the backup set, define that tape volume to the NT server
as
>a backup set, and restore the data from TSM (my understanding is a
>backupset is unencrypted backups with no rights/properties information...
>just files and folders, perhaps readonly, hidden etc attributes
included).
> The generate backupset went well (after I used move nodedata to place
all
>the files on one tape). The delete and define had no noticeable issues.
>We are trying to do the restore of the backupset to the NT server now,
but
>nothing is moving. The session started only has 4.5K sent and 694bytes
>rcv'd. It has been sitting like that for 20 minutes. I visually checked
>the tape drive, and the light is flashing as if the drive is doing
>something (LTO library). The NT admin verifies that there are no
>folders/files restored.
>
>Was this a pipe dream to begin with?
