Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-4533 applying 2nd patch for tweak to backup section - my fault. 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1178576 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Doug Meil 2011-10-03 20:58:23 +00:00
parent ab1d1d815c
commit 7f5f492925
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/docbkx/ops_mgt.xml
View File

@ -275,7 +275,7 @@ false
Distcp-ing of files in the HBase directory is not generally recommended on a live cluster. Distcp-ing of files in the HBase directory is not generally recommended on a live cluster.
</para> </para>
</section> </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 <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 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. restore, because it's a restore (via distcp) of a specific HDFS directory (i.e., the HBase part) not the entire HDFS file-system.