>>>>To my mind, the correct behaviour would be for the director to terminate
>>>>the job after FDConnectTimeout has elapsed and then to inform the
>>>>storage daemon that the job has been cancelled / had an error. At the
>>>>moment, it looks like the director cancels the job but leaves the
>>>>storage daemon in an inconsistent state.
>>>
>>>
>>>"This should not be happening" and if it is occuring with 2.0 then it's
>>>definitely worthy of a bug report.
OK. This behaviour is still happening in version 2.0.
How can I arrange for the storage daemon to time out at the same rate as
the director?
Alternatively, how can I arrange for the storage daemon to be informed
when the director cancels a job so that a volume called "" doesn't end
up mounted?
Thanks,
Chris.
Here is some output from bconsole with v2.0 of bacula:
*status sto
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: 2.0.0 (04 January 2007) i686-redhat-linux-gnu redhat
(Stentz)
Daemon started 05-Jan-07 00:54, 4 Jobs run since started.
Heap: bytes=222,428 max_bytes=285,780 bufs=120 max_bufs=122
Running Jobs:
Backup Job Ngorongoro.2007-01-05_01.20.04 waiting for Client connection.
Writing: Incremental Backup job Ngorongoro JobId=633 Volume=""
pool="PoolIncDiskB" device=""FileStorageDiskB" (/var/spool/bacula2)"
Files=0 Bytes=0 Bytes/sec=0
FDSocket closed
====
Jobs waiting to reserve a drive:
3608 JobId=634 wants Pool="PoolFullDiskB" but have
Pool="PoolIncDiskB" on drive "FileStorageDiskB" (/var/spool/bacula2).
3607 JobId=634 wants Vol="Full-0065" drive has Vol="" on drive
"FileStorageDiskB" (/var/spool/bacula2).
====
Terminated Jobs:
JobId Level Files Bytes Status Finished Name
===================================================================
629 Incr 0 0 Error 05-Jan-07 00:55 Ngorongoro
630 Full 0 0 Error 05-Jan-07 00:55 BackupCatalog
631 Incr 120 21.41 M OK 05-Jan-07 01:00 Ngorongoro
632 Full 1 8.809 M OK 05-Jan-07 01:03 BackupCatalog
====
Device status:
Device "FileStorageDiskA" (/var/spool/bacula) is not open.
Device "FileStorageDiskB" (/var/spool/bacula2) is not open.
====
In Use Volume status:
====
*unmount
The defined Storage resources are:
1: FileDiskA
2: FileDiskB
Select Storage resource (1-2): 2
3901 Device "FileStorageDiskB" (/var/spool/bacula2) is already unmounted.
*mount
The defined Storage resources are:
1: FileDiskA
2: FileDiskB
Select Storage resource (1-2): 2
3906 File device "FileStorageDiskB" (/var/spool/bacula2) is always mounted.
-------------------------------------------------------------------------
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
