From f4c34dc678895dd86dfb80955984bd81501009eb Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Thu, 10 May 2012 10:29:47 +0000
Subject: [PATCH] Mention a few things from Danny and Matt's discussion on OPENDJ-490

---
 opendj3/src/main/docbkx/admin-guide/chap-import-export.xml |   30 +++++++++++++++++++++++++++++-
 1 files changed, 29 insertions(+), 1 deletions(-)

diff --git a/opendj3/src/main/docbkx/admin-guide/chap-import-export.xml b/opendj3/src/main/docbkx/admin-guide/chap-import-export.xml
index 84412d3..ce349df 100644
--- a/opendj3/src/main/docbkx/admin-guide/chap-import-export.xml
+++ b/opendj3/src/main/docbkx/admin-guide/chap-import-export.xml
@@ -20,7 +20,7 @@
   !
   ! CCPL HEADER END
   !
-  !      Copyright 2011 ForgeRock AS
+  !      Copyright 2011-2012 ForgeRock AS
   !    
 -->
 <chapter xml:id='chap-import-export'
@@ -376,4 +376,32 @@
   (Directory Data &gt; New Base DN... &gt; Backend &gt; New Backend:
   <replaceable>backend-name</replaceable>).</para>
  </section>
+
+ <section xml:id="delete-database-backend">
+  <title>Deleting a Database Backend</title>
+  <indexterm>
+   <primary>Database backend</primary>
+   <secondary>Deleting</secondary>
+  </indexterm>
+
+  <para>You delete a database backend by using the <command>dsconfig
+  delete-backend</command> command.</para>
+
+  <para>When you delete a database backend by using the <command>dsconfig
+  delete-backend</command> command, OpenDJ does not actually remove the
+  database files for two reasons. First, a mistake could potentially cause
+  lots of data to be lost. Second, deleting a large database backend could
+  cause severe service degradation due to a sudden increase in I/O load.</para>
+
+  <para>Instead, after you run the <command>dsconfig delete-backend</command>
+  command you must also manually remove the database backend files.</para>
+
+  <para>If you do run the <command>dsconfig delete-backend</command> command by
+  mistake and have not yet deleted the actual files, then you can recover from
+  the mistake by creating the backend again, reconfiguring the indexes that
+  were removed, and rebuilding the indexes as described in the section on <link
+  xlink:href="admin-guide#configure-indexes"
+  xlink:role="http://docbook.org/xlink/role/olink"><citetitle>Configuring &amp;
+  Rebuilding Indexes</citetitle></link>.</para>
+ </section>
 </chapter>

--
Gitblit v1.10.0