Journal File Question

[Mark Andrews]

In message <Prayer.1.3.5.1207260007050.11220 at hermes-2.csi.cam.ac.uk>, Chris Thompson writes:
> On Jul 25 2012, WBrown at e1b.org wrote:
> 
> >Chris Buxton <chris.p.buxton at gmail.com> wrote on 07/25/2012 12:07:22 PM:
> >
> >> > It doesn't sync the files to make two equal copies. It applies all of 
> >the 
> >> > outstanding transactions in the journal file to the zone file and then 
> >
> >> > empties the journal.
> >> 
> >> I don't believe that is entirely correct. The journal file needs to 
> >> be retained to support ixfrs. My understanding is that it will be 
> >> automatically trimmed to max-journal-size, if that option is set.
> >
> >Do you know how it determines what is kept?
> 
> When the journal file reaches the max-journal-size value, roughly the
> first half of it is discarded. But there are other actions that can
> discard the whole journal file, such as "rndc freeze" on a type master
> zone, "rndc retransfer" on a type slave one, etc.
> 
> To find out if a journal file goes back far enough for your purposes,
> use the named-journalprint utility distributed with BIND. Although I
> have to say I would hate to be dependent on this way of recovering a
> lost zone file: you should probably be rethinking your whole backup
> and recovery strategy.

The slaves should have a recent copy of the zone.  Just axfr it and
use it as the master file. Any untransferred changes will be applied
from the journal when named starts.

> -- 
> Chris Thompson
> Email: cet1 at cam.ac.uk
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org