With TDP for Oracle you set a parameter called DSMO_AVG_SIZE. Every time a
file is sent to TSM that parameter is used to allocate space in the storage
pool. The real file size is not allocated until the entire file is written
to TSM. This action occurs for every channel allocated. So, if you are
allocating 4 channels with a DSMO_AVG_SIZE parm of 1024 MB, every time RMAN
sends a file each channel allocates 1024 MB in your storage pool. This can't
automatically migrate into your next storage pool. If you are running your
TDP backups to disk first you need to tune DSMO_AVG_SIZE to be close to the
average for your database files, the number of channels used and the
migration thresholds for your disk storage pools.



Thanks,

Eric

 -----Original Message-----
From:   Ike Hunley [mailto:bizzorg AT WORLDNET.ATT DOT NET]
Sent:   Friday, March 29, 2002 4:47 PM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Rman/TSm

Question:  When an object is passed via TDP to TSM for backup, does the
defined storage pool in TSM have to have enough space to backup the entire
object?  If the storage pool has 20GB defined, but the object is 45GB, won't
the backup spill over to the storage pool specified in the next storage
pool?