Continuity of Data Backup

2007-05-17 Thread Avy Wong
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.

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
ext 28164
**
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended 
recipient, or
an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication 
in error,
please notify us immediately by replying to the message and deleting it from 
your
computer.
**


Re: Continuity of Data Backup

2007-05-17 Thread Stuart Lamble

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.


Re: Continuity of Data Backup

2007-05-17 Thread Avy Wong
Stuart ,
Yes. I did thought about exporting the data from TSM_A to TSM_B.
As matter of  fact recently I just did a whole bunch of export nodes to
volumes LTO2. They  were a bunch of obsolete nodes that did not need to
stay on TSM to take up real estate and that exercise was painfully slow. I
have not tried exporting node between two instances. I am hoping that if I
do that it will be faster. Well, I guess I will find out. What you have
told me is very valuable information. Thank you for your help.



Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
ext 28164




Stuart Lamble [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
05/17/2007 06:20 PM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] Continuity of Data Backup






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.



**
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended 
recipient, or
an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication 
in error,
please notify us immediately by replying to the message and deleting it from 
your
computer.
**