Dwight...I think you were on target with the file size limit....it was set to 
100 MB...I'm going to set it to NO LIMIT this evening to confirm...

Thanks!
Kelli Jones
jonesk AT co.chesterfield.va DOT us 


>>> "Cook, Dwight E" <cookde AT BP DOT COM> 04/11/00 10:53AM >>>
When the client starts its backup, what is the status of diskpool ?
Is it so full that there is no room for the client's data and thus it is
directed to diskpool's next pool (which I assume is tapepool) ?
Does it reach this condition sometime during its backup ?
Is there a file size limit on your diskpool ? This could force a roll to the
nextpool...

Dwight

> ----------
> From:         Kelli Jones[SMTP:JONESK AT CO.CHESTERFIELD.VA DOT US] 
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, April 11, 2000 9:41 AM
> To:   ADSM-L AT VM.MARIST DOT EDU 
> Subject:      Changing Destination from TAPEPOOL to DISKPOOL
>
> Question...a new NT server running oracle was recently added.  In error, I
> set the destination as 'TAPEPOOL' initially and then changed it to
> 'DISKPOOL'.  It appears that the backup is continuing to attempt to go to
> TAPEPOOL which causes a problem for the backup of storage pool TAPEPOOL to
> COPYPOOL.  It appears that the session for the NT server (which is hung
> when I come in 8 hours after it starts!) is using a tape required for the
> backup of TAPEPOOL to COPYPOOL (?).  When I cancel the server session, the
> storage pool backup kicks off immediately.   What am I missing?  The
> active copygroup shows destination as 'DISKPOOL'.   Other backups going to
> DISKPOOL and starting both before and after the session begins for the
> NTserver are completing successfully.
>
> ADSM 3.1.2.50
> AIX 4.3.2
> 3466 C20
> 3575 L32 (4 Drives)
>
> Thanks,
> Kelli Jones
> jonesk AT co.chesterfield.va DOT us 
>