I've noticed that bacula (1.38.11) reports that the same media is in different
pools at the same time, with "stat stor" and "stat clients" giving the wrong
information.
For example, I've included output from "stat clients" (below, edited). Note the
pool names in the section "Running Jobs", where Volume 000035 is correctly
identified as being in the "Full" pool. Then note that in the "Device Status"
section, that volume is incorrectly identified as being in pool "Incremental".
--------------------------------------------------------------------
stat clients
Automatically selected Storage: pv132t
Connecting to Storage daemon pv132t at parthenon:9103
parthenon-sd Version: 1.38.11 (28 June 2006) i686-pc-linux-gnu redhat (Yarrow)
Daemon started 06-Dec-06 18:25, 13 Jobs run since started.
Running Jobs:
Writing: Full Backup job rodos-full JobId=2399 Volume="000035"
pool="Full" device=""Drive-0" (/dev/tape0)"
Files=116,037 Bytes=3,071,923,207 Bytes/sec=3,317,411
FDReadSeqNo=957,219 in_msg=649467 out_msg=5 fd=26
Writing: Full Backup job smyrna-full JobId=2400 Volume="000035"
pool="Full" device=""Drive-0" (/dev/tape0)"
Files=87,591 Bytes=4,771,369,752 Bytes/sec=5,158,237
FDReadSeqNo=765,792 in_msg=531018 out_msg=5 fd=29
Writing: Incremental Backup job parthenon-inc JobId=2415 Volume="000027"
pool="Incremental" device=""Drive-1" (/dev/tape1)"
Files=129 Bytes=4,262,705,479 Bytes/sec=7,792,880
FDReadSeqNo=65,910 in_msg=65618 out_msg=5 fd=11
====
Device status:
Autochanger "pv132t" with devices:
"Drive-0" (/dev/tape0)
"Drive-1" (/dev/tape1)
Device "Drive-0" (/dev/tape0) is mounted with Volume="000035" Pool="Incremental"
Slot 5 is loaded in drive 0.
Total Bytes=415,927,129,106 Blocks=6,447,286 Bytes/block=64,511
Positioned at File=418 Block=0
Device "Drive-1" (/dev/tape1) is mounted with Volume="000027" Pool="Incremental"
Slot 10 is loaded in drive 1.
Total Bytes=172,406,241,415 Blocks=2,672,469 Bytes/block=64,511
Positioned at File=172 Block=8,816
====
------------------------------------------------------------------------------
The "stat stor" command also reports the wrong information, while query number
15 (reporting what volumes Bacula thinks are in the autochanger) correctly
identified volume 000035 as being in the Full pool.
I have seen this behavior on many volumes. It's confusing to human beings, but
apparently Bacula doesn't use the "stat stor" results to determine what pool a
volume is in, so it does select the correct media for writing full vrs.
incremental backups.
----
Mark Bergman [EMAIL PROTECTED]
System Administrator
Section of Biomedical Image Analysis 215-662-7310
Department of Radiology, University of Pennsylvania
http://pgpkeys.pca.dfn.de:11371/pks/lookup?search=mark.bergman%40.uphs.upenn.edu
The information contained in this e-mail message is intended only for the
personal and confidential use of the recipient(s) named above. If the reader of
this message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you have
received this communication in error, please notify us immediately by e-mail,
and delete the original message.
-------------------------------------------------------------------------
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
