ADSM-L

Re: [ADSM-L] Continuity of Data Backup

2007-05-17 18:18:16
Subject: Re: [ADSM-L] Continuity of Data Backup
From: Stuart Lamble <adsm AT CAROUSEL.ITS.MONASH.EDU DOT AU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 18 May 2007 08:20:46 +1000
On 18/05/2007, at 5:01 AM, Avy Wong wrote:

Hello,
      We have two instances TSM_A and TSM_B, Currently we want to
move some
nodes  from TSM_A to TSM_B.  Once the nodes are moved to TSM_B, the
filespaces will be backed up over TSM_B. Is there a way to keep
continuity
of the backed up data ? Do I need to move the backed up data of
those nodes
from TSM_A to TSM_B? How do I go about it? Thank you.

Easiest way to go about this would be to do an EXPORT NODE between
instances, assuming a high speed link between the two instances. If
the link between the two instances is slow (meaning "less than the
streaming read rate of the tape drives", or if the importing server
is unable to write as fast as the tape drives can read), you'd
probably be better off doing the export to a file storage pool,
copying the exported files over to the other server, and importing
them (tedious in the extreme, and needs a large chunk of temporary
disk space, but ... well ...)

Alternatively, if you don't have any important archived data for the
nodes in question, you can just cut them over to the new instance,
take the hit of the one-time full increment, and remove them from the
original instance at some appropriate time, according to the
retention policies of the company. This assumes you have enough tape
storage space to take the short-term hit.

Cheers.

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