On Tue, 14 Nov 2000, Richard Sims <rbs AT BU DOT EDU> wrote:

Richard,

thanks for your suggestions,

> Andreas - In those circumstances I would consider doing a final backup of
>           the HSM file system(s), then do an EXPort Node of the backup
> FILESpace.  On the receiving TSM server, do an IMport Node to plant the backup
> storage pool, define the HSM file system and HSM storage pool at the new site,
> and then do a full restore with -SUbdir=yes and -RESToremigstate=Yes (which is
> the default) to recreate the directory structure, restore small files, and
> regenerate stub files in the new file system.  (Note that RESToremigstate
> restores only the ADSM record portion of the stub files, and thus you will see
> the stub files have a length of 511 rather than 4096, indicative of there
> being no beginning of the file data in the stub.)
>
> This procedure basically follows the steps you would take to recover an HSM
> file system.  Refer to the HSM manual and the HSM redbook for further detail.

I'm wanting to restore the files into an existing filesystem on Server B
into a directory ~user/from_server_A.

Think I'll do as you suggested and I'm creating a socalled temp HSM
filesystem, restore the data to it, and afterwards, I'm moving the data
into the already existing filesytems on Server B.

Is this a feasible path to do this type of migration?

BTW: We are running space management Interface - Version 3, Release 1,
Level 0.8 on 4.3.3.0

        Thanks a lot

        Andreas

--
Andreas R. Landhaeusser
Andreas R. Landhaeusser
debis Systemhaus Solutions for Research GmbH
Bunsenstr. 10, 37073 Goettingen, Germany, phone: +49 551 709 2379