ADSM-L

Re: HSM Migration Problems

2006-10-12 07:32:15
Subject: Re: HSM Migration Problems
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 12 Oct 2006 07:30:26 -0400
On Oct 12, 2006, at 4:39 AM, Timo Scheller wrote:

Problem: HSM does a restore of the whole file, not the stubfile.
What maybe caused the problem? And how do we get only the
stubfiles back?

There is no problem, and the effect is documented several places in
the HSM manual.

You are moving the contents of an established JFS, HSM-managed file
system to a new computer and JFS2 file system...new to TSM.  You
cannot expect to restore and use stub files because there is no file
data in the TSM server storage pool for that node and file system for
the stub file to "point to".

The only "easy" way to accomplish such a file system transfer is if
you have the opportunity to perform a Rename Node, as where a new
computer of comparable type and operating system is taking over the
workload and data of an outdated computer; or the new computer
assumes the identity of the old computer.  Other than that, you are
faced with the task of fully repopulating the new computer's file
systems by somehow transferring the old data, where full-file
restoral is the most realistic means...performed in a staged manner
so as to give HSM time to migrate the new data to the TSM storage
pool, to make room for more data.  Moving HSM data is no fun.

    Richard Sims

<Prev in Thread] Current Thread [Next in Thread>