Yes, your explanation is more or less correct. In addition, even if we
attempted to put the data back on a different file system, some of it just
wouldn't be understandable. For example, a lot of Windows files have
multiple streams of data ("named streams"), a concept that is foreign, as
far as I know, to most non-Windows systems (Mac does have a similar
concept with a different implementation). Another example: NetWare backup
objects are wrapped in the Novell-proprietary SIDF format (see my earlier
response on this thread) so that other OS's wouldn't know how to take them
apart.

We have studied this matter on several occasions, but for a number of
reasons, this capability just isn't feasible/practical.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Coats, Jack" <Jack.Coats AT BANKSTERLING DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/07/2003 14:40
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: restore to a different node (part 2)



Mark,
        Not that is can't be done, but from my experience and asking on
the
list, doing cross system architecture restores are no possible.
        I hope you find that I am incorrect.

        Why?  The simplified basics are that the details of the security,
permissions, allocation, etc, information is stored as a glob in the TSM
database, not as something queriable.  So if the file system you are
restoring to is not of a 'close enough' type of file system as what the
files (and the globbed data) came from, there is not a possibility that
the
restored file system information will be useable by the restored system.
        Does that make sense at all?  [If some IBMers can help confirm /
deny my understanding, it might help us all out].

        We have even been trying to restore Novel 4.11 data on Novel 5
client, and have not been able to accomplish that.

        Restoring Windows to UNIX or Novell (or other
combination/permutation) all seem to have the same issues.   Most UNIX of
different flavors will restore to other UNIX properly (i.e. Solaris
to/from
Linux), but not Linux to Windows).  At least that is my experience.

> -----Original Message-----
> From: Mark Hayden [SMTP:MHayden AT EPA.STATE.IL DOT US]
> Sent: Monday, April 07, 2003 4:26 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      restore to a different node (part 2)
>
> I did try the SET ACCESS command and it worked, but when trying to
> restore from Netware to Windows XP workstation, recieved TSA500 errors.
> It was looking for TSA500.NLM on the Windows workstation, which is not
> going to be there. Is there another way to do this restore??????
>
>
> Hi all, I know you can restore to a different node, but what we are
> doing is trying to restore from a NetWare server to a Windows 2000
> workstation. I know that you can set access to another node, but is this
> the easiest way to do this? We are restoring about 80 Gb and was looking
> for a better way, or if there is a problem restoring to a different
> platform. Please advise.
>
> PS. We are TSM 5.1.5 Server and clients...
>
>  Thanks
>
> Thanks, Mark Hayden
> Informations Systems Analyst
> E-Mail:  MHayden AT epa.state.il DOT us