ADSM-L

[ADSM-L] Move data from DISK pool to FILE pool

2009-07-28 06:38:47
Subject: [ADSM-L] Move data from DISK pool to FILE pool
From: Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 28 Jul 2009 13:35:15 +0300
Dear TSMers,
We have TSM 5.5.1.1 under AIX 5.3.
I need to move data from DISK primary storage pool (raw logical volumes) to 
FILE primary storage pool (JFS2 file system).
There are 3 tape copy pools for DISK primary pool.
I am going to use next procedure:
1) create FILE primary storage pool with appropriate size;
2) move data from DISK primary storage pool to FILE pool by "move data <vol> 
stg=<FILE> reconstruct=no" (volume by volume);
3) delete DISK primary storage pool;
4) rename FILE storage pool to old DISK pool name.
My expectations:
1)     all existing tape copy pools, made for DISK pool, will be still legal 
for FILE primary storage pool (no need to make extra backups and it is possible 
to restore any data in FILE storage pool);
2)     no need to modify any copy groups connected to old DISK pool because of 
the same storage pool name;
3)     expiry process will continue to work normally;
4)     full/incremental backup history will be untouched by data movement.
Am I right?
I will deeply appreciate any comments.
Thank you very much in advance.
Kindest regards,


Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com<mailto:G.Solonovitch AT bkme DOT com>

Please consider the environment before printing this Email


Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."