< why not just delete the volumes in the copy storage pool you want to get rid of?
Because the data isn't collocated. If my customer was on 5.2 I could collocate the specific node in question and then delete it, but I'm not at that level. Thanks anyway! -- Joshua S. Bassi Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP IBM Certified - AIX 4/5L, SAN, Shark Cell (831) 595-3962 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Stewart Sent: Monday, June 09, 2003 6:47 PM To: [EMAIL PROTECTED] Subject: Re: Move from Primary Pool Doesn't Remove from Copy Pool Once you are sure the data has all been copied to a new copy storage pool, why not just delete the volumes in the copy storage pool you want to get rid of? This shouldn't do anything to your primary pool, or your new copy pool. Curtis Stewart Shannon Bach wrote: > > After giving it some thought, I figure you have two choices. > > 1. If your OLD Copypool is sequential then you could sort by the > oldest written date and move the data from each cartridge to the NEW > Copypool. That way, data that should be expired, would be once it was > with the rest of the copypool data. This will take awhile but it > should work, though I may be wrong. You have to be careful with data > in OLD Copypools because the data could belong to an old node that > while it may no longer be in use, there are still file spaces > associated with it that may needed to be restored at some time. Your > new Copypool may not have the same data in it, especially if it's from > a retired node. > > 2. Make sure the properties of the OLD Copypool (storagepool itself) > is updated to unavailable and just let the data expire on it's own > until it is empty. The data in the Old copypool can still be > associated with management classes that the New Copypool knows nothing > about. > > I may be wrong and there is a simple answer. Maybe one of the experts > in the list may know of an easier way. > > Shannon > Madison Gas & Electric > [EMAIL PROTECTED]