Re: [Bacula-users] Lets open up a discussion about estimating required space for backups.

[Dmitri Maziuk]

On 8/14/2014 7:34 PM, Jeff MacDonald wrote:
...
> Is there a good way to plan ahead?

If your backup is growing (they always are), you will eventually hit the 
limits. There are a couple of workarounds: 1. use hot-swappable drives 
and vchanger. That means manual swapping of drives & re-labeling the 
volumes when your storage fills up. Some volumes will be offline. 2. Use 
resizable storage like zfs and hope drive capacity grows faster than 
your backup. Then you can keep replacing your drives w/ bigger ones & 
keep up while keeping everything online. No vchanger means bacula's 
autolabeling will work, too. 3. Back up to "cloud files". This one's 
ugly for many reasons but in theory "the cloud" will accommodate any 
number of file volumes, they'll all be online, autolabeled, etc.

Dima



--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Fwd: How to backup on volume that has not reached its retention period.

[John Drescher]

-- Forwarded message --
From: John Drescher 
Date: Fri, Aug 15, 2014 at 9:40 AM
Subject: Re: [Bacula-users] How to backup on volume that has not
reached its retention period.
To: Heitor Faria 


> Btw: if you reduce the Volume Retention on a pool, i'm pretty sure you gotta
> update your álready created volumes with the update command.

Correct. The settings in the conf file do not automatically apply to
already existing volumes so you must do this manually.

update pool from resource
update all volumes in pool

John


-- 
John M. Drescher

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] pruning oldest volume when its impossible

[Heitor Faria]

> Oh.. I should make an effort to be clear. I am _not_ using that feature.
>>>
>> Sorry Jeff. My mistake.
So, like I said before, you just need to create more volumes for backup or
reduce your Volume Retention. Don't forget to update the already created
volumes if you reduce the retention.


-- 

Heitor Medrado de Faria | Need Bacula training? 10% discount coupon code at
Udemy: bacula-users

+55 61 2021-8260
+55 61 8268-4220
Site: www.bacula.com.br
Facebook: heitor.faria 
Gtalk: heitorfa...@gmail.com

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to backup on volume that has not reached its retention period.

[Heitor Faria]

On Fri, Aug 15, 2014 at 9:05 AM, Heitor Faria  wrote:

>
> Initially I set the Volume Retention to 14 days, but I reduced it to 12
>> days, just to be safe that the tape will definitely get recycled. Thing is,
>> sometimes there are issues that cause the backup not running on time.
>> Backup jobs got pending, and they ran at a later date. Sometimes the jobs
>> got pending for a bit too long and this causes the number of days between
>> the last written date and the incoming backup date to be less than 12 days.
>> When this happens, the incoming backup job will not be able to run because
>> the volume status is 'Used', and it is waiting for me to create a new label.
>>
>
> Just redeuce the volume retention in one day? E. g.: 11 days?
>

Btw: if you reduce the Volume Retention on a pool, i'm pretty sure you
gotta update your álready created volumes with the update command.


-- 

Heitor Medrado de Faria | Need Bacula training? 10% discount coupon code at
Udemy: bacula-users

+55 61 2021-8260
+55 61 8268-4220
Site: www.bacula.com.br
Facebook: heitor.faria 
Gtalk: heitorfa...@gmail.com

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to backup on volume that has not reached its retention period.

[Heitor Faria]

> Initially I set the Volume Retention to 14 days, but I reduced it to 12
> days, just to be safe that the tape will definitely get recycled. Thing is,
> sometimes there are issues that cause the backup not running on time.
> Backup jobs got pending, and they ran at a later date. Sometimes the jobs
> got pending for a bit too long and this causes the number of days between
> the last written date and the incoming backup date to be less than 12 days.
> When this happens, the incoming backup job will not be able to run because
> the volume status is 'Used', and it is waiting for me to create a new label.
>

Just redeuce the volume retention in one day? E. g.: 11 days?

> I have set Volume Use Duration to 2 days, hoping that after 2 days, it
> will be marked as Used, and if in any way that the backup needs to be
> performed in less than 12 days, it will be automatically purged.
>
If the first backup runs on time, Recycle and AutoPrune = yes, this is the
expected behavior.
Observe that Bacula doesn't update its Catalog each second. The volume may
appear used after the retention period is over, but if you submit a job
that needs writing space if may recycle the volumes.

> Unfortunately, this is not happening. The volume status is used, and I
> will have to create a new label in order to get the backup job to run (I
> prefer just to manually purge it). So what should I do to tell bacula to
> run the backup job, even when it hasn't exceed the retention period?
>
If you want to just ignore the retention you can use the Purge Oldest
Volume = yes option on pool. I don't like it, since It may lead you to a
volume usages loop.

> Thanks.
>
>
> --
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>


-- 

Heitor Medrado de Faria | Need Bacula training? 10% discount coupon code at
Udemy: bacula-users

+55 61 2021-8260
+55 61 8268-4220
Site: www.bacula.com.br
Facebook: heitor.faria 
Gtalk: heitorfa...@gmail.com

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Lets open up a discussion about estimating required space for backups.

[Heitor Faria]

>
> You have a file based storage array available with a capacity of say 6 TB,
> and you have to back up 20 clients.
>
> Lets say I’m going with the default Full/Diff/Inc weekly schedule and that
> I’ve had an arbitrary retention time of 1 year on fulls 6 months on diffs
> and 1 month on incrementals.
>
> What strategies would you employ to manage disk space, estimate growth etc.


Is there a missing variable here, witch is the size of your full backups?
As for strategy I like to use GFS Rotation like explained on this diagram:
http://www.bacula.com.br/?p=2271

Chhers,
-- 

Heitor Medrado de Faria | Need Bacula training? 10% discount coupon code at
Udemy: bacula-users

+55 61 2021-8260
+55 61 8268-4220
Site: www.bacula.com.br
Facebook: heitor.faria 
Gtalk: heitorfa...@gmail.com

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] pruning oldest volume when its impossible

[Jeff MacDonald]

On Aug 14, 2014, at 10:34 PM, Heitor Faria  wrote:

>> 
>> I have a backup job that uses a Pool of 100 5 gig files. Job and File 
>> retention are set to 10 years. Vol retention set to 70 days.
>> 
>> 100 files have been filled and the oldest file is 23 days old. 
>> 
>> Right now bacula is attempting to prune the oldest volume. As I understand 
>> things.. this will not result in any thing actually being pruned from that 
>> volume and essentially my db is just going to spin and move onto the next 
>> volume until I add new ones for it to use. Am I correct?
>> 
>> I think it's correct, unless have configured the "Purge Oldest Volume = yes”.
> 
> Purge Oldest Volume = yes… just sounds evil :) Like it can override any and 
> all retention periods. I don’t want that :)
> 
> Purge Oldest Volume ignores any retention configuration and may lead you to a 
> loop, yes, if your backup size increases too much. I don't like it.
>  
>> With Autoprune = off i think the behavior would be the same at this point.
> 
> Would it? If that was off… I would think that the director would just wait 
> until either i labeled a new volume, or told it to prune one?
> 
> I think so. I wasn't aware that you were using Purge Oldest Volume option. 
> Its a game changer.

Oh.. I should make an effort to be clear. I am _not_ using that feature.


>  
>> -- 
>> 
>> Heitor Medrado de Faria | Need Bacula training? 10% discount coupon code at 
>> Udemy: bacula-users
>> +55 61 2021-8260
>> +55 61 8268-4220
>> Site: www.bacula.com.br
>> Facebook: heitor.faria
>> Gtalk: heitorfa...@gmail.com
>> 
> 
> 
> 
> 
> -- 
> 
> Heitor Medrado de Faria | Need Bacula training? 10% discount coupon code at 
> Udemy: bacula-users
> +55 61 2021-8260
> +55 61 8268-4220
> Site: www.bacula.com.br
> Facebook: heitor.faria
> Gtalk: heitorfa...@gmail.com
> 

--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] How to backup on volume that has not reached its retention period.

[Gi Dot]

Hi,

I configured bacula to perform backup on a tape for every 2 days (1 tape
for Monday & Tuesday, another tape for Wednesday & Thursday, and so on).
These tapes will be recycled every 2 weeks.

Example:
Week 1, Monday & Tuesday = Tape A
Week 2, Monday & Tuesday = Tape B
Week 3, Monday & Tuesday = Tape A
.
.

I configured my pool with the following parameters:

  Name = Cat1_SunMonW1
  Pool Type = Backup
  Recycle = yes   # Bacula can automatically recycle
Volumes
  AutoPrune = yes # Prune expired volumes
  Volume Retention = 12 days  # tape recycle every 2 weeks
  Volume Use Duration = 2 days  # tape backups for 2 days
  Recycle Current Volume = yes

Initially I set the Volume Retention to 14 days, but I reduced it to 12
days, just to be safe that the tape will definitely get recycled. Thing is,
sometimes there are issues that cause the backup not running on time.
Backup jobs got pending, and they ran at a later date. Sometimes the jobs
got pending for a bit too long and this causes the number of days between
the last written date and the incoming backup date to be less than 12 days.
When this happens, the incoming backup job will not be able to run because
the volume status is 'Used', and it is waiting for me to create a new label.

I have read in bacula documentation where it states:
If you want Bacula to stop using a Volume and recycle it before it is full,
you will need to use one or more additional directives such as:

   - Use Volume Once = yes
   - Volume Use Duration = ttt
   - Maximum Volume Jobs = nnn
   - Maximum Volume Bytes = mmm

I have set Volume Use Duration to 2 days, hoping that after 2 days, it will
be marked as Used, and if in any way that the backup needs to be performed
in less than 12 days, it will be automatically purged.

Unfortunately, this is not happening. The volume status is used, and I will
have to create a new label in order to get the backup job to run (I prefer
just to manually purge it). So what should I do to tell bacula to run the
backup job, even when it hasn't exceed the retention period?

Thanks.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Pending jobs sequence skipped.

[Gi Dot]

That, is a good idea. Thanks!


On Fri, Aug 8, 2014 at 10:17 PM, J. Echter <
j.ech...@echter-kuechen-elektro.de> wrote:

>  Am 07.08.2014 09:22, schrieb Gi Dot:
>
>   Hi,
>
>  Due to holiday and having no one around to switch tapes for me, I have
> more than 10 jobs created and pending for backup. Normally when situation
> like this occur (though with lesser number of jobs), I will just put in the
> tapes one by one and let the jobs run in sequence one after another.
>
>  This time I found that 2 jobs (Saturday and Sunday) were marked as 'fatal
> error'. Monday job should be next in sequence, but job Friday is listed
> instead of Monday. I canceled the Friday job, but then a newer job that is
> way down in the job list got to run first. How does this happen?
>
>  Check out the jobid - 138, 139, 149, 151. jobid 140 got skipped.
>
> |   137 | W2W4 | 2014-07-25 13:00:03 | B| F |   38,805 |
> 6,073,467,421 | T |
> |   138 | SatSunW2 | 2014-07-26 13:00:03 | B| I |0
> | 0 | f |
> |   139 | SatSunW2 | 2014-07-31 20:00:20 | B| F |0
> | 0 | f |
> |   149 | FriW1| 2014-08-06 03:00:33 | B| F |0
> | 0 | A |
> |   151 | SatSunW2 | 2014-08-07 10:54:28 | B| F |0
> | 0 | R |
> |   140 | MonTueW1 | | B| I |0
> | 0 | C |
> |   141 | MonTueW1 | | B| I |0
> | 0 | C |
> |   142 | WedThuW1 | | B| I |0
> | 0 | C |
> |   143 | WedThuW1 | | B| I |0
> | 0 | C |
> |   144 | FriW1 | | B| F |0
> | 0 | C |
> |   145 | SatSunW1 | | B| I |0
> | 0 | C |
> |   146 | SatSunW1 | | B| I |0
> | 0 | C |
> |   147 | MonTueW2 | | B| I |0
> | 0 | C |
> |   148 | MonTueW2 | | B| I |0
> | 0 | C |
> |   150 | WedThuW2 | | B| I |0
> | 0 | C |
> |   152 | MonTueW1 | | B| I |0
> | 0 | C |
> |   153 | MonTueW1 | | B| I |0
> | 0 | C |
>
> +---+--+-+--+---+--+---+---+
>
> --
>
>
> --
>
>
>  Hi,
>
> we use a run before script which checks if its a holiday or not on our
> tape jobs.
>
> If it is holiday it cancels the job. Only harddrive jobs run at this time.
>
> Sorry if i couldn't clarify your question.
>
> Cheers.
>
> Juergen
>
>
> --
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users