I used to use BE that way, but then I became enlightened by device pools. In the past, I was able to create device pools, such as "Full Backups" and "Differential Backups" so that when I wanted to swap the drive usage, I would not have to modify all 22 jobs I have, only swap the drive locations in the pools. I had one drive assigned to each pool. Two jobs will run at the same time in v10, but I have found they will not always run when you assign the jobs to device pools. The job engine seems to want assignment to physical hardware in order to run concurrent jobs to one library, negating the purpose of the device pools entirely. This was never a problem in v8.6. 10 has enough improvements to stay with it, but it was VERY frustrating to see my backups not run concurrently for a while. I guess I'll go back to using physical device assignent until something pops up. Thanks for all the suggestions.