What I did for my large DB2 customers was make a class which is bound to go
directly to a tape pool.
You could even do it for just that one dataset, if they bind it in their IE
file (if using an API you can make a
node just for them to use for the BIG ones.




Richard Sims <rbs AT BU DOT EDU>@VM.MARIST.EDU> on 06/21/2001 01:00:54 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: Disk pool size vs large file



>I have a 56GB disk pool with the next pool to tape.  I have a user, DB2
>Admin, that wants to back up a 125GB DB2 backup.  What's the best way to
>handle this one user?  If he/she backs up the file will it crash the
system
>because it's bigger that the diskpool, or will it go right to tape?

That huge backup will likely choke on the disk pool filling and waiting for
migration to tape.  I would take the approach, for this one exceptional
backup event, of doing UPDate STGpool ... ACCess=READOnly for the duration
of the event, so that the backup goes directly to tape.  Others with direct
experience with such DB2 backups may have more to say on approaches.

   Richard Sims, BU