From e52dbe761153ca57721758ab364a5881b1d90081 Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Wed, 28 Sep 2011 13:51:36 +0000
Subject: [PATCH] Clarify the explanation of replication purge delay

---
 opendj3/src/main/docbkx/admin-guide/chap-troubleshooting.xml |   14 +++++++++-----
 1 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/opendj3/src/main/docbkx/admin-guide/chap-troubleshooting.xml b/opendj3/src/main/docbkx/admin-guide/chap-troubleshooting.xml
index e59ede0..817f6b4 100644
--- a/opendj3/src/main/docbkx/admin-guide/chap-troubleshooting.xml
+++ b/opendj3/src/main/docbkx/admin-guide/chap-troubleshooting.xml
@@ -204,11 +204,15 @@
  misconfigured client application connecting to this replication server.
  The error was: Remote host closed connection during handshake</screen>
  
-  <para>Replicas can become irrevocably out of sync if for example you restore
-  a replica from backup with a backup archive older than the last time
-  historical information for replication was purged from the system. If this
-  happens to you, disable the replica, and then reinitialize it with newer
-  data.</para>
+  <para>OpenDJ maintains historical information about changes in order to
+  bring replicas up to date, and to resolve replication conflicts. To prevent
+  historical information from growing without limit, OpenDJ purges historical
+  information after a configurable delay
+  (<literal>replication-purge-delay</literal>, default: 3 days). A replica
+  can become irrevocably out of sync if you restore it from a backup archive
+  older than the purge delay, or if you stop it for longer than the purge
+  delay. If this happens to you, disable the replica, and then reinitialize it
+  from a recent backup or from a server that is up to date.</para>
  </section>
  
  <section>

--
Gitblit v1.10.0