Hello,
Yann Cézard wrote:
Hi list,
First of all : Bacula is a great piece of Open Source software, thanks a
lot for it !
Now, I have a little question, someone could perhaps help me :
I am configuring a new Bacula Backup Server (Linux FC3, bacula 1.36.3,
MySQL backend)
with the following design :
- Every Week a Full Backup is done (Pool of 2 volumes, storage on Files)
- Every Day an Incremental One is done (Pool of 12 volumes, storage on
Files).
- Retention Volume Period is 13 days
Each Job has its own Pools of Full and Incremental Volumes.
This allow us to save two weeks of data. In fact we only needs one and
conserve one
week more in case of problems with the last one.
Good idea.
Now my "problem" is :
The Full Backups are run on Monday, Thursday, Wednesday... depending on
the Job
(there are a lot of data, as we experienced some very long times saving
a great volume
of data, we decided to divide the biggest on 7 days), but when I will
launch bacula for
the first time, all first backups will be Full. There will be no problem
with the next
Full Backup, but the next one would probably because volumes would be
less than
13 days old...
Well, basically, you're right.
Exple :
nah, I don't need no examples ;-)
At this point, am I right or am I wrong ?
Erm. Yes.
So how could I do to have only 2 Full Backups in my Pool and a retention
period of 13 days ?
Should I configure first the retention period to 7 days the first time
Bacula is launched,
and then change it to 13 days ? Will this be OK ?
Or should I considere using 3 volumes in the Full Pool for beginning and
reduce this to
2 in the future ?
You can use all your possible solutions, and even more.
The reasons are obvious, and all solutions should work. But, I'd suggest
two other ways:
1. You can try to add (or uncomment their schedules) the jobs so they
are started the first time at the day for full backups. This gives you
some additional time to get used to bacula and grow your setup, possibly
giving you enough time to solve problems and seeing if you've got any
bottlenecks.
2. You can simply manually purge the excess volume from the first full
backup when bacula asks for more volumes. This needs only be dne once
(per job, of course) and doesn't require configuration changes, so it
should be not too much additional work and no big risk of data loss.
During my first steps with bacula, I used the first solution I
suggested, now I'd use number two :-)
I'm not sure I am very clear on describing my problem, I hope I am... :)
If you like my answer I don't care if I understood your question ;-)
Arno
Cheers,
Yann
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
