Re: [Bacula-users] Volume Retention / Use Duration
Hello Jeremy all, thanks much for your reply. On Wed, Mar 30, 2011 at 04:27:07PM +0200, Jeremy Maes wrote: Pool Type = Backup Recycle = yes AutoPrune = yes Volume Retention = 14 days Volume Use Duration = 6 days Recycle Oldest Volume = yes Maximum Volumes = 3 Label Format =Full- } Here you specify 3 volumes max, probably to make sure your incrementals are still useful? (something you forgot to do for the incrementals themselves I think) Why the 6 day use duration though? You say you want to do all full backups on the same day. Do the backups take multiple days to complete? But I'm unsure about the use duration. Is there a better way to implement the above requirements? I was hoping that when the 7th day in the cycle comes around with a new full backup being due, bacula would note the max use duration and create a new volume automatically (if max volumes isn't yet reached) or recycle the oldest one, keeping two older full backups on the other volumes. the backups themselves are rather smallish (the biggest is around 160G) and complete within a couple of hours after being started. Is there a more elegant way to keep two older volumes in the pool without making use of max use duration? All the best, Uwe -- NIONEX ist ein Unternehmen der DirectGroup Germany www.directgroupgermany.de -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Volume Retention / Use Duration
Op 31/03/2011 9:08, Uwe Schuerkamp schreef: Hello Jeremy all, thanks much for your reply. On Wed, Mar 30, 2011 at 04:27:07PM +0200, Jeremy Maes wrote: Pool Type = Backup Recycle = yes AutoPrune = yes Volume Retention = 14 days Volume Use Duration = 6 days Recycle Oldest Volume = yes Maximum Volumes = 3 Label Format =Full- } Here you specify 3 volumes max, probably to make sure your incrementals are still useful? (something you forgot to do for the incrementals themselves I think) Why the 6 day use duration though? You say you want to do all full backups on the same day. Do the backups take multiple days to complete? I was hoping that when the 7th day in the cycle comes around with a new full backup being due, bacula would note the max use duration and create a new volume automatically (if max volumes isn't yet reached) or recycle the oldest one, keeping two older full backups on the other volumes. It will indeed make the Volume get marked as Used after those 6 days when the next job starts (or you run a status dir from bconsole), making bacula search for another Volume that it can recycle (or create a new one). Unless your backups run really long you can safely shorten this time to 1 or 2 days, as long as you're sure no job will be running when the use duration (counted from the first write to the volume) expires. the backups themselves are rather smallish (the biggest is around 160G) and complete within a couple of hours after being started. Is there a more elegant way to keep two older volumes in the pool without making use of max use duration? If the amount of jobs writing to a full pool volume is a set number and isn't subject to frequent change, you could alternatively make use of the Maximum Volume Jobs parameter. This will set the volume status to Used after the specified amount of jobs have been written, giving the same result. Take care using this if you're doing all the backups concurrently though, in that case the Volume Use Duration is probably the best way to go. Kind regards, Jeremy DISCLAIMER http://www.schaubroeck.be/maildisclaimer.htm -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Volume Retention / Use Duration
On Thu, Mar 31, 2011 at 09:58:29AM +0200, Jeremy Maes wrote: Take care using this if you're doing all the backups concurrently though, in that case the Volume Use Duration is probably the best way to go. Hello Jeremy, thanks again for your thoughts support. I'll try the max use duration then. All the best, Uwe -- NIONEX ist ein Unternehmen der DirectGroup Germany www.directgroupgermany.de -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Volume Retention / Use Duration
Hi folks,
I'm trying to wrap my head around the following setup:
- For a couple of clients / jobs, we'd like to store two full backups
on disk (weekly full, daily incremental)
- We'd also like to keep 14 incrementals around just in case we need
to do a point in time recovery.
The incremental part seems rather easy, I've defined a separate pool
like so (Bacula 5.0.2 on centos compiled from source):
Pool {
Name = Online_Incremental
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 14 days
Recycle Oldest Volume = yes
Maximum Volumes = 14
Volume Use Duration = 1 day
Label Format =Incr-
}
So we'd end up with a maximum of 14 volumes, using a new volume for
incrementals each day, recycling the old ones as they expire.
Now I was wondering how to go about the Full Pool definition. I'd like
to do full backups on the same day for all clients / jobs, so I've
come up with something like this:
Pool {
Name = Online_Full
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 14 days
Volume Use Duration = 6 days
Recycle Oldest Volume = yes
Maximum Volumes = 3
Label Format =Full-
}
But I'm unsure about the use duration. Is there a better way to
implement the above requirements?
Thanks in advance for your help comments,
Uwe
--
NIONEX ist ein Unternehmen der DirectGroup Germany www.directgroupgermany.de
--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Volume Retention / Use Duration
Op 30/03/2011 14:30, Uwe Schuerkamp schreef:
Hi folks,
I'm trying to wrap my head around the following setup:
- For a couple of clients / jobs, we'd like to store two full backups
on disk (weekly full, daily incremental)
- We'd also like to keep 14 incrementals around just in case we need
to do a point in time recovery.
The incremental part seems rather easy, I've defined a separate pool
like so (Bacula 5.0.2 on centos compiled from source):
Pool {
Name = Online_Incremental
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 14 days
Recycle Oldest Volume = yes
Maximum Volumes = 14
Volume Use Duration = 1 day
Label Format =Incr-
}
So we'd end up with a maximum of 14 volumes, using a new volume for
incrementals each day, recycling the old ones as they expire.
You might run into issues with a 14d volume retention. The retention is
counted from the end of the last job written to the volume, and will
thus be at a point in time áfter the first job's scheduled time.
In the third week you might then not have any expired volumes that are
available for recycling.
You also have to keep in mind that incrementals form a chain. So if you
recycle the monday volume, you'll effectively lose your backup of all
files changed that day, that didn't change again later during the week.
Now I was wondering how to go about the Full Pool definition. I'd like
to do full backups on the same day for all clients / jobs, so I've
come up with something like this:
Pool {
Name = Online_Full
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 14 days
Volume Use Duration = 6 days
Recycle Oldest Volume = yes
Maximum Volumes = 3
Label Format =Full-
}
Here you specify 3 volumes max, probably to make sure your incrementals
are still useful? (something you forgot to do for the incrementals
themselves I think)
Why the 6 day use duration though? You say you want to do all full
backups on the same day. Do the backups take multiple days to complete?
But I'm unsure about the use duration. Is there a better way to
implement the above requirements?
Thanks in advance for your help comments,
Uwe
Kind regards,
Jeremy
DISCLAIMER
http://www.schaubroeck.be/maildisclaimer.htm
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
