Alan Brown wrote: >> You might configure concurrent jobs as a solution. > > > It won't help in this situation and the message tends to indicate > concurrent jobs are setup.
I don't think they are. My config file (http://laplace.chem.ox.ac.uk/b/bacula-dir.conf) contains this block: Director { # define myself Name = lilac-dir DIRport = 9101 # where we listen for UA connections QueryFile = "/etc/bacula/query.sql" WorkingDirectory = "/var/bacula" PidDirectory = "/var/run" Maximum Concurrent Jobs = 1 Messages = Daemon FDConnectTimeout = 10 } which should stop concurrent jobs, I think. > "waiting to reserve a device" means that all available tape drives are > in use by jobs using other Pools. What does it mean when the "tape device" is actually a hard disk directory with different files in there, one for each "tape"? > In the case of BackupCatalog it is POTENTIALLY DANGEROUS for it to be > running when any other job is also running. This job shold be run at > either highest or lowest priority (It's lower than normal jobs by > default. I've moved it to "highest" because I want the catalog backed up > every day, even if that means holding up other stuff - when at lower > priority there have been incidents where the catalog wasn't backed up > for 2+ weeks while other jobs were running.) # Backup the catalog database (after the nightly save) Job { Name = "BackupCatalog" JobDefs = "DefaultJobDiskB" Client = lilac-fd Level = Full FileSet="Catalog" Schedule = "WeeklyCycleAfterBackup" # This creates an ASCII copy of the catalog RunBeforeJob = "/etc/bacula/make_catalog_backup bacula bacula" # This deletes the copy of the catalog RunAfterJob = "/etc/bacula/delete_catalog_backup" Write Bootstrap = "/var/bacula/BackupCatalog.bsr" Priority = 12 # run after main backup } I have the catalog set to a lower priority and starting 5 min after all the other backup jobs. > Coming back to "waiting to reserve a device" > > What other jobs are running? Every night, at 9pm, I backup two PC's and also various IMAP accounts and FTP sites. Then at 9.05pm I backup the catalog. In practice, the backups usually take 10-15min to complete, except when there is a Full backup scheduled which often takes up to 1 hour. Here is a typical list of scheduled jobs: Scheduled Jobs: Level Type Pri Scheduled Name =================================================================================== Incremental Backup 9 29-Dec-06 21:00 Ngorongoro-SystemState Incremental Backup 10 29-Dec-06 21:00 Lilac Incremental Backup 10 29-Dec-06 21:00 Ngorongoro Incremental Backup 11 29-Dec-06 21:00 PlusNetWebspace Incremental Backup 11 29-Dec-06 21:00 PlusNetEmail Incremental Backup 11 29-Dec-06 21:00 RodgersOrgUkWebspace Full Backup 12 29-Dec-06 21:05 BackupCatalog After the main (9pm) jobs have tried to run, which means that the Ngorongoro ones have failed, the status reports look like this: > What does "status director" show? Running Jobs: JobId Level Name Status ====================================================================== 570 Full BackupCatalog.2006-12-28_21.05.00 is waiting on Storage FileDiskB ==== > What does "status storage" show? 3) "status storage" shows this for the jammed up catalog backup: *status storage The defined Storage resources are: 1: FileDiskA 2: FileDiskB Select Storage resource (1-2): 2 Connecting to Storage daemon FileDiskB at lilac:9103 lilac-sd Version: 1.38.2 (20 November 2005) i686-redhat-linux-gnu redhat (Stentz) Daemon started 28-Dec-06 20:59, 4 Jobs run since started. Running Jobs: Backup Job Ngorongoro-SystemState.2006-12-28_21.00.00 waiting for Client connection. Incremental Backup job Ngorongoro-SystemState JobId=564 Volume="" pool="PoolIncDiskB" device=""FileStorageDiskB" (/var/spool/bacula2)" Files=0 Bytes=0 Bytes/sec=0 FDSocket closed Backup Job Ngorongoro.2006-12-28_21.00.02 waiting for Client connection. Incremental Backup job Ngorongoro JobId=566 Volume="" pool="PoolIncDiskB" device=""FileStorageDiskB" (/var/spool/bacula2)" Files=0 Bytes=0 Bytes/sec=0 FDSocket closed ==== Terminated Jobs: JobId Level Files Bytes Status Finished Name ====================================================================== 558 Incr 45 22,287,855 OK 27-Dec-06 21:00 Lilac 560 Incr 0 0 OK 27-Dec-06 21:01 PlusNetWebspace 561 Incr 0 0 OK 27-Dec-06 21:01 PlusNetEmail 562 Incr 0 0 OK 27-Dec-06 21:01 RodgersOrgUkWebspace 557 Incr 0 0 Other 27-Dec-06 21:30 Ngorongoro-SystemState 559 Incr 0 0 Other 27-Dec-06 21:30 Ngorongoro 565 Incr 108 52,589,545 OK 28-Dec-06 21:00 Lilac 567 Incr 25 21,345 OK 28-Dec-06 21:01 PlusNetWebspace 568 Incr 10 11,487,596 OK 28-Dec-06 21:01 PlusNetEmail 569 Incr 0 0 OK 28-Dec-06 21:01 RodgersOrgUkWebspace ==== Device status: Device "FileStorageDiskA" (/var/spool/bacula) is not open or does not exist. Device "FileStorageDiskB" (/var/spool/bacula2) is not open or does not exist. ==== In Use Volume status: ==== Does anyone know what the lines: Device status: Device "FileStorageDiskA" (/var/spool/bacula) is not open or does not exist. Device "FileStorageDiskB" (/var/spool/bacula2) is not open or does not exist. mean??? /var/spool/bacula definitely does exist! Chris. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
