>strange problem: We have to move several GB of HSM managed data of Server
>A to a HSM managed filesystem of server B. Server A and Server B are on
>different locations, connected via just a 4 Mbit link.
>So there's a question:
>Is there a possibility to only transfer the stub files, export the
>files/database to the 3490Es and then recreate the data and datebase by
>import on the remote site?
>Such an idea sounds better to me than creating tar or cpio files on tapes,
>shipping and reading the the data on the remote site, which causes backups
>to be done and only after backups, the data is able to be migrated ...
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.
Another approach might be to perform a cross-site restore to populate the HSM
file system at the new site, via dsmc restore -VIRTUALNodename=_________,
say over a 3-day holiday weekend or the like. The relatively slow datacomm
link speed works to your advantage in giving HSM time to do dsmreconcile and
migration out of the file system to make room for the incoming populace.
Richard Sims, BU