ADSM-L

Re: [ADSM-L] LTO1/LTO2 to LTO4 migration?

2008-01-09 11:09:16
Subject: Re: [ADSM-L] LTO1/LTO2 to LTO4 migration?
From: William Boyer <bjdboyer AT COMCAST DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 9 Jan 2008 11:07:05 -0500
Creating the "new" copypool on the LTO4 tapes is going to be a big hit at the 
beginning.

Another thing I would do is to rename your existing LTO1/2 stgpools to 
something else, and then when you create the new LTO4 stgpool
call them the same names. That way you don't have to change any of your scripts 
and procedures.

Bill Boyer
"A life? Cool! Where can I download one of those?" - ??


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
David Longo
Sent: Wednesday, January 09, 2008 10:50 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: LTO1/LTO2 to LTO4 migration?

That's correct, one of the real nice things about TSM.

This is basically the same as migrating from any kind of disk pool to any kind 
of tape pool, doesn't matter the media
type/technology.

You do need to remember though that after you have migrated ALL of your onsite 
tape pool and it's offsite copies have been made,
then you need to "delete volume" with discarddata option on the OLD offsite 
pool tapes, or else old tapes will still be there.

DL

>>> "Bell, Charles (Chip)" <Chip.Bell AT BHSALA DOT COM> 1/9/2008 10:28 AM >>>
That sounds great! So to confirm, there are no technical gotchas that are going 
to prevent data movement from one media type
(LTO1/2) ton another (LTO3/4)? Anyone else done this?

Thanks, Bill!

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
William Boyer
Sent: Wednesday, January 09, 2008 9:25 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] LTO1/LTO2 to LTO4 migration?

Just define up your new tape drives/devc/stgpools and then set the NEXTPOOL= on 
your LTO1/LTO2 stgpool(s) to the new LTO3 or LTO4
stgpools. Now just MIGRATE STGPOOL the LTO1/2 over to the LTO4 pool. No need to 
do individual MOVE DATA/NODEDATA. Just let migration
handle it all for you. Cancel it and restart it as you need.

Bill Boyer
"I haven't lost my mind...it's backed up on tape somewhere!" - ??


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Bell, Charles (Chip)
Sent: Wednesday, January 09, 2008 10:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: LTO1/LTO2 to LTO4 migration?

Is it possible to run 'move data' or 'move nodedata' commands from either
LTO1 or LTO2 device class to LTO4? What about from LTO1/2 to LTO3? Has anyone 
done this?



God bless you!!!

Chip Bell
Network Engineer I
IBM Tivoli Certified Deployment Professional

Baptist Health System
Birmingham, AL








-----------------------------------------
Confidentiality Notice:
The information contained in this email message is privileged and confidential 
information and intended only for the use of the
individual or entity named in the address. If you are not the intended 
recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly prohibited. If you 
received this information in error, please notify the
sender and delete this information from your computer and retain no copies of 
any of this information.



#####################################
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.  If you 
receive this message in error, please immediately
delete it and all copies of it from your system, destroy any hard copies of it, 
and notify the sender.  You must not, directly or
indirectly, use, disclose, distribute, print, or copy any part of this message 
if you are not the intended recipient.  Health First
reserves the right to monitor all e-mail communications through its networks.  
Any views or opinions expressed in this message are
solely those of the individual sender, except (1) where the message states such 
views or opinions are on behalf of a particular
entity;  and (2) the sender is authorized by the entity to give such views or 
opinions.
#####################################