Maybe
you could use the "virtual autochanger" resource:
This will not work as expected. If the ArchiveDevice in the two
Device resources specifies different directories (mountpoints), then
the two Device resources cannot have the same MediaType. This is
because Bacula expects to be able to load any volume that has
MediaType=File into any Device having that same MediaType, and a
volume in
/sdb1/bacula/backup cannot be loaded into
Device
vDrive-1,
not can a volume in
/bacula/backup be loaded into
vDrive-2.
No, volumes in
/sdb1/bacula/backup will not be loaded into
vDrive-1 and volumes in
/bacula/backup will not be loaded into
vDrive-2. I read about this in the white papers from blog.bacula.org. I decided to do some tests with this. Lots of people are working with virtual autochangers this way. When you submit concurrent jobs, the volumes are mounted into their respective devices. If a requested volume is in
/sdb1/bacula/backup, it will be loaded into
vDrive-1 and if a requested volume is in
/bacula/backup, it will be loaded into
vDrive-2. This works this way and gives no error. But I agree with you that the option using LVM is a lot better.
Best regards,
Ana
To use multiple HDDs as a single autochanger, you must:
Define each Device resource to have a unique MediaType, if using the
native virtual autochanger
I would
like to set up bacula - well, my first steps have been
successful.
All my backups are written to /bacula/backup. But / has only
900GB. So I want bacula to write to /sdb1/bacula/backup,
too. /sdb1 has another 950GB of space. The sum of available
backup-space should be 1850GB HDD:
Well, I got the following config of
/etc/bacula/bacula-sd.conf:
>
> Storage { # definition of
myself
> Name = backup-sd
> SDPort = 9103 # Director's port
> WorkingDirectory = "/var/lib/bacula"
> Pid Directory = "/var/run/bacula"
> Maximum Concurrent Jobs = 20
> SDAddress = backup.example.com
> }
>
> Director {
> Name = backup-dir
> Password = "doyoureallywanttoknow"
> }
> Device {
> Name = FileStorage
> Media Type = File
> Archive Device = /bacula/backup
> LabelMedia = yes; # lets Bacula
label unlabeled media
> Random Access = Yes;
> AutomaticMount = yes; # when device
opened, read it
> RemovableMedia = no;
> AlwaysOpen = no;
> }
>
Okay - now I would like to add another device. I guess I
could just add a second entry like this:
>
> Device {
> Name = FileStorage
> Media Type = File
> Archive Device = /sdb1/bacula/backup
> LabelMedia = yes; # lets Bacula
label unlabeled media
> Random Access = Yes;
> AutomaticMount = yes; # when device
opened, read it
> RemovableMedia = no;
> AlwaysOpen = no;
> }
>
?
Do I have to change something else so that bacula is able to
write more than 900GB - if the first 900GB are "full" it
should switch to the second hdd.
Thank you very much :-)
+----------------------------------------------------------------------
|This was sent by rlb AT ehrenwert DOT it via
Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------