Alexander

Was this a differential backup? If so look at the DIFFESTIMATE option in
the TDPSQL.CFG.

Prior to performing a database backup, the TDP for SQL client must
'reserve' the required space in the storage pool. It *should* get the
estimate right for full backups and transaction log backups because the
space used in the database and transaction logs is available from SQL
Server.

For differential backups, there is no way of knowing how much data is to be
backed up until the backup is complete. The TDP for SQL client therefore
uses the percentage specified in the the DIFFESTIMATE option to calculate a
figure based on the total space used. Eg for a database of 50Gb with a
DIFFESTIMATE value of 20, TDP will reserve 10Gb (20% of 50Gb).

Your problem will arise if the actual backup exceeds the calculated
estimate. If the storage pool is not big enough to accomodate the larger
backup, of if other backup data prevents further space being reserved, this
error will occur.

Setting DIFFESTIMATE to 100 will ensure that there is always sufficient
space available, but will prevent space in your primary storage pool being
utilised by other clients and may force the backup to occur to the next
storage pool in the hierarchy unnecessarily. It is worth setting
DIFFESTIMATE to the maximum proportion of the data you can envisage ever
being backed up during a differential backup.

Hope this helps.

Neil Schofield



Visit our web site to find out about our award winning
Cool Schools community campaign at
http://www.yorkshirewater.com/yorkshirewater/schools.html
The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682