Hello everyone,
as a new bacula user, I must first say that this project's documentation
is simply staggering. This is a very nice change from the usual
situation, which is basically "read the code if you want docs". :-)
Anyway, I have, during my tests, run into a major showstopper, and half
expect it to be some dumb "noob mistake".
The next paragraph is included as a reference for other REV users; skip
to "The problem:" if you are familiar with these drives.
I (want to) use an Iomega REV drive for backup. These drives use a UDF
filesystem on their exchangeable media, which has a maximum file size of
1Gb. The medium can contain roughly 65Gb of data. I read through the
mailing list archive and the general consensus seems to be to treat the
drive as any removable harddisk, i.e. to use it as a "File" resource.
Due to the file size limit this means you have to create about 65
volumes per physical medium, which is somewhat cumbersome to handle.
Therefore I followed the recommendation in another posting and read
through the Bacula Removable Disk Howto. I configured the vchanger
script to emulate a virtual tape changer and to use autofs to mount the
REV media and needed (and as recommended in the howto).
The problem:
For testing purposes, I configured vchanger to use 2 slots per magazine
and created 2 magazines, i.e. 4 volumes total, all empty and in state
"APPEND". 2 are in the changer; for the other 2 (those in the second
virtual magazine) the "inchanger" flag is 0, as would be expected.
I now start a job that needs more volumes than there are in magazine 1.
All works fine up to the point where the first magazine is completely
full. In this situation, I assume bacula should issue a request to
insert a new volume. I could then switch the physical media and issue a
"update slots" command, thereby making the volumes in the second
magazine available.
However, this is what happens the moment the first magazine is full:
02-Aug 22:55 server-01-sd: End of medium on Volume "m01s002"
Bytes=1,073,737,915 Blocks=16,644 at 02-Aug-2007 22:55.
02-Aug 22:55 server-01-sd: Invalid slot=0 defined, cannot autoload Volume.
02-Aug 22:55 server-01-sd: 3301 Issuing autochanger "loaded? drive 0"
command.
02-Aug 22:55 server-01-sd: 3302 Autochanger "loaded? drive 0", result is
Slot 2.
02-Aug 22:55 server-01-sd: samba.2007-08-02_22.54.02 Warning: Volume
"m02s001" not on device "rev-changer-1-drive-0"
(/var/bacula/rev_vchanger/drive0).
02-Aug 22:55 server-01-sd: Marking Volume "m02s001" in Error in Catalog.
This happens to all volumes that are not in the current magazine.
Instead of requesting the insertion of a new volume, all other known
volumes in the other magazine(s) are marked with state "ERROR" and the
job stops. Does anyone have an idea why this happens and how to
prevent it?
Here is the output of "list volumes" after the error (line
breaks inserted for at least slightly better readability):
+---------+------------+-----------+---------+---------------+----------+--------------+---------+------+-----------+--
---------+---------------------+
| mediaid | volumename | volstatus | enabled | volbytes | volfiles
| volretention | recycle | slot | inchanger | mediatype | lastwritten
|
+---------+------------+-----------+---------+---------------+----------+--------------+---------+------+-----------+--
---------+---------------------+
| 27 | m01s001 | Full | 1 | 1,073,737,908 | 0
| 2,592,000 | 1 | 1 | 1 | File | 2007-08-02
22:54:52 |
| 28 | m01s002 | Full | 1 | 1,073,737,915 | 0
| 2,592,000 | 1 | 2 | 1 | File | 2007-08-02
22:55:44 |
| 29 | m02s001 | Error | 1 | 197 | 0
| 2,592,000 | 1 | 0 | 0 | File | 2007-08-02
22:55:45 |
| 30 | m02s002 | Error | 1 | 197 | 0
| 2,592,000 | 1 | 0 | 0 | File | 2007-08-02
22:55:45 |
+---------+------------+-----------+---------+---------------+----------+--------------+---------+------+-----------+--
---------+---------------------+
Here are the relevant configuration file sections for reference:
# vchanger_1.conf (the config file for the vchanger script
# from the Howto)
baculasd=”rev_vchanger-1”
baculasd_user=root
bconsole=/usr/sbin/bconsole
magslots=2
maxdrive=0
mountpoint=/mnt/rev/magazine
statedir=/var/bacula/rev_vchanger
purgepool=Default
#eof
# Storage section of bacula-dir.conf
Storage {
Name = rev_vchanger-1
Address = <server-address>
SDPort = 9103
Password = "<secret>"
Device = rev-changer-1
Media Type = File
Autochanger = yes;
}
# auto changer definition in bacula-sd.conf
Autochanger {
Name = rev-changer-1
Device = rev-changer-1-drive-0
Changer Command = "/etc/bacula/vchanger %c %o %S %a %d"
Changer Device = "/etc/bacula/vchanger_1.conf"
}
Device {
Name = rev-changer-1-drive-0
DriveIndex = 0
Autochanger = yes;
DeviceType = File
MediaType = File
ArchiveDevice = /var/bacula/rev_vchanger/drive0
RemovableMedia = no;
RandomAccess = yes;
}
Best Regards
Mike Follwerk
--
T²BF IT Services GbR
Daniel Blömer, Mike Follwerk, Marcus Teske
Marie-Curie-Str. 1
D-53359 Rheinbach
Umsatzsteuer-Identifikationsnummer
gem. § 27 a Umsatzsteuergesetz: DE 238268154
Tel. +492226 / 87 21 40
Fax: +492226 / 87 21 49
http://www.tbf-it.de/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
