This is an automated email from the ASF dual-hosted git repository.
granthenke pushed a commit to branch branch-1.11.x
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/branch-1.11.x by this push:
new 3d09bc3 KUDU-2982: Document taking backups on earlier versions of Kudu
3d09bc3 is described below
commit 3d09bc394ec99d1ef948f138c031727f91a9f075
Author: Grant Henke <[email protected]>
AuthorDate: Mon Oct 21 17:17:55 2019 -0500
KUDU-2982: Document taking backups on earlier versions of Kudu
Adds a section to the backup documentation describing how to
succesfully take backups on Kudu clusters earlier than Kudu 1.10.
Change-Id: I15201bafc5c0e40b230873f92790d4fc2a02bdde
Reviewed-on: http://gerrit.cloudera.org:8080/14525
Reviewed-by: Adar Dembo <[email protected]>
Tested-by: Kudu Jenkins
(cherry picked from commit f54ac28bc4f21da19daae6108f4323c5577d534c)
Reviewed-on: http://gerrit.cloudera.org:8080/14530
Reviewed-by: Alexey Serbin <[email protected]>
---
docs/administration.adoc | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/docs/administration.adoc b/docs/administration.adoc
index ef80117..2b3e237 100644
--- a/docs/administration.adoc
+++ b/docs/administration.adoc
@@ -436,6 +436,22 @@ rule of thumb is 1 GiB per 50 columns.
If your Spark resources drastically outscale the Kudu cluster you may want to
limit the
number of concurrent tasks allowed to run on restore.
+===== Backups on Kudu 1.9 and earlier
+
+If your Kudu cluster is version 1.9 or earlier you can still use the backup
tool
+introduced in Kudu 1.10 to backup your tables. However, because the incremental
+backup feature requires server side changes, you are limited to full backups
only.
+The process to backup tables is the same as documented above, but you will
need to
+download and use the kudu-backup jar from a Kudu 1.10+ release. Before running
+the backup job you should adjust the configuration of your servers by setting
+`--tablet_history_max_age_sec=604800`. This is the new default value in Kudu
1.10+
+to ensure long running backup jobs can complete successfully and consistently.
+Additionally, when running the backup you need to pass `--forceFull` to disable
+the incremental backup feature. Now each time the job is run a full backup
will be taken.
+
+NOTE: Taking full backups on a regular basis is far more resource and time
intensive
+than incremental backups. It is recommended to upgrade to Kudu 1.10+ soon as
possible.
+
[[physical_backup]]
=== Physical backups of an entire node
