Release Notes

Release Notes

Release Date: November 10, 2021

Tanzu Greenplum Backup and Restore utilities are released separately from Tanzu Greenplum Database (from Backup and Restore v1.13.0), and are updated independently of the core server.

Version 1.22.0

Tanzu Greenplum Backup and Restore version 1.22.0 is a minor release.

Platform Support

Tanzu Greenplum Backup and Restore is compatible with these Greenplum Database versions:

  • Tanzu Greenplum Database 4.3.22 and later
  • Tanzu Greenplum Database 5.5.0 and later
  • Tanzu Greenplum Database 6.0.0 and later

Software Component Versions

This release includes the following utilities:

See Data Domain Boost for Data Domain Boost support information.

See Known Issues for a list of issues known to exist in this release.

See Differences Compared to Open Source Greenplum Backup and Restore for the list of features that are only in Tanzu Greenplum Backup and Restore.

See Release Numbering Conventions for a description of the Tanzu Greenplum Backup and Restore release numbering scheme.

gpbackup v1.22.0

New Feature

  • [394] The gpbackup utility now supports zstd compression.
  • The gpbackup utility takes a new option – --compression-type – which specifies which compression type to use: gzip or zstd. The default is gzip.

Resolved Issues

  • [31846] In some situations, gpbackup was failing with “out of shared memory” errors due to the maximum number of locks being exceeded. This has been resolved by skipping internal metadata queries that aren’t necessary when the --leaf-partition-data option is not supplied.
  • [180198118] Resolved an issue where gpbackup was not terminating sessions correctly during copy operations.

gpbackup_helper v1.22.0

No changes since Tanzu Greenplum Backup and Restore version 1.14.0.

gprestore v1.22.0

Resolved Issues

  • [179545868] Resolved an issue introduced in gprestore 1.21.0, where COPY operations were hanging in a race condition; the issue was triggered when the DD Boost Storage Plugin was used in conjunction with a restore operation of data that had been backed up with the --single-data-file option.

gpbackup_manager v1.4.1

New Feature

  • [178954451] The gpbackup_manager utility can now successfully delete backups that had been left in a partial delete state.

Backup/Restore Plugin API

No changes since Tanzu Greenplum Backup and Restore version 1.19.0.

gpbackup_ddboost_plugin v1.6.0

No changes since Tanzu Greenplum Backup and Restore version 1.21.0.

gpbackup_s3_plugin v1.7.0

No changes since Tanzu Greenplum Backup and Restore version 1.21.0.

Data Domain Boost

This release of gpbackup and gprestore supports Data Domain Boost for backup on Red Hat Enterprise Linux. This table lists the supported versions of DDOS, Data Domain Boost SDK, and BoostFS.

Table 1. Data Domain Boost Compatibility
DDOS Data Domain Boost BoostFS
7.5 7.5 7.5
7.4 7.4 7.4
7.2 7.2 7.2
7.1 7.1 7.0
6.2 3.5 1.3
6.1 (all versions) 3.4 1.1
6.0 (all versions) 3.3 n/a
Note: In addition to the DDOS versions listed in the previous table, gpbackup and gprestore support all minor patch releases (fourth digit releases) later than the certified version.

Known Issues

  • When attempting to restore data from Greenplum 4.3.x/5.x/6.x (prior to Greenplum v6.14.1 and v5.28.6), views with anyarray typecasts are not restorable. From Tanzu Greenplum Backup and Restore v1.20.3, gpbackup generates an error when such views are detected.

    Workaround: On the original cluster, identify any views that exhibit this symptom, using a query similar to:

    SELECT relname AS anyarray_views 
                      FROM pg_class WHERE relkind = 'v' AND oid >= 16384 AND (pg_get_viewdef(oid) 
                      LIKE '%::anyarray%') IS TRUE; 

    Then select option 1 or 2:

    1. Using the backup set with the errors, run gprestore with the --on-error-continue flag. The affected views will not be re-created. After the restore completes, re-create each VIEW using your original VIEW definition.
    2. Drop each affected VIEW on the original Greenplum cluster. Take another backup of the older cluster and run gprestore on the new cluster. Finally, recreate the VIEW on the new cluster using the original VIEW definition.
  • When attempting to restore data from Greenplum 4.3.x/5.x into Greenplum 6.x, if the restore involved a table distributed by character(n) or char(n) using the legacy bpchar hash operator, the restore would fail. This issue has been resolved in Greenplum Database 6.12. Upgrade to the latest Greenplum release to avoid this issue.
  • gprestore does not support restoring a backup that contains partitioned tables where the table is created with a non-reserved keyword that is used as a partition name. For example, the non-reserved keyword at is used as a partition name in this SUBPARTITION TEMPLATE clause fragment:
    ... 
                  SUBPARTITION TEMPLATE
                  ( SUBPARTITION "at" VALUES ('usa'),
                  ...

    gpbackup backs up the partitioned table, but gprestore returns an error when attempting to restore the table.

    Before performing a backup with gpbackup, you must ensure that partitioned tables do not use any of these non-reserved keywords as a partition name:

    ADD, ALTER, ALWAYS, AT, ATTRIBUTE, CATALOG, COMMENTS, CONFIGURATION, CONFLICT, CONTINUE, CURRENT, DATA, DAY, DENY, DEPENDS, DICTIONARY, DISCARD, DOCUMENT, DXL, EVENT, EXTENSION, FAMILY, FILESPACE, FILTER, FULLSCAN, FUNCTIONS, HOUR, IDENTITY, IGNORE, IMPORT, INITPLAN, INLINE, LABEL, LEAKPROOF, LOCKED, LOGGED, MAPPING, MATERIALIZED, METHOD, MINUTE, MONTH, NOCREATEEXTTABLE, OFF, ORDERED, ORDINALITY, OVER, PARALLEL, PARSER, PASSING, PLANS, POLICY, PROGRAM, RANDOMLY, READABLE, READS, RECURSIVE, REF, REFRESH, REJECT, REPLICATED, ROOTPARTITION, SECOND, SEQUENCES, SERVER, SKIP, SNAPSHOT, SQL, STANDALONE, STRIP, TABLES, TEXT, TRANSFORM, TYPES, UNLOGGED, VALIDATION, VARYING, VIEWS, WEB, WHITESPACE, WITHIN, WITHOUT, WRAPPER, WRITABLE, XML, YEAR, YES

  • A gprestore operation using the --redirect-schema option fails if gprestore attempts to restore an index in a schema and the name of the index is the name of the schema followed by a '.' (period). For example, this CREATE INDEX command creates the index named test. on a table in the schema test. The index is in the schema test.

    CREATE INDEX "test." ON test.mytbl USING btree (i);
    If the index and table are backed up with gpbackup, restoring the backup with this gprestore command fails because gprestore fails to restore the test. index.
    gprestore --timestamp <timestamp> --redirect-schema foo2
  • Beginning with versions 4.3.33 and 5.19, Greenplum Database checks that the distribution key for a table is a prefix of any unique index key. This policy is not in place for Greenplum Database versions before 4.3.33 or 5.19, and it is possible to create a backup of a database from one of these earlier versions with unique indexes that do not comply with the policy. When you restore such a backup to a Greenplum Database version that does enforce the policy:
    • If the unique index is for a primary key constraint, Greenplum Database automatically modifies the table's distribution policy if the table has no data.
    • In other cases, creating a unique index with a key that does not begin with the table's distribution key fails.

    This issue affects restoring backups made from Greenplum Database 4.3.32.0, 5.18.0, or earlier to a Greenplum Database version 4.3.33.0, 5.19.0, 6.0, or later system. The issue affects the gprestore, gpdbrestore, and pg_restore utilities.

Differences Compared to Open Source Greenplum Backup and Restore

Tanzu Greenplum Backup and Restore includes all of the functionality in the open source Greenplum Backup github repository and S3 storage plugin repository and adds:

  • Greenplum backup plugin for DD Boost
  • Greenplum gpbackup_manager utility
  • Greenplum Backup and Restore installation file in gppkg format

Release Numbering Conventions

The Tanzu Greenplum Backup and Restore distribution release number indicates the type of the release.

  • The first number is the gpbackup/gprestore major release number. For example, given the release number, 1.16.0, the major release number is 1.
  • The second number is the minor release number. Given the release number 1.16.0, the minor release number is 16. This number increments when new features are added to the gpbackup/gprestore utilities.
  • The third number is the maintenance release number. This number increments when the gpbackup/gprestore utilities included in the distribution contain fixes without new features, or if one or more components included in the distribution, such as gpbackup_manager and the backup storage plugins, have been updated.

The release versions of the components included in the distribution, such as gpbackup_manager and the backup storage plugins, are separate from the distribution version, but follow the same numbering scheme as the distribution.