All of tapepool1 will be copied to copypool1b.

If you don't want this to happen, you need to make a new primary
tapepool1b and marry it to diskpool1.  Then only new backup version
will go to copypool1b.

A node can have its backups spread across any number of primary
disk or sequential storagepools.


--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <s7cf83d1.025 AT equitable-of-iowa DOT com>, on 09/03/99
In <s7cf83d1.025 AT equitable-of-iowa DOT com>, on 09/03/99
   at 08:15 AM, Dana Mitchell <dnmitchell AT EQUITABLE-OF-IOWA DOT COM> said:

>Hello,

>I have another question relating to exactly how copypools operate.  I am in 
>the process of implementing STK 9840's for ADSM's use under OS/390.

>I currently have five disk-tape pool pairs getting backed up to five 
>copypools.  Two of these pools are quite large (and good 9840 candidates).  My 
>problem is that all five copypools are using the same device class and thus I 
>am unable to point the large pools to the 9840's while leaving the small pools 
>going to 3490 equivalents.

>I would like to define new copy pools and a new device class to go to the 
>9840's.  What will happen when I backup tapepool1 to (new) copypool1B?  WIll 
>just any new files in tapepool1 that havn't been backed up to *any* copypool 
>be backed up to new copypool1B?  Or since *no* files in tapepool1 had been 
>previously backed up copypool1B will they all try to get backed up?  I would 
>like to have new backups go to the 984

>All comments are appreciated.
>Dana Mitchell
>Equitable of Iowa