Re: Primary Pool and Copypool Relationship
If you want to pursue this, you'll have to run a select statement against the VOLUMEUSAGE to find the relevant offsite pool volumes. Check in the volumes from the resultant list, and run your MOVE NODEDATA. -- Mark Stapleton >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of Rushforth, Tim >Sent: Wednesday, June 09, 2004 9:39 AM >To: [EMAIL PROTECTED] >Subject: Re: Primary Pool and Copypool Relationship > >OK, #1 below wouldn't work either without bringing offsite tapes back! > >>Yes. Keep in mind that MOVE NODEDATA is not very useful for offsite >>copypools, since it requires the copypool-volumes to be onsite and >>available. (It doesn't work like e.g. MOVE DATA does, which >gets the files >>from the primary pool) >>-- >>Jurjen Oskam > >-Original Message- >From: Rushforth, Tim >Sent: June 7, 2004 3:05 PM >To: 'ADSM: Dist Stor Manager' >Subject: RE: Primary Pool and Copypool Relationship > >Ooops forgot about that restriction. To do this without bringing back >offsite tapes or deleting all copy pool data for some nodes >temporarily: > >1. Move nodedata from Copy Pool #1 to Copy Pool #1 (to new >volumes) for the >nodes you want to move. >2. Move nodedata Primary Pool #1 to Primary Pool #2 >3. Backup primary pool #2 to Copy Pool #2 >4. Delete the new volumes from 1. > > >-----Original Message- >From: Stapleton, Mark [mailto:[EMAIL PROTECTED] >Sent: June 7, 2004 2:54 PM >To: [EMAIL PROTECTED] >Subject: Re: Primary Pool and Copypool Relationship > >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of >Rushforth, Tim >>I guess the proper sequence should have been: >> >>1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will >use >>the data on Primary Pool #1 as the source data) >>2. Move nodedata from Primary Pool #1 to Primary Pool #2 > >Unfortunately, step #1 is not possible. MOVE NODEDATA supports data >moves within a single copy pool, but not between two copy pools. > >-- >Mark Stapleton > >
Re: Primary Pool and Copypool Relationship
OK, #1 below wouldn't work either without bringing offsite tapes back! >Yes. Keep in mind that MOVE NODEDATA is not very useful for offsite >copypools, since it requires the copypool-volumes to be onsite and >available. (It doesn't work like e.g. MOVE DATA does, which gets the files >from the primary pool) >-- >Jurjen Oskam -Original Message- From: Rushforth, Tim Sent: June 7, 2004 3:05 PM To: 'ADSM: Dist Stor Manager' Subject: RE: Primary Pool and Copypool Relationship Ooops forgot about that restriction. To do this without bringing back offsite tapes or deleting all copy pool data for some nodes temporarily: 1. Move nodedata from Copy Pool #1 to Copy Pool #1 (to new volumes) for the nodes you want to move. 2. Move nodedata Primary Pool #1 to Primary Pool #2 3. Backup primary pool #2 to Copy Pool #2 4. Delete the new volumes from 1. -Original Message- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 2:54 PM To: [EMAIL PROTECTED] Subject: Re: Primary Pool and Copypool Relationship From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim >I guess the proper sequence should have been: > >1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will use >the data on Primary Pool #1 as the source data) >2. Move nodedata from Primary Pool #1 to Primary Pool #2 Unfortunately, step #1 is not possible. MOVE NODEDATA supports data moves within a single copy pool, but not between two copy pools. -- Mark Stapleton
Re: Primary Pool and Copypool Relationship
Ooops forgot about that restriction. To do this without bringing back offsite tapes or deleting all copy pool data for some nodes temporarily: 1. Move nodedata from Copy Pool #1 to Copy Pool #1 (to new volumes) for the nodes you want to move. 2. Move nodedata Primary Pool #1 to Primary Pool #2 3. Backup primary pool #2 to Copy Pool #2 4. Delete the new volumes from 1. 1. move nodedata for the smaller group of data of the copy stgpool to new copy stg pool volumes in the same pool -Original Message- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 2:54 PM To: [EMAIL PROTECTED] Subject: Re: Primary Pool and Copypool Relationship From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim >I guess the proper sequence should have been: > >1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will use >the data on Primary Pool #1 as the source data) >2. Move nodedata from Primary Pool #1 to Primary Pool #2 Unfortunately, step #1 is not possible. MOVE NODEDATA supports data moves within a single copy pool, but not between two copy pools. -- Mark Stapleton
Re: Primary Pool and Copypool Relationship
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim >I guess the proper sequence should have been: > >1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will use >the data on Primary Pool #1 as the source data) >2. Move nodedata from Primary Pool #1 to Primary Pool #2 Unfortunately, step #1 is not possible. MOVE NODEDATA supports data moves within a single copy pool, but not between two copy pools. -- Mark Stapleton
Re: Primary Pool and Copypool Relationship
I guess the proper sequence should have been:
1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will use
the data on Primary Pool #1 as the source data)
2. Move nodedata from Primary Pool #1 to Primary Pool #2
I'm not sure if there is any way other than to bring the volumes back onsite
and do the move node data then.
Depending on how much other data is in Copy Pool #1 - you could do this but
I wouldn't recommend it. Delete all data in Copy Pool #1 then backup
Primary Pool #1.
-Original Message-
From: David Nicholson [mailto:[EMAIL PROTECTED]
Sent: June 7, 2004 1:39 PM
To: [EMAIL PROTECTED]
Subject: Re: Primary Pool and Copypool Relationship
I tried this cmd, but all my copy pool volumes are UNAVAIL (offsite).
any other suggestions?
Dave Nicholson
Whirlpool Corporation
"Rushforth, Tim" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/07/2004 11:20 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Primary Pool and Copypool Relationship
Yes this is how TSM works. You can have multiple copy pools for 1 Primary
Pool.
See http://msgs.adsm.org/cgi-bin/get/adsm0404/221.html for one way to delete
this data. (This assumes that there is still domr data that you want on
Copy Pool #1)
-Original Message-
From: David Nicholson [mailto:[EMAIL PROTECTED]
Sent: June 7, 2004 10:09 AM
To: [EMAIL PROTECTED]
Subject: Primary Pool and Copypool Relationship
Hi All,
I moved a lot of data out of Primary Pool #1 and into Primary Pool
#
2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool
#2.
It appears that the Copy Pool # 1 still has the backup of this
data...which I expected. The problem is that
it appears the data was also backed up to copy pool #2 as I moved the
datathis was not expected.
Does this sound like expected behavior? If so, any ideas for how
to clean up the "extra" copy in Copy Pool #1???
Thanks!
Dave Nicholson
Whirlpool Corporation
Re: Primary Pool and Copypool Relationship
I tried this cmd, but all my copy pool volumes are UNAVAIL (offsite).
any other suggestions?
Dave Nicholson
Whirlpool Corporation
"Rushforth, Tim" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/07/2004 11:20 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Primary Pool and Copypool Relationship
Yes this is how TSM works. You can have multiple copy pools for 1 Primary
Pool.
See http://msgs.adsm.org/cgi-bin/get/adsm0404/221.html for one way to delete
this data. (This assumes that there is still domr data that you want on
Copy Pool #1)
-Original Message-
From: David Nicholson [mailto:[EMAIL PROTECTED]
Sent: June 7, 2004 10:09 AM
To: [EMAIL PROTECTED]
Subject: Primary Pool and Copypool Relationship
Hi All,
I moved a lot of data out of Primary Pool #1 and into Primary Pool
#
2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool
#2.
It appears that the Copy Pool # 1 still has the backup of this
data...which I expected. The problem is that
it appears the data was also backed up to copy pool #2 as I moved the
datathis was not expected.
Does this sound like expected behavior? If so, any ideas for how
to clean up the "extra" copy in Copy Pool #1???
Thanks!
Dave Nicholson
Whirlpool Corporation
Re: Primary Pool and Copypool Relationship
Yes this is how TSM works. You can have multiple copy pools for 1 Primary Pool. See http://msgs.adsm.org/cgi-bin/get/adsm0404/221.html for one way to delete this data. (This assumes that there is still domr data that you want on Copy Pool #1) -Original Message- From: David Nicholson [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: Primary Pool and Copypool Relationship Hi All, I moved a lot of data out of Primary Pool #1 and into Primary Pool # 2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool #2. It appears that the Copy Pool # 1 still has the backup of this data...which I expected. The problem is that it appears the data was also backed up to copy pool #2 as I moved the datathis was not expected. Does this sound like expected behavior? If so, any ideas for how to clean up the "extra" copy in Copy Pool #1??? Thanks! Dave Nicholson Whirlpool Corporation
Primary Pool and Copypool Relationship
Hi All, I moved a lot of data out of Primary Pool #1 and into Primary Pool # 2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool #2. It appears that the Copy Pool # 1 still has the backup of this data...which I expected. The problem is that it appears the data was also backed up to copy pool #2 as I moved the datathis was not expected. Does this sound like expected behavior? If so, any ideas for how to clean up the "extra" copy in Copy Pool #1??? Thanks! Dave Nicholson Whirlpool Corporation
