From ab1d1d815cb17931a0400d82e23011beba38a57f Mon Sep 17 00:00:00 2001 From: Doug Meil Date: Mon, 3 Oct 2011 20:53:21 +0000 Subject: [PATCH] HBASE-4533 tweaks to backup section git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1178572 13f79535-47bb-0310-9956-ffa450edef68 --- src/docbkx/ops_mgt.xml | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/src/docbkx/ops_mgt.xml b/src/docbkx/ops_mgt.xml index fe29eff524a..97e8ecc791c 100644 --- a/src/docbkx/ops_mgt.xml +++ b/src/docbkx/ops_mgt.xml @@ -267,15 +267,18 @@ false -
Backup NameNode - - -
Distcp - Distcp could be used to either copy the contents of the hbase directory in HDFS to either the same cluster, or do a different cluster. + Distcp could be used to either copy the contents of the HBase directory in HDFS to either the same cluster in another directory, or + to a different cluster. Note: Distcp works in this situation because the cluster is down and there are no in-flight edits to files. - This is not recommended on a live cluster. + Distcp-ing of files in the HBase directory is not generally recommended on a live cluster. + +
+
Restore (if needed) + 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.