Tom,
I ran into the same problem about bacula rescheduling a second full backup.
This should only happen the first time, since in following cycles the next
incremental backup should see the previous full backup and run off that, but
it's still no fun to have a single backup that huge. My solution was to
find logical places to split the backup into different filesets and then
have multiple schedules that stagger the load.
Hope it helps,
Kyle Marsh
On 8/27/07, Tom Sommer <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I was hoping someone had some expert advice regarding a possible Bacula
> setup, in a fairly large scale - I would say Enterprise.
>
> I have around 250+ clients with an average of 20GB per client I need to
> backup. Some clients, such as mailservers, have ~110GB data in small files
> and some webservers have ~30GB of various types of files, not a lot of
> changes in these though.
>
> I have to setup an optimal backup solution, with the goal to have a 7 day
> retention period.
>
> I have a 10TB storage device (Raw File Storage) (ignore the inconsistency
> between the number of clients and the size of the storage), and have tried
> several ways to optimize the Schedule to prune volumes effectively, but
> I'm not that confident it's optimal.
>
> Basically I am currently using the following settings:
>
> Pool {
> Name = Default
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 14 days
> Label Format = File-
> Maximum Volume Bytes = 10g
> # Volume Use Duration = 24h
> # Maximum Volume Jobs = 2
> # Use Volume Once = yes
> }
>
> Schedule {
> Name = "WeeklyCycle"
> Run = Full 1st sun at 23:05
> Run = Differential 2nd-5th sun at 23:05
> Run = Incremental mon-sat at 23:05
> }
>
> Client {
> Name = backupserver-fd
> Address = backupserver
> FDPort = 9102
> Catalog = MyCatalog
> Password = [MASKED]
> File Retention = 7 days
> Job Retention = 1 months
> AutoPrune = yes
> }
>
> My primary concern is after 7 days, I will still have more data stored
> than I actually need to recover files 7 days back.
>
> I am also worried about running too many FULL backups, because it takes a
> long time to backup 110+GB in ~3 mill. files, sometimes more than 24
> hours, which leads Bacula to spin a full backup twice (since it tries to
> run an incremental without it being able to see a full backup is in
> progress, bug?).
>
> Lots of text, hope someone will share their advice.
>
> Thanks a lot.
>
> --
> Tom Sommer
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
