We make only a fleeting reference to backup here in the admin docs http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_maintenance You might enter a JIRA.
Having incomplete snapshots is fine - it's a common case that the server has to handle. Patrick On Fri, Aug 5, 2011 at 9:06 AM, Damu R <[email protected]> wrote: > Thanks Ted. > > You might want to investigate using an observer or non-voting ZK instance as >> a backup mechanism. This would not upset your quorum since that machine >> would not participate in leader elections or in getting a quorum for >> commits. It would give you very current backups. >> > > This is my current line of though too. Even in that case there is a > possibility of having a incomplete snapshot if the backup script kicks in > when zookeeper is still writing its snapshot? Is there any way to identify > and avoid this? > > Regards > Damu > > >> On Fri, Aug 5, 2011 at 11:30 AM, Damu R <[email protected]> wrote: >> >> > Hi, >> > I am in the process of setting up regular backup of zookeeper data >> > directory. Is there any documentation available on the recommended >> > tool/method or issues to be aware of? Some of by doubts are: >> > 1. what is the recommended frequency of backup? is there any case where >> > zookeeper may decide to get a complete data dump instead of using the >> > latest >> > snapshot and replaying transactions? >> > 2. from my understanding after reading the zookeeper administration >> guide, >> > zookeeper starts a fuzzy snapshot after a configured number of >> operations. >> > for backing up we need to take the latest snapshot and the transaction >> log >> > file. how do you avoid copying the snapshot when zookeeper is in the >> > process >> > of writing the snapshot file itself? >> > >> > It would be helpful if you can provide me some pointers on the possible >> > solutions. >> > >> > Regards >> > Damu >> > >> >
