Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume
Thanks to Ana,
It works without any problem now.
But what do you mean Label Format clauses are strange. Are you sure
whether the same volume is reused ?
Does bacula detect Maximum Volumes greater than 1 so il will automatically
add the number after ?
For ex: monday-2014-11-17001 and monday-2014-11-1700.
Truc
On Tue, Nov 18, 2014 at 7:57 PM, Martin Simmons mar...@lispworks.com
wrote:
Also, I think those Label Format clauses are strange when used with
Recycle =
yes. The volumes will be labelled forever with the creation date
(e.g. monday-2014-11-17), not the recycling date.
__Martin
On Tue, 18 Nov 2014 13:51:57 -0300, Ana Emília M. Arruda said:
Yes, you are correct. That was exactly what ocurred. If you want a 13
days
retention period for your incremental jobs, you will have to configure
a Maximum
Volumes of 2. Also, you have different retention periods for incremental
and full backups (me too). So I would recommend you to have different
pools
for your full and incremental backups.
Best regards,
Ana
On Tue, Nov 18, 2014 at 1:35 PM, Sieu Truc sieut...@gmail.com wrote:
Yes, the actual value is 13, and it caused the problem.
In my opinion, the first week , bacula created successfully the monday
incremental backup, and its status was USED but it had to be wait 13
days.
During that time, in the second week, bacula tried to write again to
the
same volume that is not pruned so it caused the problem. And maybe it
hangs
the remain jobs.
Is it right ?
Or do you have any suggestion ?
Truc
On Tue, Nov 18, 2014 at 5:27 PM, Ana EmÃlia M. Arruda
emiliaarr...@gmail.com wrote:
Hi Sieu,
If you have changed the volume retention for your volumes in the
pool
configuration, this change only is applied to new volumes created.
For the
volumes that were already in the catalog, you should run an update
volume
through bconsole and change this value there too.
Since you said that you have changed from 6 to 13 days your retention
periods, I´m supposing maybe this is your problem with is waiting
on
max storage jobs.
Best regards,
Ana
On Tue, Nov 18, 2014 at 12:39 PM, Sieu Truc sieut...@gmail.com
wrote:
sorry for my mistake, in the pools.conf, the value of parameter
Volume
Retention is all 13 days, not 6 days as above.
Truc
On Tue, Nov 18, 2014 at 4:34 PM, Sieu Truc sieut...@gmail.com
wrote:
Hello,
I have a schedules.conf like
#
# Planification des sauvegardes nfs.
#
Schedule {
Name = schedule_intra1
Run = Level=Incremental Pool=lundi Monday at 22:00
Run = Level=Incremental Pool=mardi Tuesday at 22:00
Run = Level=Incremental Pool=mercredi Wednesday at 22:00
Run = Level=Incremental Pool=jeudi Thursday at 22:00
Run = Level=Incremental Pool=vendredi Friday at 22:00
Run = Level=Incremental Pool=samedi Saturday at 22:00
Run = Level=Full Pool=dimanche_pair w02 w04 w06 w08 w10 w12
w14
w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48
w50 w52
Sunday at 22:00
Run = Level=Full Pool=dimanche_impair w01 w03 w05 w07 w09
w11
w13 w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45
w47 w49
w51 w53 Sunday at 22:00
}
Schedule {
Name = schedule_intra2
Run = Level=Incremental Pool=monday Monday at 22:10
Run = Level=Incremental Pool=tuesday Tuesday at 22:10
Run = Level=Incremental Pool=wednesdayi Wednesday at 22:10
Run = Level=Incremental Pool=thursday Thursday at 22:10
Run = Level=Incremental Pool=friday Friday at 22:10
Run = Level=Incremental Pool=saturday Saturday at 22:10
Run = Level=Full Pool=sunday_even w02 w04 w06 w08 w10 w12
w14
w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48
w50 w52
Sunday at 22:10
Run = Level=Full Pool=sunday_odd w01 w03 w05 w07 w09 w11 w13
w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47
w49 w51
w53 Sunday at 22:10
}
And here the definitions of the pools are:
Pool {
Name = monday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= lundi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format = monday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}
Pool {
Name = tuesday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= mardi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format =
tuesday-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}
}
Pool {
Name = wednesday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1
Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume
You´re welcome Sieu :-)
About the label format: when Bacula recycles a volume, it doesn´t change
the label. So if you have a thursday-2014-11-6 volume, with 13 days
retention period and , then it could be recycled and used by Bacula at
2014-11-27, but your volume name will stay the first label
thursday-2014-11-6. So, in the case of reusing volumes, it is better to not
have dates on volumes names. Instead, maybe you can have thursday-1,
thursday-2, etc.
Best regards,
Ana
On Wed, Nov 19, 2014 at 6:40 AM, Sieu Truc sieut...@gmail.com wrote:
Thanks to Ana,
It works without any problem now.
But what do you mean Label Format clauses are strange. Are you sure
whether the same volume is reused ?
Does bacula detect Maximum Volumes greater than 1 so il will
automatically add the number after ?
For ex: monday-2014-11-17001 and monday-2014-11-1700.
Truc
On Tue, Nov 18, 2014 at 7:57 PM, Martin Simmons mar...@lispworks.com
wrote:
Also, I think those Label Format clauses are strange when used with
Recycle =
yes. The volumes will be labelled forever with the creation date
(e.g. monday-2014-11-17), not the recycling date.
__Martin
On Tue, 18 Nov 2014 13:51:57 -0300, Ana Emília M. Arruda said:
Yes, you are correct. That was exactly what ocurred. If you want a 13
days
retention period for your incremental jobs, you will have to configure
a Maximum
Volumes of 2. Also, you have different retention periods for incremental
and full backups (me too). So I would recommend you to have different
pools
for your full and incremental backups.
Best regards,
Ana
On Tue, Nov 18, 2014 at 1:35 PM, Sieu Truc sieut...@gmail.com wrote:
Yes, the actual value is 13, and it caused the problem.
In my opinion, the first week , bacula created successfully the
monday
incremental backup, and its status was USED but it had to be wait
13 days.
During that time, in the second week, bacula tried to write again to
the
same volume that is not pruned so it caused the problem. And maybe it
hangs
the remain jobs.
Is it right ?
Or do you have any suggestion ?
Truc
On Tue, Nov 18, 2014 at 5:27 PM, Ana EmÃlia M. Arruda
emiliaarr...@gmail.com wrote:
Hi Sieu,
If you have changed the volume retention for your volumes in the
pool
configuration, this change only is applied to new volumes created.
For the
volumes that were already in the catalog, you should run an update
volume
through bconsole and change this value there too.
Since you said that you have changed from 6 to 13 days your retention
periods, I´m supposing maybe this is your problem with is waiting
on
max storage jobs.
Best regards,
Ana
On Tue, Nov 18, 2014 at 12:39 PM, Sieu Truc sieut...@gmail.com
wrote:
sorry for my mistake, in the pools.conf, the value of parameter
Volume
Retention is all 13 days, not 6 days as above.
Truc
On Tue, Nov 18, 2014 at 4:34 PM, Sieu Truc sieut...@gmail.com
wrote:
Hello,
I have a schedules.conf like
#
# Planification des sauvegardes nfs.
#
Schedule {
Name = schedule_intra1
Run = Level=Incremental Pool=lundi Monday at 22:00
Run = Level=Incremental Pool=mardi Tuesday at 22:00
Run = Level=Incremental Pool=mercredi Wednesday at 22:00
Run = Level=Incremental Pool=jeudi Thursday at 22:00
Run = Level=Incremental Pool=vendredi Friday at 22:00
Run = Level=Incremental Pool=samedi Saturday at 22:00
Run = Level=Full Pool=dimanche_pair w02 w04 w06 w08 w10
w12 w14
w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46
w48 w50 w52
Sunday at 22:00
Run = Level=Full Pool=dimanche_impair w01 w03 w05 w07 w09
w11
w13 w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43
w45 w47 w49
w51 w53 Sunday at 22:00
}
Schedule {
Name = schedule_intra2
Run = Level=Incremental Pool=monday Monday at 22:10
Run = Level=Incremental Pool=tuesday Tuesday at 22:10
Run = Level=Incremental Pool=wednesdayi Wednesday at 22:10
Run = Level=Incremental Pool=thursday Thursday at 22:10
Run = Level=Incremental Pool=friday Friday at 22:10
Run = Level=Incremental Pool=saturday Saturday at 22:10
Run = Level=Full Pool=sunday_even w02 w04 w06 w08 w10 w12
w14
w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46
w48 w50 w52
Sunday at 22:10
Run = Level=Full Pool=sunday_odd w01 w03 w05 w07 w09 w11
w13
w15 w17 w19 w21 w23 w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45
w47 w49 w51
w53 Sunday at 22:10
}
And here the definitions of the pools are:
Pool {
Name = monday
Pool Type = Backup
AutoPrune = yes
Volume Retention = 6 days
Volume Use Duration = 1 days
Recycle = yes
#recyclepool= lundi
Maximum Volumes = 1
Recycle Current Volume = yes
Label Format
Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume
*Just to give a personal contribution about the subject*.
1. It's redundant to have date variables on the volume names, since you have
the Label Date information on Bacula Catalog, that can be accessed with the
llist command.
2. For disk backups I like to use something like: Label Format =
${Pool}-${NumVols}, or maybe: ${Pool}-${NumVols}-${Storage}; NumVols is a
incremental counter of volumes in pool, and this way you will have always a
unique name for each volume.
Regards,
=
Heitor Medrado de Faria - LPIC-III | ITIL-F
Faltam poucos dias - Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 2021-8260 | 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
==
- Mensagem original -
De: Ana Emília M. Arruda emiliaarr...@gmail.com
Para: Sieu Truc sieut...@gmail.com
Cc: Martin Simmons mar...@lispworks.com,
Bacula-users@lists.sourceforge.net bacula-users@lists.sourceforge.net
Enviadas: Quarta-feira, 19 de novembro de 2014 10:18:40
Assunto: Re: [Bacula-users] Problem of is waiting on max storage jobs and is
waiting for an appendable volume
You´re welcome Sieu :-)
About the label format: when Bacula recycles a volume, it doesn´t change the
label. So if you have a thursday-2014-11-6 volume, with 13 days retention
period and , then it could be recycled and used by Bacula at 2014-11-27, but
your volume name will stay the first label thursday-2014-11-6. So, in the case
of reusing volumes, it is better to not have dates on volumes names. Instead,
maybe you can have thursday-1, thursday-2, etc.
Best regards,
Ana
On Wed, Nov 19, 2014 at 6:40 AM, Sieu Truc sieut...@gmail.com wrote:
Thanks to Ana,
It works without any problem now.
But what do you mean Label Format clauses are strange. Are you sure whether
the same volume is reused ?
Does bacula detect Maximum Volumes greater than 1 so il will automatically add
the number after ?
For ex: monday -2014-11-17001 and monday -2014-11-1700.
Truc
On Tue, Nov 18, 2014 at 7:57 PM, Martin Simmons mar...@lispworks.com wrote:
blockquote
Also, I think those Label Format clauses are strange when used with Recycle =
yes. The volumes will be labelled forever with the creation date
(e.g. monday-2014-11-17), not the recycling date.
__Martin
On Tue, 18 Nov 2014 13:51:57 -0300, Ana Emília M. Arruda said:
Yes, you are correct. That was exactly what ocurred. If you want a 13 days
retention period for your incremental jobs, you will have to configure
a Maximum
Volumes of 2. Also, you have different retention periods for incremental
and full backups (me too). So I would recommend you to have different pools
for your full and incremental backups.
Best regards,
Ana
On Tue, Nov 18, 2014 at 1:35 PM, Sieu Truc sieut...@gmail.com wrote:
Yes, the actual value is 13, and it caused the problem.
In my opinion, the first week , bacula created successfully the monday
incremental backup, and its status was USED but it had to be wait 13
days.
During that time, in the second week, bacula tried to write again to the
same volume that is not pruned so it caused the problem. And maybe it hangs
the remain jobs.
Is it right ?
Or do you have any suggestion ?
Truc
On Tue, Nov 18, 2014 at 5:27 PM, Ana EmÃlia M. Arruda
emiliaarr...@gmail.com wrote:
Hi Sieu,
If you have changed the volume retention for your volumes in the pool
configuration, this change only is applied to new volumes created. For the
volumes that were already in the catalog, you should run an update
volume
through bconsole and change this value there too.
Since you said that you have changed from 6 to 13 days your retention
periods, I´m supposing maybe this is your problem with is waiting on
max storage jobs.
Best regards,
Ana
On Tue, Nov 18, 2014 at 12:39 PM, Sieu Truc sieut...@gmail.com wrote:
sorry for my mistake, in the pools.conf, the value of parameter Volume
Retention is all 13 days, not 6 days as above.
Truc
On Tue, Nov 18, 2014 at 4:34 PM, Sieu Truc sieut...@gmail.com wrote:
Hello,
I have a schedules.conf like
#
# Planification des sauvegardes nfs.
#
Schedule {
Name = schedule_intra1
Run = Level=Incremental Pool=lundi Monday at 22:00
Run = Level=Incremental Pool=mardi Tuesday at 22:00
Run = Level=Incremental Pool=mercredi Wednesday at 22:00
Run = Level=Incremental Pool=jeudi Thursday at 22:00
Run = Level=Incremental Pool=vendredi Friday at 22:00
Run = Level=Incremental Pool=samedi Saturday at 22:00
Run = Level=Full Pool=dimanche_pair w02 w04 w06 w08 w10 w12 w14
w16 w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 w50
w52
Sunday at 22:00
Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume
I've found this thread very helpful. I have just a couple of questions.
1. I have jobs that backup to disk. It has data spooling turned on and
MAXIMUM CONCURRENT JOBS = 5. They all have the same priority and write
to the same pool. It appears to be working, is this the proper way to
handle concurrent jobs?
2. I have a COPY JOB that kicks later that night that copies from DISK
to TAPE (LTO-5). It too has the same configuration above but it on runs
one job at a time. I sort of expected it to run concurrent and use the
data spooling to make sure everything was in order before writing to the
tape but is always seems to block on storage.
3. Sometimes the individual responsible forgets to put in the tape the
night before. I have a critical job (Priority = 1) that kicks off the
next morning. However it never runs because the tape job is in the
queue waiting for the tape (Priority = 10). Is there a way to make sure
the higher priority job gets run?
Thanks again.
Steve Hammond
On 11/19/2014 7:23 AM, hei...@bacula.com.br wrote:
*Just to give a personal contribution about the subject*.
1. It's redundant to have date variables on the volume names, since
you have the Label Date information on Bacula Catalog, that can be
accessed with the llist command.
2. For disk backups I like to use something like: Label Format =
${Pool}-${NumVols}, or maybe: ${Pool}-${NumVols}-${Storage};
NumVols is a incremental counter of volumes in pool, and this way you
will have always a unique name for each volume.
Regards,
=
Heitor Medrado de Faria - LPIC-III | ITIL-F
Faltam poucos dias - Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 2021-8260 tel:%2B55%2061%202021-8260 | 8268-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
==
*De: *Ana Emília M. Arruda emiliaarr...@gmail.com
*Para: *Sieu Truc sieut...@gmail.com
*Cc: *Martin Simmons mar...@lispworks.com,
Bacula-users@lists.sourceforge.net bacula-users@lists.sourceforge.net
*Enviadas: *Quarta-feira, 19 de novembro de 2014 10:18:40
*Assunto: *Re: [Bacula-users] Problem of is waiting on max storage
jobs and is waiting for an appendable volume
You´re welcome Sieu :-)
About the label format: when Bacula recycles a volume, it doesn´t
change the label. So if you have a thursday-2014-11-6 volume, with 13
days retention period and , then it could be recycled and used by
Bacula at 2014-11-27, but your volume name will stay the first label
thursday-2014-11-6. So, in the case of reusing volumes, it is better
to not have dates on volumes names. Instead, maybe you can have
thursday-1, thursday-2, etc.
Best regards,
Ana
On Wed, Nov 19, 2014 at 6:40 AM, Sieu Truc sieut...@gmail.com
mailto:sieut...@gmail.com wrote:
Thanks to Ana,
It works without any problem now.
But what do you mean Label Format clauses are strange. Are you
sure whether the same volume is reused ?
Does bacula detect Maximum Volumes greater than 1 so il will
automatically add the number after ?
For ex: monday-2014-11-17001 and monday-2014-11-1700.
Truc
On Tue, Nov 18, 2014 at 7:57 PM, Martin Simmons
mar...@lispworks.com mailto:mar...@lispworks.com wrote:
Also, I think those Label Format clauses are strange when used
with Recycle =
yes. The volumes will be labelled forever with the creation date
(e.g. monday-2014-11-17), not the recycling date.
__Martin
On Tue, 18 Nov 2014 13:51:57 -0300, Ana Emília M. Arruda
said:
Yes, you are correct. That was exactly what ocurred. If you
want a 13 days
retention period for your incremental jobs, you will have to
configure
a Maximum
Volumes of 2. Also, you have different retention periods for
incremental
and full backups (me too). So I would recommend you to have
different pools
for your full and incremental backups.
Best regards,
Ana
On Tue, Nov 18, 2014 at 1:35 PM, Sieu Truc
sieut...@gmail.com mailto:sieut...@gmail.com wrote:
Yes, the actual value is 13, and it caused the problem.
In my opinion, the first week , bacula created
successfully the monday
incremental backup, and its status was USED but it had
to be wait 13 days.
During that time, in the second week, bacula tried to
write again to the
same volume that is not pruned so it caused the problem.
And maybe it hangs
the remain jobs.
Re: [Bacula-users] bacula can't make use of multi drives
Thanks for the response heitor,
Is it a bug that bacula cannot write to multiple drives for the jobs in
the same pool? Will there be a fix. Back in March 2014 Wolfgang Denk
wrote it can but how?
http://adsm.org/lists/html/Bacula-users/2014-03/msg00212.html
On 18-11-2014 14:03, hei...@bacula.com.br wrote:
I am trying to make bacula use multi drives in a Fujitsu Tape Library
with no success. Recently I added 3 more drives to bacula
configuration to reduce backup time. But bacula insists on using only
the first drive. Backup jobs are not sent to other suitable tape
drives. Jobs are started at the same time and queued. Jobs in the
queue is waiting for the previous job to finish even if there is a
valid media (tape) for the pool and other drives are idle. I can mount
other drives manually. Is there any other setting I'm missing to make
use of multi-drives? Please advise.
Hey Mr. Suleyman: if you want Bacula to write in more than one drive
simultaneously, the most reliable option is submit the job into
different pools at the same given scheduled time.
Regards,
Heitor Medrado de Faria
Need Bacula training? 10% discount coupon code at Udemy: bacula-users
https://www.udemy.com/bacula-backup-software/?couponCode=bacula-users
+55 61 2021-8260 tel:%2B55%2061%202021-8260 | 8268-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
*De: *Süleyman Kuran sku...@ayk.gov.tr
*Para: *bacula-users bacula-users@lists.sourceforge.net
*Enviadas: *Terça-feira, 18 de novembro de 2014 7:39:33
*Assunto: *[Bacula-users] bacula can't make use of multi drives
Hi,
I am trying to make bacula use multi drives in a Fujitsu Tape Library
with no success. Recently I added 3 more drives to bacula
configuration to reduce backup time. But bacula insists on using only
the first drive. Backup jobs are not sent to other suitable tape
drives. Jobs are started at the same time and queued. Jobs in the
queue is waiting for the previous job to finish even if there is a
valid media (tape) for the pool and other drives are idle. I can mount
other drives manually. Is there any other setting I'm missing to make
use of multi-drives? Please advise.
Regards,
Suleyman
==
CentOS release 6.5 (Final)
Bacula version 5.0.0-12.el6
*C**onfig files:*
*bacula-sd.conf*
==
Storage { # definition of myself
Name = bacula-sd
SDPort = 9103 # Director's port
WorkingDirectory = /var/spool/bacula
Pid Directory = /var/run
* Maximum Concurrent Jobs = 2*
}
Autochanger {
Name = AYKAutochanger
Device = Drive-1
Device = Drive-2
Device = Drive-3
Device = Drive-4
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg9
}
Device {
Name = Drive-1
Drive Index = 0
Media Type = LTO-5
Archive Device = /dev/nst0
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
Random Access = no
Maximum File Size = 10GB
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg9
AutoChanger = yes
}
Device {
Name = Drive-2
Drive Index = 1
Media Type = LTO-5
Archive Device = /dev/nst1
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
Random Access = no
Maximum File Size = 10GB
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg9
AutoChanger = yes
Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
}
Device {
Name = Drive-3
Drive Index = 2
Media Type = LTO-5
Archive Device = /dev/nst2
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
Random Access = no
Maximum File Size = 10GB
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
# Changer Device = /dev/changer
Changer Device = /dev/sg9
AutoChanger = yes
Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
}
Device {
Name = Drive-4
Drive Index = 3
Media Type = LTO-5
Archive Device = /dev/nst3
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
Random Access = no
Maximum File Size = 10GB
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg9
AutoChanger = yes
Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
}
...
===
*ba**cula-dir.conf
*Director {#
Re: [Bacula-users] bacula can't make use of multi drives
Is it a bug that bacula cannot write to multiple drives for the jobs in the
same pool? Will there be a fix. Back in March 2014 Wolfgang Denk wrote it can
but how?
http://adsm.org/lists/html/Bacula-users/2014-03/msg00212.html
It's not a bug, but just the way it's designed.
Prefer Mounted Volumes=no it's a directive that could allow to write multiple
volumes within the same pool at the same time, however this is a little buggy
and not recommended at this time.
Regards,
=
Heitor Medrado de Faria - LPIC-III | ITIL-F
Faltam poucos dias - Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 2021-8260 | 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
==
- Mensagem original -
De: Süleyman Kuran sku...@ayk.gov.tr
Para: hei...@bacula.com.br
Cc: bacula-users bacula-users@lists.sourceforge.net
Enviadas: Quarta-feira, 19 de novembro de 2014 13:04:02
Assunto: Re: [Bacula-users] bacula can't make use of multi drives
Thanks for the response heitor,
Is it a bug that bacula cannot write to multiple drives for the jobs in the
same pool? Will there be a fix. Back in March 2014 Wolfgang Denk wrote it can
but how?
http://adsm.org/lists/html/Bacula-users/2014-03/msg00212.html
On 18-11-2014 14:03, hei...@bacula.com.br wrote:
I am trying to make bacula use multi drives in a Fujitsu Tape Library with no
success. Recently I added 3 more drives to bacula configuration to reduce
backup time. But bacula insists on using only the first drive. Backup jobs are
not sent to other suitable tape drives. Jobs are started at the same time and
queued. Jobs in the queue is waiting for the previous job to finish even if
there is a valid media (tape) for the pool and other drives are idle. I can
mount other drives manually. Is there any other setting I'm missing to make use
of multi-drives? Please advise.
Hey Mr. Suleyman: if you want Bacula to write in more than one drive
simultaneously, the most reliable option is submit the job into different pools
at the same given scheduled time.
Regards,
Heitor Medrado de Faria
Need Bacula training? 10% discount coupon code at Udemy: bacula-users
+55 61 2021-8260 | 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
- Mensagem original -
De: Süleyman Kuran sku...@ayk.gov.tr
Para: bacula-users bacula-users@lists.sourceforge.net
Enviadas: Terça-feira, 18 de novembro de 2014 7:39:33
Assunto: [Bacula-users] bacula can't make use of multi drives
Hi,
I am trying to make bacula use multi drives in a Fujitsu Tape Library with no
success. Recently I added 3 more drives to bacula configuration to reduce
backup time. But bacula insists on using only the first drive. Backup jobs are
not sent to other suitable tape drives. Jobs are started at the same time and
queued. Jobs in the queue is waiting for the previous job to finish even if
there is a valid media (tape) for the pool and other drives are idle. I can
mount other drives manually. Is there any other setting I'm missing to make use
of multi-drives? Please advise.
Regards,
Suleyman
==
CentOS release 6.5 (Final)
Bacula version 5.0.0-12.el6
C onfig files:
bacula-sd.conf
==
Storage { # definition of myself
Name = bacula-sd
SDPort = 9103 # Director's port
WorkingDirectory = /var/spool/bacula
Pid Directory = /var/run
Maximum Concurrent Jobs = 2
}
Autochanger {
Name = AYKAutochanger
Device = Drive-1
Device = Drive-2
Device = Drive-3
Device = Drive-4
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg9
}
Device {
Name = Drive-1
Drive Index = 0
Media Type = LTO-5
Archive Device = /dev/nst0
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
Random Access = no
Maximum File Size = 10GB
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg9
AutoChanger = yes
}
Device {
Name = Drive-2
Drive Index = 1
Media Type = LTO-5
Archive Device = /dev/nst1
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
Random Access = no
Maximum File Size = 10GB
Changer Command = /usr/libexec/bacula/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg9
AutoChanger = yes
Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
}
Device {
Name = Drive-3
Drive Index = 2
Media Type = LTO-5
Archive Device = /dev/nst2
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
Random Access = no
Maximum File Size = 10GB
Changer Command =
Re: [Bacula-users] Incremental Jobs
To reuse the older fileset, you will need to manually delete rows 11, 12 etc
from the fileset table in the catlog and also delete the job records that were
created on 2014-11-18. Dump the catalog to a text file before doing this in
case it breaks something.
Then add the Ignore Fileset Changes = yes option to the fileset.
__Martin
On Tue, 18 Nov 2014 19:06:54 -0200 (BRST), Dante Colo said:
Hi Martin
Here it is my job confs and the db query output below, it seems that there
are duplicated filesets , even on that ones with the same name
(tscobra_database_fileset,tscobra_fileset) , is it possible reuse the older
filesets ?
JobDefs {
Name = defaultjob
Enabled = yes
SpoolData = yes
SpoolSize = 148GB
Messages = Standard
Accurate = yes
Write Bootstrap = /var/bacula/working/%c.bsr
Max Run Time = 60 hours
Incremental Max Run Time = 21 hours
Differential Max Wait Time = 21 hours
Reschedule On Error = yes
Reschedule Interval = 5 minutes
Reschedule Times = 10
Allow mixed priority = yes
}
#
Job {
Name = catalog_backup_job
JobDefs = defaultjob
Type = Backup
Client = zimbra
Level = Full
FileSet= catalog_fileset
Schedule = catalog_daily_backup
SpoolData= no
# This creates an ASCII copy of the catalog
# Arguments to make_catalog_backup.pl are:
# make_catalog_backup.pl catalog-name
RunBeforeJob = /etc/bacula/scripts/make_catalog_backup.pl zimbracatalog
# This deletes the copy of the catalog
RunAfterJob = /etc/bacula/scripts/delete_catalog_backup
Write Bootstrap = /var/bacula/working/%n.bsr
Priority = 10 # run after main backup
Pool = zimbra-local-storage
}
#
Job {
Name = restore_jobs
Type = Restore
Client=salamone-fileserver2
FileSet= default_fileset
Pool = default
Replace = never
Messages = Standard
Where = /backup/bacula/restore
}
#
Job {
Name = tscobra_job
JobDefs = defaultjob
Client = tscobra
Type = Backup
Level = Incremental
FileSet = tscobra_fileset
Pool = zimbra-local-storage
Schedule = daily_backup
Priority = 100
}
#
#
Job {
Name = tscobra_database_job
JobDefs = defaultjob
Client = tscobra
Type = Backup
Level = Incremental
FileSet = tscobra_database_fileset
Pool = zimbra-local-storage
Schedule = daily_backup
Priority = 100
Run Script {
Runs When = Before
Fail Job On Error = yes
Command = \d:/TSCOBRA/BKP/tscobrabkp.bat\
}
}
#
Job {
Name = arquivo_virtual_job
JobDefs = defaultjob
Client = salamone-fileserver2
Type = Backup
Level = Incremental
FileSet = arquivo_virtual_fileset
Pool = zimbra-local-storage
Schedule = daily_backup
Priority = 100
}
#
Job {
Name = arquivo_morto_job
JobDefs = defaultjob
Client = salamone-fileserver2
Type = Backup
Level = Incremental
FileSet = arquivo_morto_fileset
Pool = zimbra-local-storage
Schedule = daily_backup
Priority = 100
}
#
Job {
Name = compartilhado _job
JobDefs = defaultjob
Client = salamone-fileserver2
Type = Backup
Level = Incremental
FileSet = compartilhado _fileset
Pool = zimbra-local-storage
Schedule = daily_backup
Priority = 100
}
#
#
Job {
Name = outros_diretorios_job
JobDefs = defaultjob
Client = salamone-fileserver2
Type = Backup
Level = Incremental
FileSet = outros_diretorios_fileset
Pool = zimbra-local-storage
Schedule = daily_backup
Priority = 100
}
#
Job {
Name = samba_homedirs_job
JobDefs = defaultjob
Client = salamone-fileserver2
base= samba_homedirs_job
Type = Backup
Level = Incremental
FileSet = homedirs_fileset
Pool = zimbra-local-storage
Schedule = daily_backup
Priority = 100
}
#
psql (8.4.20)
Type help for help.
bacula=# SELECT * from fileset;
filesetid | fileset | md5 | createtime
---+++-
2 | samba_outros_diretorios | xl+UB++Dl8tyaC+9HClyMD | 2014-11-07 19:27:21
3 | arquivo_virtual | KW+yR5lQN0+Fsh/tD4/3LA | 2014-11-07 20:00:00
4 | arquivo_morto | d7/xkH/lPU+tcgtp78++vA | 2014-11-07 20:00:00
5 | compartilhado | iVFzOi+2SS+yt4lrU9gEWD | 2014-11-07 20:00:00
6 | samba_homedirs | 90sOS/IPEm+Xw9/ALhl2nB | 2014-11-07 20:00:00
7 | unix_servers_confs_fileset | C7/gERdoLV4g8W+I6H+nDC | 2014-11-11 00:42:32
8 | tscobra_database_fileset | F9k6yHJhY7Vr5F/JVn+/bC | 2014-11-13 18:04:41
9 | tscobra_fileset | FF/H12/zFjYUn/J0R0+t4D | 2014-11-13 19:09:12
10 | catalog_fileset | f7/JDyhoN90Uo7/wui/xgD | 2014-11-17 16:48:46
11 | tscobra_fileset | B4BWN5+niA+Om8Jxw9+Z+D | 2014-11-18 01:19:51
12 | tscobra_database_fileset | mQI1EF+Q+R5JZy1cN7JjVD | 2014-11-18 01:20:04
13 | outros_diretorios_fileset | 93/ui8N8T7/DS75kzV/18A | 2014-11-18 01:20:52
14 | compartilhado_fileset | iVFzOi+2SS+yt4lrU9gEWD | 2014-11-18 10:32:32
15 | arquivo_virtual_fileset | KW+yR5lQN0+Fsh/tD4/3LA | 2014-11-18 10:55:34
(14 rows)
bacula=# select clientid, name from client;
Re: [Bacula-users] Incremental Jobs
On Tue, 18 Nov 2014 17:34:18 -0500, Bill Arlofski said: On 11/18/2014 07:50 AM, Dante Colo wrote: Hello Heitor I tried but wasn't the case, anyway thank you for the suggestion. re: Adding Ignore Fileset Changes = Yes option in fileset. If you add that to a fileset, it will take affect after the first full of that newly modified fileset is complete. I say newly modified fileset because by adding that option, you are in fact changing the fileset, and Bacula will think it needs to run a full. I don't think that is true. The fileset md5 doesn't include boolean options like Ignore Fileset Changes. __Martin -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula can't make use of multi drives
On 11/19/2014 11:10 AM, hei...@bacula.com.br wrote: Is it a bug that bacula cannot write to multiple drives for the jobs in the same pool? Will there be a fix. Back in March 2014 Wolfgang Denk wrote "it can" but how? http://adsm.org/lists/html/Bacula-users/2014-03/msg00212.html It's not a bug, but just the way it's designed. "Prefer Mounted Volumes=no" it's a directive that could allow to write multiple volumes within the same pool at the same time, however this is a little buggy and not recommended at this time. It's not a bug, but it is a little buggy?? I think that the only problem with setting "Prefer Mounted Volumes = no" is that it will result in a lot of moving of a volume back and forth between drives. While it might not be a bug, since it works as advertised, it CAN be a problem. For tape, it will really slow things down because it takes a substantial time to move a tape out of one drive and into another. For disk virtual autochangers, though, the moving between "drives" is simply closing a disk file and then re-opening it, meaning that the delay is very negligible. If there is some other issue, like a race condition that I am not aware of, then that would indeed be a bug in my book. But I have used PreferMountedVolumes=no for disk virtual autochanger without (so far) encountering any such problems, just the swapping between drives. And for disk virtual autochangers, I don't see that as a problem in and of itself. Regards, = Heitor Medrado de Faria- LPIC-III | ITIL-F Faltam poucos dias - Treinamento Telepresencial Bacula:http://www.bacula.com.br/?p=2174 61 2021-8260|8268-4220 Site:www.bacula.com.br|Facebook:heitor.faria|Gtalk:heitorfa...@gmail.com == -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula-Web 7.0.0 released
Dear all, After several month of development, I'm happy to inform you that Bacula-Web version 7.0.0 is available from now. This major feature release include several bug fixes and new features which will surely interest you. The features added in this version are A completly reworked web UI interface I started to work with Twitter Bootstrap, jQuery and Font Awesome to make the web interface more responsive and stop spending hours trying to fix CSS compability issues between different browsers. This transition has also helped me to gain time for the development of the interface. But this is only the first step and even if some display bug are present, I will do the necessary to solve them quickly. Dashboard: Stored Files widget A new widget Stored Files have been added to the new dashboard Bacula director timezone (date/time) From this version the date and time are not taken from web server were Bacula-Web is running. But from the Bacula director server. All details about this new release are available on the news section of the web site http://www.bacula-web.org/news.html Thanks again to all the people who contributed to this release by creating bug reports, feature requests, translation update, etc it would not have been possible without your help guys ;) As usual, any questions or remarks are more than welcome Best regards Davide Franco Project site: www.bacula-web.org -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula can't make use of multi drives
I think that the only problem with setting Prefer Mounted Volumes = no is that it will result in a lot of moving of a volume back and forth between drives. While it might not be a bug, since it works as advertised, it CAN be a problem. For tape, it will really slow things down because it takes a substantial time to move a tape out of one drive and into another. For disk virtual autochangers, though, the moving between drives is simply closing a disk file and then re-opening it, meaning that the delay is very negligible. Mr. Fisher: It's not just that. Eventually Prefer Mounted Volumes = no messes up the autochanger during a random backup and you have to restart storage daemon and sometimes powercycle the tape library. If there is some other issue, like a race condition that I am not aware of, then that would indeed be a bug in my book. But I have used PreferMountedVolumes=no for disk virtual autochanger without (so far) encountering any such problems, just the swapping between drives. And for disk virtual autochangers, I don't see that as a problem in and of itself. I don't know if it is already fixed or if this error happens for all autochangers. But last Bacula System Community Storage whitepapers goes in the same way. Having 2 pools is still safer and more reliable way to do multiple volumes writing. Regards, = Heitor Medrado de Faria - LPIC-III | ITIL-F Faltam poucos dias - Treinamento Telepresencial Bacula: http://www.bacula.com.br/?p=2174 61 2021-8260 | 8268-4220 Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com == - Mensagem original - De: Josh Fisher jfis...@pvct.com Para: bacula-users@lists.sourceforge.net Enviadas: Quarta-feira, 19 de novembro de 2014 14:52:42 Assunto: Re: [Bacula-users] bacula can't make use of multi drives On 11/19/2014 11:10 AM, hei...@bacula.com.br wrote: Is it a bug that bacula cannot write to multiple drives for the jobs in the same pool? Will there be a fix. Back in March 2014 Wolfgang Denk wrote it can but how? http://adsm.org/lists/html/Bacula-users/2014-03/msg00212.html It's not a bug, but just the way it's designed. Prefer Mounted Volumes=no it's a directive that could allow to write multiple volumes within the same pool at the same time, however this is a little buggy and not recommended at this time. It's not a bug, but it is a little buggy?? I think that the only problem with setting Prefer Mounted Volumes = no is that it will result in a lot of moving of a volume back and forth between drives. While it might not be a bug, since it works as advertised, it CAN be a problem. For tape, it will really slow things down because it takes a substantial time to move a tape out of one drive and into another. For disk virtual autochangers, though, the moving between drives is simply closing a disk file and then re-opening it, meaning that the delay is very negligible. If there is some other issue, like a race condition that I am not aware of, then that would indeed be a bug in my book. But I have used PreferMountedVolumes=no for disk virtual autochanger without (so far) encountering any such problems, just the swapping between drives. And for disk virtual autochangers, I don't see that as a problem in and of itself. blockquote Regards, = Heitor Medrado de Faria - LPIC-III | ITIL-F Faltam poucos dias - Treinamento Telepresencial Bacula: http://www.bacula.com.br/?p=2174 61 2021-8260 | 8268-4220 Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com == /blockquote -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk___
Re: [Bacula-users] Problem of is waiting on max storage jobs and is waiting for an appendable volume
Hi Steven,
On Wed, Nov 19, 2014 at 10:48 AM, Steven Hammond bcf1...@gmail.com wrote:
I've found this thread very helpful. I have just a couple of questions.
1. I have jobs that backup to disk. It has data spooling turned on and
MAXIMUM CONCURRENT JOBS = 5. They all have the same priority and write to
the same pool. It appears to be working, is this the proper way to handle
concurrent jobs?
Yes, this is a suitable way to handle concurrent disk backup jobs.
2. I have a COPY JOB that kicks later that night that copies from DISK to
TAPE (LTO-5). It too has the same configuration above but it on runs one
job at a time. I sort of expected it to run concurrent and use the data
spooling to make sure everything was in order before writing to the tape
but is always seems to block on storage.
When writing concurrent jobs to tape, only one job will write to tape at a
time and the other jobs will do data spooling to disk. Can you post a
status dir when copy jobs are running?
3. Sometimes the individual responsible forgets to put in the tape the
night before. I have a critical job (Priority = 1) that kicks off the next
morning. However it never runs because the tape job is in the queue
waiting for the tape (Priority = 10). Is there a way to make sure the
higher priority job gets run?
You can use Max Run Time directives. Specially I use the Max Run Sched
Time to avoid that. Your jobs will run until this time is reached counted
from the scheduled time.
Thanks again.
Steve Hammond
You´re welcome.
Best regards,
Ana
On 11/19/2014 7:23 AM, hei...@bacula.com.br wrote:
*Just to give a personal contribution about the subject*.
1. It's redundant to have date variables on the volume names, since you
have the Label Date information on Bacula Catalog, that can be accessed
with the llist command.
2. For disk backups I like to use something like: Label Format =
${Pool}-${NumVols}, or maybe: ${Pool}-${NumVols}-${Storage}; NumVols is
a incremental counter of volumes in pool, and this way you will have always
a unique name for each volume.
Regards,
=
Heitor Medrado de Faria - LPIC-III | ITIL-F
Faltam poucos dias - Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 2021-8260 %2B55%2061%202021-8260 | 8268-4220 %2B55%2061%208268-4220
Site: www.bacula.com.br | Facebook: heitor.faria
http://www.facebook.com/heitor.faria | Gtalk: heitorfa...@gmail.com
==
--
*De: *Ana Emília M. Arruda emiliaarr...@gmail.com
emiliaarr...@gmail.com
*Para: *Sieu Truc sieut...@gmail.com sieut...@gmail.com
*Cc: *Martin Simmons mar...@lispworks.com mar...@lispworks.com,
Bacula-users@lists.sourceforge.net Bacula-users@lists.sourceforge.net
bacula-users@lists.sourceforge.net bacula-users@lists.sourceforge.net
*Enviadas: *Quarta-feira, 19 de novembro de 2014 10:18:40
*Assunto: *Re: [Bacula-users] Problem of is waiting on max storage jobs
and is waiting for an appendable volume
You´re welcome Sieu :-)
About the label format: when Bacula recycles a volume, it doesn´t change
the label. So if you have a thursday-2014-11-6 volume, with 13 days
retention period and , then it could be recycled and used by Bacula at
2014-11-27, but your volume name will stay the first label
thursday-2014-11-6. So, in the case of reusing volumes, it is better to not
have dates on volumes names. Instead, maybe you can have thursday-1,
thursday-2, etc.
Best regards,
Ana
On Wed, Nov 19, 2014 at 6:40 AM, Sieu Truc sieut...@gmail.com wrote:
Thanks to Ana,
It works without any problem now.
But what do you mean Label Format clauses are strange. Are you sure
whether the same volume is reused ?
Does bacula detect Maximum Volumes greater than 1 so il will
automatically add the number after ?
For ex: monday-2014-11-17001 and monday-2014-11-1700.
Truc
On Tue, Nov 18, 2014 at 7:57 PM, Martin Simmons mar...@lispworks.com
wrote:
Also, I think those Label Format clauses are strange when used with
Recycle =
yes. The volumes will be labelled forever with the creation date
(e.g. monday-2014-11-17), not the recycling date.
__Martin
On Tue, 18 Nov 2014 13:51:57 -0300, Ana Emília M. Arruda said:
Yes, you are correct. That was exactly what ocurred. If you want a 13
days
retention period for your incremental jobs, you will have to configure
a Maximum
Volumes of 2. Also, you have different retention periods for
incremental
and full backups (me too). So I would recommend you to have different
pools
for your full and incremental backups.
Best regards,
Ana
On Tue, Nov 18, 2014 at 1:35 PM, Sieu Truc sieut...@gmail.com wrote:
Yes, the actual value is 13, and it caused the problem.
In my opinion, the first week , bacula created successfully the
[Bacula-users] Configuration help for autochangers
Hello list, I am trying to get my grasp in Bacula configuration with virtual autochangers and I could certainly use some advice from you all. I want to backup data from ~100 hosts. I have no tapes and I want to backup everything into a large, multi TB, disk array. Hosts come and go so my requirement is: if ever a host is deleted, all disk space allocated for this host should be freed (jobs purged + volumes truncated or deleted). I can't restart sd every time a host is added so I'm trying to set up Virtual Autochangers. On the sd I have a single mountpoint (/bacvol02) and I have created directories for a number of hosts greater than the hosts I have now to backup (/bacvol02/host001, /bacvol02/host002, ..., /bacvol02/host999). A virtual autochanger (VA) includes all of these devices. Let's call this autochanger hosts-va. On the director I want to create a job for each host. Data for this host should go into its own directory (ie: jobs on host001 - /bacvol02/host001, jobs on host002 - /bacvol02/host002, etc..). How do I setup the VA on Director's side? Shoud I use pools? Can I use the same Media Type everywhere since there is no mounting/unmounting required? What if I had several jobs for each host (think about separate jobs for every user home): would it be possible to have each job create a volume (maybe with a descriptive label) inside the host device? Eg: job for joe should backup /home/joe on host001. Bacula then creates volumes such as /bacvol02/host001/joe-001, /bacvol02/host001/joe-002, ...) Thanks, .a.c. Andrea -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] multiple archive devices
Hi,
Have a problem with an existing setup.
We do backups to disk, here is one of the device definitions:
Device {
Name = FileStorage
Media Type = File
Archive Device = /mnt/baculaStorage
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
The archive device is starting to run out of space. Is it possible to
have multiple archive devices for a single device definition?
Thanks in advance
JBB
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] multiple archive devices
Hi Jonathan,
On Wed, Nov 19, 2014 at 2:46 PM, Jonathan Bayer linuxguruga...@gmail.com
wrote:
Hi,
Have a problem with an existing setup.
We do backups to disk, here is one of the device definitions:
Device {
Name = FileStorage
Media Type = File
Archive Device = /mnt/baculaStorage
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
The archive device is starting to run out of space. Is it possible to
have multiple archive devices for a single device definition?
No, it is not posible. You will have to redirect your jobs to do the
backups in the new partition mount point if you cannot increase the current
partition size. There are always others solutions but it will depend on
your needs.
Thanks in advance
JBB
Best regards,
Ana
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula can't make use of multi drives
For the sake of sharing information I am going to reply to this thread since I am working on the same type of setup and experiencing similar issues. I removed the setting ‘prefer mounted volumes = no' and separated my jobs into 3 different pools. All my jobs are running smoothly now, no failures. The prefer mounted volumes was the issue. Now I am experiencing interleaving on a single volume/tape drive with multiple jobs scheduled at the same time, in the same pool, as opposed to bacula using different volumes and different drives for jobs scheduled at the same time for the same pool. Here is my issue: I have 10 jobs that kick off at the same time every day. Each job takes anywhere from 10 minutes to 2 hours. The pool behind these jobs has 4 tape drives and 4 volumes(virtual tapes) assigned to it. The 10 jobs all kick off at the same time and they all write to the same volume, apparently(assuming) interleaving the data. See my paste below, Ive bolded start times, end times, pools and tapes. One can see these jobs all completed near each other and ran for over an hour. All to the same tape/volume, tape3 and volume CF5F6A . I assume if I had the prefer mounted volume=no for these jobs they would use all 4 drives in the pool and write to separate volumes as opposed to interleaving to a single drive and volume. But based on the manual, reported problems and experienced problems with ‘prefer mounted volumes = no’ I hesitate to use that. My question: Is there another way to get multiple jobs scheduled at the same time to run concurrently using different drives and volumes, as assigned to the pool, versus all writing at the same time and interleaving the data to a single drive and volume even though the pool has 4 drives/volumes assigned to it?Or is prefer mounted volumes = no the only way to solve this? any help is greatly appreciated 19-Nov 10:06 backup02-sd JobId 925: Job write elapsed time = 01:01:23, Transfer rate = 1.489 M Bytes/second 19-Nov 10:06 backup02-dir JobId 925: Bacula backup02-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu ubuntu 14.04 JobId: 925 Job:labsdb1.2014-11-19_09.05.00_21 Backup Level: Full (upgraded from Differential) Client: labsdb1 2.4.4 (28Dec08) x86_64-pc-linux-gnu,debian,lenny/sid FileSet:Database Backup 2014-11-07 22:02:50 Pool: database (From Job resource) Catalog:MyCatalog (From Client resource) Storage:Tape3 (From Pool resource) Scheduled time: 19-Nov-2014 09:05:00 Start time: 19-Nov-2014 09:05:02 End time: 19-Nov-2014 10:06:26 Elapsed time: 1 hour 1 min 24 secs Priority: 10 FD Files Written: 2 SD Files Written: 2 FD Bytes Written: 5,486,802,781 (5.486 GB) SD Bytes Written: 5,486,802,988 (5.486 GB) Rate: 1489.4 KB/s Software Compression: None VSS:no Encryption: no Accurate: no Volume name(s): CF5F6A Volume Session Id: 155 Volume Session Time:1415816791 Last Volume Bytes: 1,348,311,508,992 (1.348 TB) Non-fatal FD errors:0 SD Errors: 0 FD termination status: OK SD termination status: OK Termination:Backup OK 19-Nov 10:06 backup02-dir JobId 925: Begin pruning Jobs older than 1 year . 19-Nov 10:06 backup02-dir JobId 925: No Jobs found to prune. 19-Nov 10:06 backup02-dir JobId 925: Begin pruning Files. 19-Nov 10:06 backup02-dir JobId 925: No Files found to prune. 19-Nov 10:06 backup02-dir JobId 925: End auto prune. 19-Nov 10:41 backup02-sd JobId 919: Job write elapsed time = 01:36:26, Transfer rate = 2.570 M Bytes/second 19-Nov 10:41 backup02-dir JobId 919: Bacula backup02-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu ubuntu 14.04 JobId: 919 Job:shopd1.2014-11-19_09.05.00_15 Backup Level: Full (upgraded from Differential) Client: shopdb1 5.0.2 (28Apr10) x86_64-pc-linux-gnu,debian,squeeze/sid FileSet:varlibDatabase Backup 2014-11-06 20:20:52 Pool: database (From Job resource) Catalog:MyCatalog (From Client resource) Storage:Tape3 (From Pool resource) Scheduled time: 19-Nov-2014 09:05:00 Start time: 19-Nov-2014 09:05:00 End time: 19-Nov-2014 10:41:26 Elapsed time: 1 hour 36 mins 26 secs Priority: 10 FD Files Written: 3 SD Files Written: 3 FD Bytes Written: 14,875,191,024 (14.87 GB) SD Bytes Written: 14,875,192,011 (14.87 GB) Rate: 2570.9 KB/s Software Compression: None VSS:
Re: [Bacula-users] bacula mixing up slots and volumes with virtual multiple drive autochanger running on Amazon AWS storage gateway
Thank you for your reply. I removed that setting and separated my jobs into 3 different pools. All my jobs are running smoothly now. The prefer mounted volumes was the issue. Now I am experiencing interleaving on a single volume/tape drive with multiple jobs scheduled at the same time, in the same pool, as opposed to bacula using different volumes and different drives for jobs scheduled at the same time for the same pool. Here is my issue: I have 10 jobs that kick off at the same time every day. Each job takes anywhere form 10 minutes to 30 minutes. The pool behind these jobs has 4 tape drives and 4 volumes(virtual tapes) assigned to it. The 10 jobs all kick off at the same time and they all write to the same volume, apparently(assuming) interleaving the data. See my paste below, Ive bolded start times, end times, pools and tapes. Once can see these jobs all completed near each other and ran for over an hour. All to the same tape/volume. I assume if I had the prefer mounted volume=no for these jobs they would use all 4 drives in the pool and write to separate volumes as opposed to interleaving to a single drive and volume. But based on the manual, reported problems and experienced problems with ‘prefer mounted volumes = no’ I hesitate to use that. My question: Is there another way to get multiple jobs scheduled at the same time to run concurrently using different drives and volumes as assigned to the pool versus all writing at the same time and interleaving the data to a single drive and volume?Or is prefer mounted volumes = no the only way to solve this? any help is greatly appreciated 19-Nov 10:06 backup02-sd JobId 925: Job write elapsed time = 01:01:23, Transfer rate = 1.489 M Bytes/second 19-Nov 10:06 backup02-dir JobId 925: Bacula backup02-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu ubuntu 14.04 JobId: 925 Job:labsdb1.2014-11-19_09.05.00_21 Backup Level: Full (upgraded from Differential) Client: labsdb1 2.4.4 (28Dec08) x86_64-pc-linux-gnu,debian,lenny/sid FileSet:Database Backup 2014-11-07 22:02:50 Pool: database (From Job resource) Catalog:MyCatalog (From Client resource) Storage:Tape3 (From Pool resource) Scheduled time: 19-Nov-2014 09:05:00 Start time: 19-Nov-2014 09:05:02 End time: 19-Nov-2014 10:06:26 Elapsed time: 1 hour 1 min 24 secs Priority: 10 FD Files Written: 2 SD Files Written: 2 FD Bytes Written: 5,486,802,781 (5.486 GB) SD Bytes Written: 5,486,802,988 (5.486 GB) Rate: 1489.4 KB/s Software Compression: None VSS:no Encryption: no Accurate: no Volume name(s): CF5F6A Volume Session Id: 155 Volume Session Time:1415816791 Last Volume Bytes: 1,348,311,508,992 (1.348 TB) Non-fatal FD errors:0 SD Errors: 0 FD termination status: OK SD termination status: OK Termination:Backup OK 19-Nov 10:06 backup02-dir JobId 925: Begin pruning Jobs older than 1 year . 19-Nov 10:06 backup02-dir JobId 925: No Jobs found to prune. 19-Nov 10:06 backup02-dir JobId 925: Begin pruning Files. 19-Nov 10:06 backup02-dir JobId 925: No Files found to prune. 19-Nov 10:06 backup02-dir JobId 925: End auto prune. 19-Nov 10:41 backup02-sd JobId 919: Job write elapsed time = 01:36:26, Transfer rate = 2.570 M Bytes/second 19-Nov 10:41 backup02-dir JobId 919: Bacula backup02-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu ubuntu 14.04 JobId: 919 Job:shopd1.2014-11-19_09.05.00_15 Backup Level: Full (upgraded from Differential) Client: shopdb1 5.0.2 (28Apr10) x86_64-pc-linux-gnu,debian,squeeze/sid FileSet:varlibDatabase Backup 2014-11-06 20:20:52 Pool: database (From Job resource) Catalog:MyCatalog (From Client resource) Storage:Tape3 (From Pool resource) Scheduled time: 19-Nov-2014 09:05:00 Start time: 19-Nov-2014 09:05:00 End time: 19-Nov-2014 10:41:26 Elapsed time: 1 hour 36 mins 26 secs Priority: 10 FD Files Written: 3 SD Files Written: 3 FD Bytes Written: 14,875,191,024 (14.87 GB) SD Bytes Written: 14,875,192,011 (14.87 GB) Rate: 2570.9 KB/s Software Compression: None VSS:no Encryption: yes Accurate: no Volume name(s): CF5F6A Volume Session Id: 149 Volume Session Time:1415816791 Last Volume Bytes: 1,375,507,574,784 (1.375 TB)
Re: [Bacula-users] bacula can't make use of multi drives
Hi Jared, Can you post here your storage configurations? Best regards, Ana On Wed, Nov 19, 2014 at 3:56 PM, Kelley, Jared jkel...@popcap.com wrote: For the sake of sharing information I am going to reply to this thread since I am working on the same type of setup and experiencing similar issues. I removed the setting ‘prefer mounted volumes = no' and separated my jobs into 3 different pools. All my jobs are running smoothly now, no failures. The prefer mounted volumes was the issue. Now I am experiencing interleaving on a single volume/tape drive with multiple jobs scheduled at the same time, in the same pool, as opposed to bacula using different volumes and different drives for jobs scheduled at the same time for the same pool. Here is my issue: I have 10 jobs that kick off at the same time every day. Each job takes anywhere from 10 minutes to 2 hours. The pool behind these jobs has 4 tape drives and 4 volumes(virtual tapes) assigned to it. The 10 jobs all kick off at the same time and they all write to the same volume, apparently(assuming) interleaving the data. See my paste below, Ive bolded start times, end times, pools and tapes. One can see these jobs all completed near each other and ran for over an hour. All to the same tape/volume, tape3 and volume *CF5F6A* . I assume if I had the prefer mounted volume=no for these jobs they would use all 4 drives in the pool and write to separate volumes as opposed to interleaving to a single drive and volume. But based on the manual, reported problems and experienced problems with ‘prefer mounted volumes = no’ I hesitate to use that. My question: Is there another way to get multiple jobs scheduled at the same time to run concurrently using different drives and volumes, as assigned to the pool, versus all writing at the same time and interleaving the data to a single drive and volume even though the pool has 4 drives/volumes assigned to it?Or is prefer mounted volumes = no the only way to solve this? any help is greatly appreciated 19-Nov 10:06 backup02-sd JobId 925: Job write elapsed time = 01:01:23, Transfer rate = 1.489 M Bytes/second 19-Nov 10:06 backup02-dir JobId 925: Bacula backup02-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu ubuntu 14.04 JobId: 925 Job:labsdb1.2014-11-19_09.05.00_21 Backup Level: Full (upgraded from Differential) Client: labsdb1 2.4.4 (28Dec08) x86_64-pc-linux-gnu,debian,lenny/sid FileSet:Database Backup 2014-11-07 22:02:50 P*ool: database (From Job resource)* Catalog:MyCatalog (From Client resource) *Storage:Tape3 (From Pool resource)* *Scheduled time: 19-Nov-2014 09:05:00* * Start time: 19-Nov-2014 09:05:02* *End time: 19-Nov-2014 10:06:26* Elapsed time: 1 hour 1 min 24 secs Priority: 10 FD Files Written: 2 SD Files Written: 2 FD Bytes Written: 5,486,802,781 (5.486 GB) SD Bytes Written: 5,486,802,988 (5.486 GB) Rate: 1489.4 KB/s Software Compression: None VSS:no Encryption: no Accurate: no *Volume name(s): CF5F6A* Volume Session Id: 155 Volume Session Time:1415816791 Last Volume Bytes: 1,348,311,508,992 (1.348 TB) Non-fatal FD errors:0 SD Errors: 0 FD termination status: OK SD termination status: OK Termination:Backup OK 19-Nov 10:06 backup02-dir JobId 925: Begin pruning Jobs older than 1 year . 19-Nov 10:06 backup02-dir JobId 925: No Jobs found to prune. 19-Nov 10:06 backup02-dir JobId 925: Begin pruning Files. 19-Nov 10:06 backup02-dir JobId 925: No Files found to prune. 19-Nov 10:06 backup02-dir JobId 925: End auto prune. 19-Nov 10:41 backup02-sd JobId 919: Job write elapsed time = 01:36:26, Transfer rate = 2.570 M Bytes/second 19-Nov 10:41 backup02-dir JobId 919: Bacula backup02-dir 5.2.6 (21Feb12): Build OS: x86_64-pc-linux-gnu ubuntu 14.04 JobId: 919 Job:shopd1.2014-11-19_09.05.00_15 Backup Level: Full (upgraded from Differential) Client: shopdb1 5.0.2 (28Apr10) x86_64-pc-linux-gnu,debian,squeeze/sid FileSet:varlibDatabase Backup 2014-11-06 20:20:52 *Pool: database (From Job resource)* Catalog:MyCatalog (From Client resource) *Storage:Tape3 (From Pool resource)* *Scheduled time: 19-Nov-2014 09:05:00* * Start time: 19-Nov-2014 09:05:00* *End time: 19-Nov-2014 10:41:26* Elapsed time: 1 hour 36 mins 26 secs Priority:
Re: [Bacula-users] bacula can't make use of multi drives
Sure, here is my bacula-sd.conf and bacula-dir.conf. passwords and addresses
edited for security reasons.
# Default Bacula Storage Daemon Configuration file
#
# For Bacula release 3.0.1 (30 April 2009) -- debian 5.0.1
#
# 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 = backup02-sd
SDPort = 9103 # Director's port
WorkingDirectory = /etc/bacula/working
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
}
# List Directors who are permitted to contact Storage daemon
#
Director {
Name = backup02-dir
Password = “PASSWORD
}
## Restricted Director, used by tray-monitor to get the
# status of the storage daemon
##
Director {
Name = backup02-mon
Password = “PASSWORD
Monitor = yes
}
Autochanger {
Name = Autochanger
Device = Drive-1, Drive-2, Drive-3, Drive-4, Drive-5, Drive-6, Drive-7,
Drive-8, Drive-9, Drive-10
Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg12
}
Device {
Name = Drive-1
Drive Index = 0
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-01-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-2
Drive Index = 1
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-02-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-3
Drive Index = 2
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-03-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-4
Drive Index = 3
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-04-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-5
Drive Index = 4
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-05-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-6
Drive Index = 5
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-06-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-7
Drive Index = 6
Media Type = LTO
Archive Device =
Re: [Bacula-users] bacula can't make use of multi drives
Hi Jared,
In your bacula-sd.conf, you have defined an autochanger device:
Name = Autochanger
Device = Drive-1, Drive-2, Drive-3, Drive-4, Drive-5, Drive-6, Drive-7,
Drive-8, Drive-9, Drive-10
...
}
But, in your bacula-sd.conf, you don't use it. Instead, you have a storage
definition for each of your tape devices, like the bellow one for the
Drive-1:
Storage {
Name = Tape1
Address = backup # N.B. Use a fully qualified name here, not
localhost
SDPort = 9103
Password = “PASSWORD # password for SD
Device = Drive-1
Media Type = LTO
Autochanger = yes # enable for autochanger device
Maximum Concurrent Jobs = 20
}
This way, you are not using an autochanger nor a group of devices, but
stand alone tape drives.
If you want to use the autochanger, in your bacula-dir.conf, you should
have just one storage definition for your autochanger, like (note that the
Device name in your bacula-dir.conf is the same as the Autochanger Name in
your bacula-sd.conf):
Storage {
Name =
Autochanger-sd
Address = backup # N.B. Use a fully qualified name here, not
localhost
SDPort = 9103
Password = “PASSWORD # password for SD
Device =
Autochanger
Media Type = LTO
Autochanger = yes # enable for autochanger device
Maximum Concurrent Jobs = 20
}
Also, could you please confirm if the bellow definitions in your pools are
really working?
Pool {
Name = Default
Pool Type = Backup
Storage = Tape7, Tape8, Tape9, Tape10
...
}
Is it really possible to have more than one storage in the storage
directive definition above? Because I really think that the storage
directive accepts just one storage entry definition. And if you have
defined an autochanger in your bacula-dir.conf, so this should be something
like:
Pool {
Name = Default
Pool Type = Backup
Storage = Autochanger-sd
...
}
Best regards,
Ana
On Wed, Nov 19, 2014 at 5:01 PM, Kelley, Jared jkel...@popcap.com wrote:
Sure, here is my bacula-sd.conf and bacula-dir.conf. passwords and
addresses edited for security reasons.
# Default Bacula Storage Daemon Configuration file
#
# For Bacula release 3.0.1 (30 April 2009) -- debian 5.0.1
#
# 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 = backup02-sd
SDPort = 9103 # Director's port
WorkingDirectory = /etc/bacula/working
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
}
# List Directors who are permitted to contact Storage daemon
#
Director {
Name = backup02-dir
Password = “PASSWORD
}
## Restricted Director, used by tray-monitor to get the
# status of the storage daemon
##
Director {
Name = backup02-mon
Password = “PASSWORD
Monitor = yes
}
Autochanger {
Name = Autochanger
Device = Drive-1, Drive-2, Drive-3, Drive-4, Drive-5, Drive-6, Drive-7,
Drive-8, Drive-9, Drive-10
Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
Changer Device = /dev/sg12
}
Device {
Name = Drive-1
Drive Index = 0
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-01-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-2
Drive Index = 1
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-02-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = 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'
SpoolDirectory = /etc/bacula/spool
Maximum Concurrent Jobs = 20
Maximum Changer Wait = 10 minutes
}
Device {
Name = Drive-3
Drive Index = 2
Media Type = LTO
Archive Device =
/dev/tape/by-path/ip-:3260-iscsi-iqn.1997-05.com.amazon:sgw-20b85d49-tapedrive-03-lun-0-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
LabelMedia = no;
AutoChanger = yes
# Enable the Alert command only if
