>Can you give us a few more clues ?
Sure:
>Are you backing up to multiple offsite storage pools at the same time?
No, single pools at a time. As we have six production drives and two main
stgpool backups so
this problem will always occur if we try to use more than a pair of drives
for a backup stgpool - unless
there is a setting or option that prevents two processes asking for the same
volume, at the same time, for the same job.

>Can you schedule the copys at another quiet time
Unfortunately not, the copy jobs that run in the morning (where the problem
is most apparent) mop up
data that has not been copied to the offsite tapes from previous stgpool
backups in the night.
We have 200Gb - 300Gb to copy a night to offsite copies (collocated onto ~
25-30 tapes)

>We also make two copies of our primary pool and we have two tape drives
>running two procs.
>The copies are made from the backuppool to the tapes and files (large
>files)that have migrated to the primary tape pools are copied after the
disk
>pool has been copied.
>The trick is to have the majority of files from the overnight backup on
disk
>and copy these files to the offsite copypools before these files are
>migrated to the primary pools.
>This will improve this copy process.

I like this idea although I'm not sure we have the disk to cope with this
yet. I shall experiment with
this approach.


>Leo Humar
>LCS Pty Ltd
>lhumar AT bigpond.net DOT au

>No trees were killed in the sending of this message. However a large
>number of electrons were terribly inconvenienced.