From 2d114130841e9480e0b7de458ed477f02efd42fd Mon Sep 17 00:00:00 2001
From: dyozie
Date: Tue, 7 Nov 2017 15:18:22 -0800
Subject: [PATCH] Docs - add info about filtering leaf partitions with gpbackup
---
.../admin_guide/managing/backup-gpbackup.xml | 59 ++++++++++++++++++-
.../admin_utilities/gpbackup.xml | 24 +++++---
2 files changed, 74 insertions(+), 9 deletions(-)
diff --git a/gpdb-doc/dita/admin_guide/managing/backup-gpbackup.xml b/gpdb-doc/dita/admin_guide/managing/backup-gpbackup.xml
index 144e71980a..4539f02237 100644
--- a/gpdb-doc/dita/admin_guide/managing/backup-gpbackup.xml
+++ b/gpdb-doc/dita/admin_guide/managing/backup-gpbackup.xml
@@ -20,9 +20,10 @@
format="dita"/> for more information.) Storing the table data in CSV files also provides
opportunities for using other restore utilities, such as gpload, to load the
data either in the same cluster or another cluster. By default, one file is created for each
- table on the segment. You can specify the -leaf-partition-data option with
+ table on the segment. You can specify the -leaf-partition-data option with
gpbackup to create one data file per leaf partition of a partitioned table,
- instead of a single file.
+ instead of a single file. This option also enables you to filter backup sets by leaf
+ partitions.
Each gpbackup task uses a single transaction in Greenplum Database. During
this transaction, metadata is backed up on the master host, and data for each table on each
segment host is written to CSV backup files using COPY .. ON SEGMENT commands
@@ -41,6 +42,10 @@
requires a distinct timestamp.
Database object filtering is currently limited to schemas and tables.
Filtering objects with gprestore is not yet supported.
+ You cannot use the -exclude-table-file with
+ -leaf-partition-data. Although you can specify leaf partition names
+ in a file specified with -exclude-table-file, gpbackup
+ ignores the partition names.
Incremental backups are not supported.