Author: Wesley Render <wrender AT otherdata DOT com>
Date: Tue, 03 Nov 2015 15:24:43 +0000
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 ha
Author: Carlo Filippetto <carlo.filippetto AT gmail DOT com>
Date: Tue, 3 Nov 2015 17:00:39 +0100
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 h
Author: Wesley Render <wrender AT otherdata DOT com>
Date: Tue, 03 Nov 2015 16:14:10 +0000
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 -- ____
Author: Wesley Render <wrender AT otherdata DOT com>
Date: Tue, 03 Nov 2015 16:17:52 +0000
Is anyone able to clarify question number 1? I should be all set after that. Thanks! -- Wesley Render, Consultant OtherData -- _______________________________________________ Bacula-users mailing lis
Author: Carlo Filippetto <carlo.filippetto AT gmail DOT com>
Date: Tue, 3 Nov 2015 17:23:09 +0100
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
Author: Phil Stracchino <phils AT caerllewys DOT net>
Date: Tue, 3 Nov 2015 11:39:07 -0500
I use auto-labeling for my disk volumes, to achieve exactly that end. Each volume created has a 24-hour use window, and then it's done, with 14 days expiration for daily incrementals and 60 days for
Author: Wesley Render <wrender AT otherdata DOT com>
Date: Tue, 03 Nov 2015 23:38:01 +0000
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
Author: Carlo Filippetto <carlo.filippetto AT gmail DOT com>
Date: Wed, 4 Nov 2015 10:16:51 +0100
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 rest
Author: Wesley Render <wrender AT otherdata DOT com>
Date: Wed, 04 Nov 2015 14:35:00 +0000
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
You may also use Media Type to tie volumes to particular devices. For example, if disk storage is being used at both locations, then setting the Media Type for the Device at location 1 to "File-1" an
Author: Wesley Render <wrender AT otherdata DOT com>
Date: Wed, 04 Nov 2015 16:48:35 +0000
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 usi
Author: Wesley Render <wrender AT otherdata DOT com>
Date: Thu, 05 Nov 2015 17:02:56 +0000
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 li
Author: Dimitri Maziuk <dmaziuk AT bmrb.wisc DOT edu>
Date: Thu, 5 Nov 2015 11:34:51 -0600
FWIW I've been using Pool { ... Maximum Volumes = X Maximum Volume Bytes = Y Recycle = yes AutoPrune = yes Purge Oldest Volume = yes Recycle Oldest Volume = yes } (where X*Y = 90-ish% of storage disk