On 11/03/2015 07:24 AM, Wesley Render wrote:
> I have recently started using Bacula and have a couple of questions
> regarding volume pools. I am using 7.2 version, and we have 4 Linux
> servers with a total of about 100GB of data to backup.
>
> 1. We have two different storage devices that a
On 11/05/2015 11:02 AM, Wesley Render wrote:
>
> In case this helps anyone. I ended up having problems with setting
> volume limits. For example I suddenly decided to adjust our
> incremental backups to run every 4 hours, and started reaching volume
> limits with errors.
>
> From what I ha
In case this helps anyone. I ended up having problems with setting
volume limits. For example I suddenly decided to adjust our
incremental backups to run every 4 hours, and started reaching volume
limits with errors.
From what I have read in the documentation setting "Volume Use
Duration
Ok. Thanks Josh. I've already created Pools for each storage location
and done the initial full backups so I will most likely stick with
this method.
So far the backups appear to run a lot better using different pools
for each storage location.
Thanks,
--
Wesley Render, Consultant
Other
On 11/3/2015 6:38 PM, Wesley Render wrote:
> Should each storage daemon/geographic storage location have it's own
> set of Volume Pools? Or can I share one set of Volume Pools between
> all of the storage daemons/storage locations?
You may also use Media Type to tie volumes to particular device
It seems to be working a lot better with different volume pools at
each storage location. I have one server backing up to the server at
our office, and 2 servers backing up to the datacenter. Here is what I
have so far:
Pool {
Name = office-p-monthly
Pool Type = Backup
Volume Retent
I think you have to use one set of pool for every storage.
I think that you can write volumes of the same pool into different storage,
the problem may arrive when you have to restore...
Try to a restore job...
This is my Schedule:
Schedule {
Name = "Custom"
Run = Level=Full Storage
Should each storage daemon/geographic storage location have it's own
set of Volume Pools? Or can I share one set of Volume Pools between
all of the storage daemons/storage locations?
I am using auto labelling as well and it works great.
--
Wesley Render, Consultant
OtherData
---
On 11/03/15 11:23, Carlo Filippetto wrote:
> I don't like to use "label-format" I prefer to set the label by myself.
> In my installation all the jobs that runs during the same night gone to
> the same volumes.
I use auto-labeling for my disk volumes, to achieve exactly that end.
Each volume creat
I don't like to use "label-format" I prefer to set the label by myself.
In my installation all the jobs that runs during the same night gone to the
same volumes.
bye
2015-11-03 17:14 GMT+01:00 Wesley Render :
>
> Thanks Carlo. This is very helpful. I also found this here which I missed
> before:
Is anyone able to clarify question number 1?
I should be all set after that.
Thanks!
--
Wesley Render, Consultant
OtherData
--
___
Bacula-users mailing list
Bacula-users@list
Thanks Carlo. This is very helpful. I also found this here which I
missed before:
http://www.bacula.org/7.0.x-manuals/en/main/Automated_Disk_Backup.html
--
Wesley Render, Consultant
OtherData
--
_
Hi,
for question #2:
Yes you have to create different pool, the firts reason is that usually
incremental bck lives less than a Full backup, the duration is into the
Pool information
So in my case I have
- p-daily INCREMENTAL with 6 volumes (duration 7 days)
- p-weekly DIFFERENTIAL with 4 volumes
13 matches
Mail list logo
