I have done it both ways, the biggest difference I found were the commands used. Both took about the same amount of time. I would suggest doing the move when expiration is not running and when there are not many backups running. And always make a backup first, but you knew that...
Andy Huebner -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Angus Macdonald Sent: Wednesday, April 04, 2007 3:50 AM To: [email protected] Subject: Re: [ADSM-L] moving/deleting a DB volume Agreed. That's the way I did a similar migration recently. No downtime that way. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Collins, Brenda Sent: 03 April 2007 19:19 To: [email protected] Subject: Re: [ADSM-L] moving/deleting a DB volume Hi! I just went through this process myself but I normally just make the new volume a copy of the original and once the synchronization process is complete, then I delete the original volume. Brenda -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Patterson, Scott Sent: Tuesday, April 03, 2007 12:50 PM To: [email protected] Subject: [ADSM-L] moving/deleting a DB volume Hi there all, TSM 5.2.7 on AIX 5.3.3 - question is about deleting a db vol with the intent to "move" it. As one can see from the output of the q dbv command we have 2 db vols. The first is on a local disk array and the second on enterprise storage disk. The goal is to get the DB off the local disk and onto the enterprise storage disk. ANS8000I Server command: 'q dbv f=d' Volume Name (Copy 1): /adsmserv/db/dbvol01.dsm Copy Status: Sync'd Volume Name (Copy 2): Copy Status: Undefined Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 50,000 Allocated Space (MB): 50,000 Free Space (MB): 0 Volume Name (Copy 1): /adsmserv/db2/db2.dsm Copy Status: Sync'd Volume Name (Copy 2): Copy Status: Undefined Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 81,000 Allocated Space (MB): 10,000 Free Space (MB): 71,000 If we run the command "delete dbv /adsmserv/db/dbvol01.dsm", TSM is smart enough to move the database contents out of /adsmserv/db/dbvol01.dsm and into /adsmserv/db2/db2.dsm. Is that correct? This delete/mov occurs during the background without interrupting other TSM processes and sessions? We would also like to delete/move the log vol in the near future. This move isn't from local to enterprise storage, just from one local array to another. We have not defined the new log volume or extended the current log volume. Assuming this work has been done... can we (again) simply "delete logv" on the log volume we want to "move" from? ANS8000I Server command: 'q logv f=d' Volume Name (Copy 1): /adsmserv/log/logvol01.dsm Copy Status: Sync'd Volume Name (Copy 2): Copy Status: Undefined Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 10,000 Allocated Space (MB): 10,000 Free Space (MB): 0 Thanks so much! Scott This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
