On Wed, Sep 24, 2014 at 12:27:30PM -0300, Sergio Belkin wrote: > Hi Folks, > > I've read this thread, and I'd want to get some clarification about this > topic. > > if Julien have set the Volume Retention of incremental in 35 days, I don't > understand why "(around 15 june Incr-0001 should be recycled)".
5th June would be more correct .. if "Incr-0001" is written on 1 May, then 1 May + 35 days = ~5 June To clarify a little bit: I'm doing a full backup per month and a daily incremental backup (with Use Volume Once) > 2) is it correct that on 1 july Full-0001 it's recycled? if Volume > Retention of Backuo Job was set as of 45 days. On 1 June, Full-0001 it's > changes it's status, it will be recycled on 15 july aprox. Pleae correct me > if I'm wrong. sounds correct to me..! > > Thanks in advance! > Don't forget that volume retention takes precedence over any job retention and that it's it read from the catalog, so don't forget to bconsole -> update if you change them ..! > 2009-04-03 4:37 GMT-03:00 Julien Cigar <jci...@ulb.ac.be>: > > > On Thu, 2009-04-02 at 20:52 -0400, mo...@frakir.org wrote: > > > On Thu, Apr 02, 2009 at 09:25:55PM +0200, Julien Cigar wrote: > > > > > > > > 1 may 0:00 am : Full backup -> volume "Full-0001" > > > > > 1 may 8:00 pm : Incremental backup -> volume "Incr-0001" > > > > > 2 may 8:00 pm : Incremental backup -> volume "Incr-0002" > > > > > 3 may 8:00 pm : Incremental backup -> volume "Incr-0003" > > > > > ... > > > > > 31 may 8:00 pm : Incremental backup -> volume "Incr-0031" > > > > > > > > > > 1 june 0:00 am : Full backup -> volume "Full-0002" > > > > > 1 june 8:00 pm : Incremental backup -> volume "Incr-0032" > > > > > 2 june 8:00 pm : Incremental backup -> volume "Incr-0033" > > > > > 3 june 8:00 pm : Incremental backup -> volume "Incr-0034" > > > > > ... > > > > > (around 15 june Incr-0001 should be recycled) > > > > > > > > > > 1 july 0:00 am : Full backup -> volume "Full-0001" (recycled) > > > > > > An incremental can be promoted to a full in the middle of a cycle. > > > This can happen because of a fileset change or a rerun of a failed > > > level. If such an event happens on June 15, the volume Full-0001 will > > > be overwritten. At this point, you can't do a restore of the FS from > > > May 31, even though it's only been 15 days. > > > > > > > right. > > > > thanks ! > > > > > - Morty > > -- > > Julien Cigar > > Belgian Biodiversity Platform > > http://www.biodiversity.be > > Université Libre de Bruxelles (ULB) > > Campus de la Plaine CP 257 > > Bâtiment NO, Bureau 4 N4 115C (Niveau 4) > > Boulevard du Triomphe, entrée ULB 2 > > B-1050 Bruxelles > > Mail: jci...@ulb.ac.be > > @biobel: http://biobel.biodiversity.be/person/show/471 > > Tel : 02 650 57 52 > > > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Bacula-users mailing list > > Bacula-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > > -- > -- > Sergio Belkin http://www.sergiobelkin.com > LPIC-2 Certified - http://www.lpi.org > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.
pgpSb4mrOVdi9.pgp
Description: PGP signature
------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
