[
https://issues.apache.org/jira/browse/GEODE-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032068#comment-16032068
]
ASF subversion and git services commented on GEODE-2994:
--------------------------------------------------------
Commit c1288ac87f1cdee0e34441ab181eeb0506ad4554 in geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c1288ac ]
GEODE-2994 Take backups when region ops are quiescent
This closes #544
> Doc task: interactions of backups with persistence
> --------------------------------------------------
>
> Key: GEODE-2994
> URL: https://issues.apache.org/jira/browse/GEODE-2994
> Project: Geode
> Issue Type: Improvement
> Components: docs
> Reporter: Karen Smoler Miller
> Assignee: Karen Smoler Miller
>
> Document that an inconsistent state can occur by using a backup to restore
> system state, if the backup is made at the wrong time.
> There are 2 examples where persistence and taking a backup might cause an
> inconsistency with region data, if that backup is used to restore a system.
> # *A Lucene index.* The Lucene index is persistent. If a backup is unlucky
> enough to be taken between a persisted write to a region (disk op) and a
> persisted write to the Lucene index (disk op), then the backup represents
> inconsistent data in the region and Lucene index.
> # *An AEQ.* The AEQ is persistent. If a backup is unlucky enough to be taken
> between a persisted write to a region (disk op) and a persisted write to the
> AEQ (disk op), then the backup represents inconsistent data in the region and
> the AEQ.
> The solution is to make sure that backups are taken when the system is
> quiescent WRT region operations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
