You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by dm...@apache.org on 2011/10/03 22:58:23 UTC
svn commit: r1178576 - /hbase/trunk/src/docbkx/ops_mgt.xml
Author: dmeil
Date: Mon Oct 3 20:58:23 2011
New Revision: 1178576
URL: http://svn.apache.org/viewvc?rev=1178576&view=rev
Log:
HBASE-4533 applying 2nd patch for tweak to backup section - my fault.
Modified:
hbase/trunk/src/docbkx/ops_mgt.xml
Modified: hbase/trunk/src/docbkx/ops_mgt.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/ops_mgt.xml?rev=1178576&r1=1178575&r2=1178576&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/ops_mgt.xml (original)
+++ hbase/trunk/src/docbkx/ops_mgt.xml Mon Oct 3 20:58:23 2011
@@ -275,7 +275,7 @@ false
Distcp-ing of files in the HBase directory is not generally recommended on a live cluster.
</para>
</section>
- <section xml:id="ops.backup.fullshutdown.distcp"><title>Restore (if needed)</title>
+ <section xml:id="ops.backup.fullshutdown.restore"><title>Restore (if needed)</title>
<para>The backup of the hbase directory from HDFS is copied onto the 'real' hbase directory via distcp. The act of copying these files
creates new HDFS metadata, which is why a restore of the NameNode edits from the time of the HBase backup isn't required for this kind of
restore, because it's a restore (via distcp) of a specific HDFS directory (i.e., the HBase part) not the entire HDFS file-system.