You need to update all the volumes in the pool with the new settings

Have a look at bconsole update command 1 -> 13




On samedi, 19 mars 2016 11.44:19 h CET John Naggets wrote:
> Hi Bruno,
> 
> Thanks for explaining and helping with so much details. I must say I am still 
> a bit confused but at least I managed to get one volume to be used per job. 
> So each job has now its own volume written on the file system. My Incremental 
> pool looks like that now:
> 
> Pool {
>   Name = Incremental
>   Pool Type = Backup
>   Recycle = yes                       # Bareos can automatically recycle 
> Volumes
>   AutoPrune = yes                     # Prune expired volumes
>   Volume Retention = 30 days          # How long should the Incremental 
> Backups 
>   Label Format = "Incremental-"       # Volumes will be labeled "Incremental-
>   Maximum Volume Jobs = 1               # we put only one job per media 
> }
> 
> Now I noticed that my previous volumes before this change are not 
> automatically adapted to these new settings. What do I need to do in that 
> case?
> 
> Regards
> John
> 
> On Tuesday, March 15, 2016 at 9:38:24 PM UTC+1, Bruno Friedmann wrote:
> > On mardi, 15 mars 2016 13.00:19 h CET John Naggets wrote:
> > > Hi Bruno,
> > > 
> > > Thanks for your example but somehow I am not sure about the "Maximum 
> > > Volumes = 1" parameter. If I understand correctly this parameter it means 
> > > I would have only one single volume or file respectively in my pool? 
> > > 
> > > Because I am using the default config of bareos with 3 pools: Full, 
> > > Incremental and Differential and having only one single file does not 
> > > make sense.
> > > 
> > > Regards
> > > John
> > > 
> > 
> > For sure my example was addressing only one case, having one volune for one 
> > job in one pool, with one device storage.
> > (typical setup for customer who want a job for each week)
> > Which give me 5 files 
> > 
> > One of the hard thing to understand (at least at the beginning) is that 
> > there's not a one fixed way to do and organize your
> > backup with Bareos, you can be really creative :-)
> > 
> > So just an example in your case (but as I didn't have all the elements, 
> > don't forget to taint that with a grain of salt)
> > I will take the simple setup with one dir, one sd, one client
> > 
> > You want for Example a Full pool for 12 months so you setup the pool to 
> > handle 12 volumes
> > with a retention time of a bit less than one year.
> > The full job will goes there, and one full pro month for one job 
> > Then on you device storage you will have 12 media
> > 
> > Differential will handle 4-5 weeks at you discretion I prefer 5 
> > So the pool has retention period of 28 days, and 5 volumes 
> > Device like for month
> > 
> > Incremental will run for 7 days so you create a pool with retention time 
> > for 6.5 days
> > and limit to 7 volumes.
> > 
> > All of them will normally have one storage device.
> > 
> > This is one way of doing things. 
> > 
> > You can imagine differents things, like having a pool days (where on sunday 
> > you have a full job
> > and then 6 incremental) this job use one pool one storage one type of media
> > Then you add another pool which contain diff (weeks) and another one for 
> > full (months)
> > using another time retention (weeks 28 days), month (11.5 months) but share 
> > another storage
> > device and media type   
> > 
> > :-) And now I'm pretty sure I've lost you ....
> > 
> > There's one golden rules, on which you should make all your configuration : 
> > What I want to restore, for how long, and how complicated/speed.
> > 
> > This is your "sla", each time you modify your configuration, take your time
> > to check if you comply to what you decide is good for your restores.
> > 
> > 
> > > On Tuesday, March 15, 2016 at 7:18:45 AM UTC+1, Bruno Friedmann wrote:
> > > > On samedi, 12 mars 2016 12.35:22 h CET John Naggets wrote:
> > > > > Hello,
> > > > > 
> > > > > In the default director config of bareos the three pools full, 
> > > > > differential and incremental all use one volume to store many jobs as 
> > > > > long as the max volume bytes has not been reached.
> > > > > 
> > > > > So I was wondering is this because of effeciency? Because I was 
> > > > > thinking, that it might be better to have one volume per job instead? 
> > > > > 
> > > > > By the way I am using file based storage and no tapes, so that would 
> > > > > mean I would have one file per job.
> > > > > 
> > > > > Regards
> > > > > John
> > > > > 
> > > > > 
> > > > Hi John, in case you didn't find it.
> > > > 
> > > > In pool definition you can use 
> > > > 
> > > > For example to have only one media with one job in a pool WEEKNN (01-05)
> > > > you can setup 
> > > > 
> > > >   Maximum Volumes = 1                   # We use one media in weekNN 
> > > > pool
> > > >   Maximum Volume Jobs = 1               # we put only one job per media
> > > > 
> > > > It is a valid different way of doing things.
> > > > 
> > > 
> > > 
> > 
> > 
> 
> 


-- 

Bruno Friedmann 
Ioda-Net Sàrl www.ioda-net.ch
 
 openSUSE Member, fsfe fellowship
 GPG KEY : D5C9B751C4653227
 irc: tigerfoot

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to