[Bacula-users] Use multiple HDDs to backup files to
Hi there, thank you very much. There have been editable values on some bacula-configurations. In 2 of 3 cases the value has been 20 - in one case (bacula-dir.conf) the value was set to 1. how can I make sure that the concurrent jobs are going to the same value? +-- |This was sent by r...@ehrenwert.it via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Use multiple HDDs to backup files to
Alright - I solved it using LVM.
Now I've got another question: Is it possible to run multiple backups at the
same time?
This is my bacula-sd.conf at the moment:
#
# Default Bacula Storage Daemon Configuration file
#
# For Bacula release 5.2.6 (21 February 2012) -- debian jessie/sid
#
# You may need to change the name of your tape drive
# on the Archive Device directive in the Device
# resource. If you change the Name and/or the
# Media Type in the Device resource, please ensure
# that dird.conf has corresponding changes.
#
Storage { # definition of myself
Name = archiv-sd
SDPort = 9103 # Director's port
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
#SDAddress = 127.0.0.1
SDAddress = archiv.myserver.com
}
#
# List Directors who are permitted to contact Storage daemon
#
Director {
Name = archiv-dir
Password = U3fAurzWQLQa-yiNtt_ncXIcopObxuDPw
}
#
# Restricted Director, used by tray-monitor to get the
# status of the storage daemon
#
Director {
Name = archiv-mon
Password = 5JE0u-IcgQrViQG_MDv6BzmNFS_UZF3CM
Monitor = yes
}
#
# Note, for a list of additional Device templates please
# see the directory bacula-source/examples/devices
# Or follow the following link:
#
http://bacula.svn.sourceforge.net/viewvc/bacula/trunk/bacula/examples/devices/
#
#
# Devices supported by this Storage daemon
# To connect, the Director's bacula-dir.conf must have the
# same Name and MediaType.
#
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;
}
#
# An autochanger device with two drives
#
#Autochanger {
# Name = Autochanger
# Device = Drive-1
# Device = Drive-2
# Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
# Changer Device = /dev/sg0
#}
#Device {
# Name = Drive-1 #
# Drive Index = 0
# Media Type = DLT-8000
# Archive Device = /dev/nst0
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# AutoChanger = yes
# #
# # Enable the Alert command only if you have the mtx package loaded
# # Note, apparently on some systems, tapeinfo resets the SCSI controller
# # thus if you turn this on, make sure it does not reset your SCSI
# # controller. I have never had any problems, and smartctl does
# # not seem to cause such problems.
# #
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = sh -c 'smartctl -H -l error %c'
#}
#Device {
# Name = Drive-2 #
# Drive Index = 1
# Media Type = DLT-8000
# Archive Device = /dev/nst1
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# AutoChanger = yes
# # Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = sh -c 'smartctl -H -l error %c'
#}
#
# A Linux or Solaris LTO-2 tape drive
#
#Device {
# Name = LTO-2
# Media Type = LTO-2
# Archive Device = /dev/nst0
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# Maximum File Size = 3GB
## Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
## Changer Device = /dev/sg0
## AutoChanger = yes
# # Enable the Alert command only if you have the mtx package loaded
## Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
## If you have smartctl, enable this, it has more info than tapeinfo
## Alert Command = sh -c 'smartctl -H -l error %c'
#}
#
# A Linux or Solaris LTO-3 tape drive
#
#Device {
# Name = LTO-3
# Media Type = LTO-3
# Archive Device = /dev/nst0
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# Maximum File Size = 4GB
## Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
## Changer Device = /dev/sg0
## AutoChanger = yes
# # Enable the Alert command only if you have the mtx package loaded
## Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
## If you have smartctl, enable this, it has more info than tapeinfo
## Alert Command = sh -c 'smartctl -H -l error %c'
#}
#
# A Linux or Solaris LTO-4 tape drive
#
#Device {
# Name = LTO-4
# Media Type = LTO-4
# Archive
Re: [Bacula-users] Use multiple HDDs to backup files to
Now I've got another question: Is it possible to run multiple backups at the same time? Yes of course. You most likely have to increase the maximum concurrent jobs setting in 3 or so places to do so and if you only have a single device in your storage make sure the concurrent jobs all go to the same volume. John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
In 2 of 3 cases the value has been 20 - in one case (bacula-dir.conf) the value was set to 1. how can I make sure that the concurrent jobs are going to the same value? They do not need to be the same value. They all control different levels of concurrency (jobs, individual clients, storage, director). John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Use multiple HDDs to backup files to
Okay, so because the dir-conf was set to 1, there was only one job running at the same time. Now I set it to 5 - so there will be 5 jobs running? So how can I make sure that all jobs are being written to the same volume? +-- |This was sent by r...@ehrenwert.it via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
On Fri, Jun 12, 2015 at 10:33 AM, SPQR bacula-fo...@backupcentral.com wrote: Okay, so because the dir-conf was set to 1, there was only one job running at the same time. Now I set it to 5 - so there will be 5 jobs running? So how can I make sure that all jobs are being written to the same volume? Don't use directives such as Use Volume once / Maximum use duration ... And make sure the jobs go to the same pool. John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
On 6/2/2015 1:42 PM, Heitor Faria wrote:
I particularly do not like the idea of having separate volumes of
the same media type into two different mount points, but I know
people that are configuring this way. So I decided to do some
tests and see what really was happening. No issues. Instead I
prefer the LVM solution.
The point is to make sure severall disks are being write at the same
time (load balance) and more resiliency since a dead LVM is a terrible
situation.
But I kind of agree with you: I don't know why to use different Media
Types for compatible media.
Because, using the previous example config, volumes in directory
/sdb1/bacula/backup cannot be loaded into vDrive1 and volumes in
directory /bacula/backup cannot be loaded into vDrive2. Bacula uses the
MediaType to decide which volumes can be loaded into which Devices. A
backup job will run without error, writing to either one directory or
the other. But unless tvDrive1 and vDrive2 have different Media Types, a
subsequent restore job will assume it can load any of those volumes into
whichever Device it happens to get assigned to read from.
Regards,
===
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems
Certified Administrator II
15 a 26 de junho: Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 tel:%2B55%2061%202021-82608268-4220 tel:%2B55%2061%208268-4220
Site: www.bacula.com.br http://www.bacula.com.br/ | Facebook:
heitor.faria http://www.facebook.com/heitor.faria | Gtalk:
heitorfa...@gmail.com mailto:heitorfa...@gmail.com
On Tue, Jun 2, 2015 at 2:12 PM, Bryn Hughes li...@nashira.ca
mailto:li...@nashira.ca wrote:
Do you have some specific reason to need to have these two
volumes separate?
You might be best off using LVM to create a single logical
drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
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 http://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 r...@ehrenwert.it mailto:r...@ehrenwert.it
via Backup Central.
|Forward SPAM to ab...@backupcentral.com
mailto:ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
mailto:Bacula-users@lists.sourceforge.net
Re: [Bacula-users] Use multiple HDDs to backup files to
On 6/2/2015 12:43 PM, Ana Emília M. Arruda wrote:
Hello Josh,
On Tue, Jun 2, 2015 at 8:12 AM, Josh Fisher jfis...@pvct.com
mailto:jfis...@pvct.com wrote:
On 6/1/2015 5:21 PM, Ana Emília M. Arruda wrote:
Hello,
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
http://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.
Yes. For a backup job using automatic labeling, it will indeed work. But
that is misleading. Say on 1 June a full job ran using vDrive1 and wrote
to volume full_1 in directory /bacula/backup. On 2 June an incremental
job is run, only this time it was assigned vDrive2 and wrote to volume
inc_1 in directory /sdb1/bacula/backup. Both of these jobs will run
without error. However, now a restore is impossible, as is a subsequent
Virtual Full job.
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
or
Use vchanger, which is designed for using multiple removable HDDs
(See http://sourceforge.net/projects/vchanger/)
or
Combine the HDD partitions using LVM2 or md so that there is only
a single mountpoint
.
bacula-sd.conf:
Autochanger {
Name = VChanger
Changer Device = /dev/null
Changer Command = # versão 5.2.6. For 7.0.5 version, use /dev/null
Device = vDrive-1, vDrive-2
}
Device {
Name = vDrive-1
Drive Index = 0
Device Type = File
Media Type = File
Archive Device = /bacula/backup
...
}
Device {
Name = vDrive-2
Drive Index = 1
Device Type = File
Media Type = File
Archive Device = /sdb1/bacula/backup # is this your mount point?
...
}
In your bacula-dir.conf (or wherever you have your storage
definiton for director):
Storage {
Name = MyVirtualAutochanger
Address = X.X.X.X
SDPort = 9103
Password = xx
Device = VChanger
Media Type = File
Maximum Concurrent Jobs = XX
Autochanger=yes
}
Best regards,
Ana
On Wed, May 20, 2015 at 1:32 PM, SPQR
bacula-fo...@backupcentral.com
mailto:bacula-fo...@backupcentral.com wrote:
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 http://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
Re: [Bacula-users] Use multiple HDDs to backup files to
Ana,
You are right. Now I understand this workaround.
Regards,
===
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified
Administrator II
15 a 26 de junho: Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria
De: Ana Emília M. Arruda emiliaarr...@gmail.com
Para: Josh Fisher jfis...@pvct.com
Cc: Bacula-users@lists.sourceforge.net bacula-users@lists.sourceforge.net
Enviadas: Quarta-feira, 3 de junho de 2015 15:19:23
Assunto: Re: [Bacula-users] Use multiple HDDs to backup files to
Thank you Josh.
I read in the Best Practices for Disk Based Backup white paper this
recommendation (different media types for different mount points). Lots of
people were reporting that this was working fine. So I had been testing the
backup with this configuration, not the restores. Now I see that in the case
of
a restore, this will only work for volumes that are in the first device (mount
point).
Best regards,
Ana
On Wed, Jun 3, 2015 at 10:21 AM, Josh Fisher jfis...@pvct.com wrote:
On 6/2/2015 1:42 PM, Heitor Faria wrote:
I particularly do not like the idea of having separate volumes of the same
media
type into two different mount points, but I know people that are
configuring
this way. So I decided to do some tests and see what really was happening.
No
issues. Instead I prefer the LVM solution.
The point is to make sure severall disks are being write at the same time
(load
balance) and more resiliency since a dead LVM is a terrible situation.
But I kind of agree with you: I don't know why to use different Media Types
for
compatible media.
Because, using the previous example config, volumes in directory
/sdb1/bacula/backup cannot be loaded into vDrive1 and volumes in directory
/bacula/backup cannot be loaded into vDrive2. Bacula uses the MediaType to
decide which volumes can be loaded into which Devices. A backup job will run
without error, writing to either one directory or the other. But unless
tvDrive1 and vDrive2 have different Media Types, a subsequent restore job
will
assume it can load any of those volumes into whichever Device it happens to
get
assigned to read from.
Regards,
===
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified
Administrator II
15 a 26 de junho: Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk:
heitorfa...@gmail.com
On Tue, Jun 2, 2015 at 2:12 PM, Bryn Hughes li...@nashira.ca wrote:
Do you have some specific reason to need to have these two volumes
separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
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 r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com
Re: [Bacula-users] Use multiple HDDs to backup files to
Thank you Josh.
I read in the Best Practices for Disk Based Backup white paper this
recommendation (different media types for different mount points). Lots of
people were reporting that this was working fine. So I had been testing the
backup with this configuration, not the restores. Now I see that in the
case of a restore, this will only work for volumes that are in the first
device (mount point).
Best regards,
Ana
On Wed, Jun 3, 2015 at 10:21 AM, Josh Fisher jfis...@pvct.com wrote:
On 6/2/2015 1:42 PM, Heitor Faria wrote:
I particularly do not like the idea of having separate volumes of the
same media type into two different mount points, but I know people that are
configuring this way. So I decided to do some tests and see what really was
happening. No issues. Instead I prefer the LVM solution.
The point is to make sure severall disks are being write at the same time
(load balance) and more resiliency since a dead LVM is a terrible situation.
But I kind of agree with you: I don't know why to use different Media
Types for compatible media.
Because, using the previous example config, volumes in directory
/sdb1/bacula/backup cannot be loaded into vDrive1 and volumes in directory
/bacula/backup cannot be loaded into vDrive2. Bacula uses the MediaType to
decide which volumes can be loaded into which Devices. A backup job will
run without error, writing to either one directory or the other. But unless
tvDrive1 and vDrive2 have different Media Types, a subsequent restore job
will assume it can load any of those volumes into whichever Device it
happens to get assigned to read from.
Regards,
===
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified
Administrator II
15 a 26 de junho: Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 %2B55%2061%202021-82608268-4220 %2B55%2061%208268-4220
Site: www.bacula.com.br | Facebook: heitor.faria
http://www.facebook.com/heitor.faria | Gtalk: heitorfa...@gmail.com
On Tue, Jun 2, 2015 at 2:12 PM, Bryn Hughes li...@nashira.ca wrote:
Do you have some specific reason to need to have these two volumes
separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
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 r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
On 6/1/2015 5:21 PM, Ana Emília M. Arruda wrote:
Hello,
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.
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
or
Use vchanger, which is designed for using multiple removable HDDs (See
http://sourceforge.net/projects/vchanger/)
or
Combine the HDD partitions using LVM2 or md so that there is only a
single mountpoint
.
bacula-sd.conf:
Autochanger {
Name = VChanger
Changer Device = /dev/null
Changer Command = # versão 5.2.6. For 7.0.5 version, use /dev/null
Device = vDrive-1, vDrive-2
}
Device {
Name = vDrive-1
Drive Index = 0
Device Type = File
Media Type = File
Archive Device = /bacula/backup
...
}
Device {
Name = vDrive-2
Drive Index = 1
Device Type = File
Media Type = File
Archive Device = /sdb1/bacula/backup # is this your mount point?
...
}
In your bacula-dir.conf (or wherever you have your storage definiton
for director):
Storage {
Name = MyVirtualAutochanger
Address = X.X.X.X
SDPort = 9103
Password = xx
Device = VChanger
Media Type = File
Maximum Concurrent Jobs = XX
Autochanger=yes
}
Best regards,
Ana
On Wed, May 20, 2015 at 1:32 PM, SPQR bacula-fo...@backupcentral.com
mailto:bacula-fo...@backupcentral.com wrote:
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 http://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 r...@ehrenwert.it mailto:r...@ehrenwert.it via
Backup Central.
|Forward SPAM to ab...@backupcentral.com
mailto:ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
mailto:Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
Do you have some specific reason to need to have these two volumes separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
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 r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
I particularly do not like the idea of having separate volumes of the same
media type into two different mount points, but I know people that are
configuring this way. So I decided to do some tests and see what really was
happening. No issues. Instead I prefer the LVM solution.
On Tue, Jun 2, 2015 at 2:12 PM, Bryn Hughes li...@nashira.ca wrote:
Do you have some specific reason to need to have these two volumes
separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
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 r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
I particularly do not like the idea of having separate volumes of the same
media
type into two different mount points, but I know people that are configuring
this way. So I decided to do some tests and see what really was happening. No
issues. Instead I prefer the LVM solution.
The point is to make sure severall disks are being write at the same time (load
balance) and more resiliency since a dead LVM is a terrible situation.
But I kind of agree with you: I don't know why to use different Media Types for
compatible media.
Regards,
===
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified
Administrator II
15 a 26 de junho: Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
On Tue, Jun 2, 2015 at 2:12 PM, Bryn Hughes li...@nashira.ca wrote:
Do you have some specific reason to need to have these two volumes separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
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 r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com .
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Use multiple HDDs to backup files to
Hello,
Maybe you could use the virtual autochanger resource:
bacula-sd.conf:
Autochanger {
Name = VChanger
Changer Device = /dev/null
Changer Command = # versão 5.2.6. For 7.0.5 version, use /dev/null
Device = vDrive-1, vDrive-2
}
Device {
Name = vDrive-1
Drive Index = 0
Device Type = File
Media Type = File
Archive Device = /bacula/backup
...
}
Device {
Name = vDrive-2
Drive Index = 1
Device Type = File
Media Type = File
Archive Device = /sdb1/bacula/backup # is this your mount point?
...
}
In your bacula-dir.conf (or wherever you have your storage definiton for
director):
Storage {
Name = MyVirtualAutochanger
Address = X.X.X.X
SDPort = 9103
Password = xx
Device = VChanger
Media Type = File
Maximum Concurrent Jobs = XX
Autochanger=yes
}
Best regards,
Ana
On Wed, May 20, 2015 at 1:32 PM, SPQR bacula-fo...@backupcentral.com
wrote:
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 r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Use multiple HDDs to backup files to
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 r...@ehrenwert.it via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
