Bacula-users

[Bacula-users] Strange tape selection behaviour

2012-03-07 13:31:34
Subject: [Bacula-users] Strange tape selection behaviour
From: Tilman Schmidt <t.schmidt AT phoenixsoftware DOT de>
To: bacula-users <bacula-users AT lists.sourceforge DOT net>
Date: Wed, 07 Mar 2012 19:16:55 +0100
This is what my Bacula server reported at the start of last night's
backup cycle:

06-MÀr 22:05 backup-dir JobId 1027: Start Backup JobId 1027,
Job=backup.2012-03-06_22.05.00_27
06-MÀr 22:05 backup-dir JobId 1027: Max configured use duration
exceeded. Marking Volume "Daily_0" as Used.
06-MÀr 22:05 backup-dir JobId 1027: There are no more Jobs associated
with Volume "Daily_0". Marking it purged.
06-MÀr 22:05 backup-dir JobId 1027: All records pruned from Volume
"Daily_0"; marking it "Purged"
06-MÀr 22:05 backup-dir JobId 1027: Recycled volume "Daily_0"
06-MÀr 22:05 backup-dir JobId 1027: Using Device "LTO-3"
06-MÀr 22:05 bacula-sd JobId 1027: Job backup.2012-03-06_22.05.00_27 is
waiting. Cannot find any appendable volumes.
Please use the "label" command to create a new Volume for:
    Storage:      "LTO-3" (/dev/nst0)
    Pool:         Daily
    Media type:   LTO-3
06-MÀr 22:10 bacula-sd JobId 1027: 3307 Issuing autochanger "unload
slot 8, drive 0" command.
06-MÀr 22:10 bacula-sd JobId 1027: 3304 Issuing autochanger "load slot
3, drive 0" command.
06-MÀr 22:11 bacula-sd JobId 1027: 3305 Autochanger "load slot 3, drive
0", status is OK.
06-MÀr 22:11 bacula-sd JobId 1027: Volume "Daily_2" previously written,
moving to end of data.
06-MÀr 22:13 bacula-sd JobId 1027: Ready to append to end of Volume
"Daily_2" at file=104.
06-MÀr 22:13 bacula-sd JobId 1027: Spooling data ...

(Please ignore the mangled umlaut in the month name. The "-8"
option was missing from the bsmtp commands in bacula-dir.conf,
but that's corrected now.)

From there, everything proceeded perfectly fine.
The two preceding jobs had been
- incremental to volume "Daily_2" (slot 3)
- full to volume "March" (slot 8)

Pool "Daily" contains three volumes "Daily_0", "Daily_1" and
"Daily_2". Before this job, all three had status "Append".
"Daily_0" and "Daily_1" were in fact empty (VolFiles=0), and
"Daily_2" nowhere near full (130GB on an LTO-3 tape).
After this job, volume "Daily_0" displays status "Recycle"
while "Daily_1" and "Daily_2" still say "Append".
So why would Bacula
- first purge and recycle "Daily_0" (but not "Daily_1")
- then complain that it couldn't find any appendable volumes
- and finally five minutes later mount and use "Daily_2",
  thereby admitting it was appendable after all?

Thanks,
Tilman


Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Bacula-users] Strange tape selection behaviour, Tilman Schmidt <=