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
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
*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 =
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
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,
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
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 =
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
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?
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
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
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
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
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;
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 =
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
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
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
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
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
20 matches
Mail list logo
