Insert overwriteable media in disk pool?

[Eakx]

Hi 

I have a incremental backup to disk job that takes backup to a disk pool with 6 disks and TB's of free space. 

This works fine, but occasionally the backup job tries to store the job on the disk with the least amount of free space. This results in halted job and message: "Please insert overwritable media into the robotic library using the import command."

Why can't the job store the data in the disk whith the most free space?

Why can't the job store the data on several disks in the pool?

Why can't the job switch to another disk in the pool when it sees that there is no more space?

Does anybody else have this problem? Is there any way to avoid this problem?

[Colin_Weaver]

Load balancing in disk pooks currently does not work in an optimal fashion.

We are current planning (subject to change) to introduce some enhancements in this area that will allow the selection at the start of a job, of the disk device with most free space, however this enhancement is currently planned for the next full release of Backup Exec and will not be available in the current version.

One thing that is not planned to be changed is the limitation where GRT enabled sets cannot span from one device to another when the device fills up mid job. This is because we have to be able to mount the GRT image from one location to recover individual data from within it.

Note: Spreading the data over multiple disks in the pool in parallel (similar to RAID 5) is known as Multi-Streaming and I believe is something available in NetBackup and not in Backup Exec.