Re: Primary Pool and Copypool Relationship
2004-06-07 15:54:10
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Primary Pool and Copypool Relationship, David Nicholson
- Re: Primary Pool and Copypool Relationship, Rushforth, Tim
- Re: Primary Pool and Copypool Relationship, David Nicholson
- Re: Primary Pool and Copypool Relationship, Rushforth, Tim
- Re: Primary Pool and Copypool Relationship,
Stapleton, Mark <=
- Re: Primary Pool and Copypool Relationship, Rushforth, Tim
- Re: Primary Pool and Copypool Relationship, Rushforth, Tim
- Re: Primary Pool and Copypool Relationship, Stapleton, Mark
|
Previous by Date: |
Re: Primary Pool and Copypool Relationship, Rushforth, Tim |
Next by Date: |
TSM, Solaris, and more then 4 CPU's: Trouble in Paradise?, French, Michael |
Previous by Thread: |
Re: Primary Pool and Copypool Relationship, Rushforth, Tim |
Next by Thread: |
Re: Primary Pool and Copypool Relationship, Rushforth, Tim |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|