Hi, On 6/4/2007 3:54 PM, Lonny Selinger wrote: > Setup: > > I have 2 DLT drives (a and b) set up to accept jobs dedicated to each > drive. Certain types of jobs go to a and certain types go to b and > this seems to work fine. The problem I'm running into is having a > drive request media in another drive. Both are valid for writing and > are in the same pool but for some reason I'll get media mount > requests on drive a for the media in drive b and vic/versa. Anyone > have any ideas why this might be? The two media ID's aren't full and > the upcoming jobs still show that a backup destined for drive b is > going to request the media already mounted in a.
Which version of Bacula? This should happen rarely since 1.38, I believe, since in that version the catalog notices which device used a volume last. > Suggestions greatly appreciated, Thanks! Lonny Different media types, but that has been suggested... the catalog update fpr the existing volumes is rather simple: In SQL, something like 'UPDATE Media SET MediaType="a" WHERE <however you can most easily select the volumes>;' is all you need. You could select by Volume name, with wildcards, or using a list of volume IDs, for example. Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- 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 Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
