Bacula-users

Re: [Bacula-users] Problem changing tapes due to inconsistency between 'list media' and 'query catalog'?

2010-01-28 10:38:09
Subject: Re: [Bacula-users] Problem changing tapes due to inconsistency between 'list media' and 'query catalog'?
From: John Drescher <drescherjm AT gmail DOT com>
To: Thomas Dhollander <thomas.dhollander AT gmail DOT com>
Date: Thu, 28 Jan 2010 10:36:06 -0500
On Thu, Jan 28, 2010 at 10:32 AM, Thomas Dhollander
<thomas.dhollander AT gmail DOT com> wrote:
> Hi John
>
> Thanks for your reaction. I added the conf files below.
>
> Looking forward to any hints / thoughts on this.
>
> Thomas
>
>
> On 28 Jan 2010, at 14:42, John Drescher wrote:
>
>>> In our current setup, Bacula does not seem to automatically load the correct
>>> tape in the drive for its backups. We did specify the correct autochanger
>>> options in the storage daemon conf file and made sure the device uses the
>>> autochanger.
>>>
>>> When we execute the 'list media' command in bconsole, we get the following
>>> output:
>>>
>>> Automatically selected Catalog: ClientDB
>>> Using Catalog "ClientDB"
>>> Pool: Default
>>> +---------+------------+-----------+---------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+
>>> | MediaId | VolumeName | VolStatus | Enabled | VolBytes       | VolFiles |
>>> VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten
>>> |
>>> +---------+------------+-----------+---------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+
>>> |       1 | 426BBL     | Append    |       1 | 26,842,862,592 |       65 |
>>> 31,536,000 |       1 |    0 |         1 | LTO-4     | 2010-01-28 06:00:11 |
>>> +---------+------------+-----------+---------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+
>>>
>>> from which i derive that Bacula recognizes one pool ('Default') with one
>>> associated volume, that is currently in the autochanger.
>>>
>>> But the 'query catalog' command (we use the mysql db) seems not to know
>>> about the volume in the autochanger:
>>>
>>> *query catalog
>>> Automatically selected Catalog: ClientDB
>>> Using Catalog "ClientDB"
>>> Available queries:
>>>      1: List up to 20 places where a File is saved regardless of the
>>> directory
>>>      2: List where the most recent copies of a file are saved
>>>      3: List last 20 Full Backups for a Client
>>>      4: List all backups for a Client after a specified time
>>>      5: List all backups for a Client
>>>      6: List Volume Attributes for a selected Volume
>>>      7: List Volumes used by selected JobId
>>>      8: List Volumes to Restore All Files
>>>      9: List Pool Attributes for a selected Pool
>>>     10: List total files/bytes by Job
>>>     11: List total files/bytes by Volume
>>>     12: List Files for a selected JobId
>>>     13: List Jobs stored on a selected MediaId
>>>     14: List Jobs stored for a given Volume name
>>>     15: List Volumes Bacula thinks are in changer
>>>     16: List Volumes likely to need replacement from age or errors
>>> Choose a query (1-16): 15
>>> No results to list.
>>>
>>> In addition, the logs show the following message blocks:
>>> 28-Jan 04:00 blade03-sd JobId 19: Invalid slot=0 defined in catalog for
>>> Volume "426BBL" on "TS2900" (/dev/nst0). Manual load may be required.
>>> 28-Jan 04:00 blade03-sd JobId 19: 3301 Issuing autochanger "loaded? drive 0"
>>> command.
>>> 28-Jan 04:00 blade03-sd JobId 19: 3302 Autochanger "loaded? drive 0",
>>> result: nothing loaded.
>>> 28-Jan 04:00 blade03-sd JobId 19: 3301 Issuing autochanger "loaded? drive 0"
>>> command.
>>> 28-Jan 04:00 blade03-sd JobId 19: 3302 Autochanger "loaded? drive 0",
>>> result: nothing loaded.
>>> 28-Jan 04:00 blade03-sd JobId 19: Warning: mount.c:219 Open device "TS2900"
>>> (/dev/nst0) Volume "426BBL" failed: ERR=dev.c:474 Unable to open device
>>> "TS2900" (/dev/nst0): ERR=No medium found
>>>
>>> In other words, the catalog does not seem to know about the volumes in the
>>> autochanger slots? Could we run a bscan or take other actions to restore
>>> consistency between the catalog and the tape library? We already tried the
>>> 'update slots' command but that had no effect.
>>>
>>> Note that we are just getting started with Bacula soo re-initializing the
>>> whole catalog is an option if it would make our setup consistent again.
>>>
>> That would require you to erase each tape used with mt.
>>
>> Can you post your bacula-sd.conf and bacula-dir.conf and your bacula version.
>
> bacula-sd.conf:
> --------------------
>
> Storage {                             # definition of myself
>  Name = blade03-sd
>  SDPort = 9103                  # Director's port
>  WorkingDirectory = "/var/lib/bacula"
>  Pid Directory = "/var/run"
>  Maximum Concurrent Jobs = 20
> }
>
> Director {
>  Name = blade03-dir
>  Password = "Vzl7x+Z+WEFvLNXRip1XWMKZRT8gGLhbT/N1Z+moemxv"
> }
>
> Autochanger{
>  Name = Autochanger
>  Device = TS2900
>  Changer Command = "/usr/lib64/bacula/mtx-changer %c %o %S %a %d"
>  Changer Device = /dev/changer
> }
>
> Device {
>  Name = TS2900
>  Drive Index = 0
>  Media Type = LTO-4
> #  Archive Device = /dev/IBMtape0n
>  Archive Device = /dev/nst0
>  AutomaticMount = yes               # when device opened, read it
>  Autoselect = yes
>  AlwaysOpen = yes
>  RemovableMedia = yes
>  RandomAccess = no
>  AutoChanger = yes
>  #Alert Command = "sh -c 'tapeinfo -f %c | grep TapeAlert | cat'"
>  Maximum Network Buffer Size = 65536
>  Spool Directory = /var/spool/bacula
>  Label Type = IBM
>  Check Labels = yes
> }
>
> Messages {
>  Name = Standard
>  director = blade03-dir = all
> }
>
> bacula-dir.conf:
> --------------------
>
> # Bacula
> Director {
>  Name = blade03-dir
>  DIRport = 9101
>  QueryFile = "/usr/lib64/bacula/query.sql"
>  WorkingDirectory = "/var/lib/bacula"
>  PidDirectory = "/var/run"
>  Maximum Concurrent Jobs = 1
>  Password = "re73hjSIcRcixolfzXJsaeaJafv1hHC2juYgss4Zrx/q"
>  Messages = Daemon
> }
>
> JobDefs {
>  Name = DefaultJob
>  Type = Backup
>  Level = Incremental
>  FileSet = FullClientBackup
>  Schedule = WeeklyCycle
>  Storage = TapeDrive
>  Messages = Standard
>  Pool = Default
>  Priority = 10
> }
>
> JobDefs {
>  Name = client-jobdefs
>  Type = Backup
>  Level = Incremental
>  FileSet = FullClientBackup
>  Schedule = "WeeklyCycle"
>  Storage = TapeDrive #File
>  Messages = Standard
>  Pool = Default
>  Priority = 10
> }
>
> #Job {
> #  Name = "BackupClient1"
> #  JobDefs = "DefaultJob"
> #  Write Bootstrap = "/var/lib/bacula/Client1.bsr"
> #}
>
> Job {
>  Name = VirtualImagesJob
>  JobDefs = DefaultJob
>  Client = blade03-fd
>  FileSet = VirtualImagesFileSet
> }
>

You are missing the storage and client sections of bacula-dir.conf.
The stroage section probably is enough.

John

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users