> One thing that might be different between my needs and others is that > I never want to use more than one drive at a time for a single pool. I > am not sure that made sense so I will try to say it a different way... > I mean that if there are concurrent jobs running for a single pool I > want this to only be on a single drive at a time.
So, a more generalized version of this statement might be that you want to be able to set a maximum number of drives used for referencing volumes in a pool on a pool-by-pool basis (from 0 to the maximum available for that library). Would it also be useful to be able to distinguish between drives used for backups and drives used for migration jobs? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
