Release Notes

Release Notes

Pivotal Greenplum Backup and Restore utilities are released separately from Pivotal Greenplum Database, and are updated independently of the core server.

Version 1.18.2

Released 2020-06-05

Pivotal Greenplum Backup and Restore version 1.18.2 is a maintenance release that resolves an issue.

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 Pivotal Greenplum Backup and Restore.

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

gpbackup_ddboost_plugin v1.4.0

Resolved Issue

  • [30668] - This version resolves a known issue when using DD Boost v3.3, DDOS v7.1 and ifgroups. The plugin is updated to use the DDBoost shared library (libDDBoost.so) version 3.5. The DD Boost 3.5 library is compatible with DDOS 6.0, 6.1, 6.2, 7.0, and 7.1.

Version 1.18.1

Released 2020-05-15

Pivotal Greenplum Backup and Restore version 1.18.1 is a maintenance release that resolves an issue.

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 Pivotal Greenplum Backup and Restore.

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

gpbackup v1.18.1

Resolved Issue

  • [30639] Running gpbackup with the --include-table or --include-table-file options to back up a set of tables incorrectly backed up user-defined functions and protocols. This issue is resolved.

Version 1.18.0

Release 2020-05-08

Pivotal Greenplum Backup and Restore version 1.18.0 is a minor release.

Platform Support

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

  • Pivotal Greenplum Database 4.3.22 and later
  • Pivotal Greenplum Database 5.5.0 and later
  • Pivotal 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 Pivotal Greenplum Backup and Restore.

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

gpbackup v1.18.0

Features

  • The new option --without-globals skips backing up global metadata during the backup process. The option is valid a full database backup or with the --metadata-only option.
  • When performing a backup operation with a schema filtering option such as --include-schema and the schema contains a view, gpbackup does not lock the referenced tables if the table is in a different schema than the view. In previous releases, gpbackup locked the table.
  • gpbackup no longer exits when it attempts to back up certain database objects that are dropped during a backup operation. If a constraint, function, index, rule, or view is dropped during a backup operation, gpbackup logs a warnings and continues the backup process.

Resolved Issues

  • [30454] gpbackup did not correctly back up GRANT commands that were executed on extension functions.
  • [30560] gpbackup versions returned an error that stated cache lookup failed and exited when the backup operation attempted to back up a constraint, function, index, rule, or view that was dropped during the backup. Now the information is logged and the backup continues. This fix requires a Greenplum Database update that is in Greenplum 5 release 5.27.0 or later, and in Greenplum 6 release later than 6.7.1.
  • [30567] gpbackup used an incorrect REVOKE syntax on aggregate functions.
  • [30571] While backing up a schema that contained a view, gpbackup locked a table in a different schema if the table was referenced by the view. Now the table is not locked.
  • [171263572] If gpbackup encountered an error during the backup process, the report file contained an invalid duration.

gpbackup_helper v1.18.0

No changes since the previous release.

gprestore v1.18.0

New Features

  • You can use the --truncate-table option with the gprestore command, to truncate data from a set of tables before restoring the table data from a backup.
  • When performing a restore operation that uses the --with-stats option, Greenplum Database automatic updating of table statistics during the restore operation is disabled. Restored tables will only have statistics from the backup. To update restored table statistics you can use the ANALYZE command.

Resolved Issues

  • [171506474 ] gprestore did not update the modcount of COPY FROM SEGMENT statements during a restore operation.
  • [171224448] Resolved a table filtering issue that occurred if a table name provided with --include-table contained a single quote ('). Table names that contain a single quote are now supported if the single quote is escaped or the table name is encapsulated in double quotes (for example, --include-table public.'foo\'bar' or --include-table public."foo'bar".
  • [172188554] Resolved a problem that prevented plug-in configuration files from being deleted on segment hosts when encryption was used.
  • [172297557] Resolved a gprestore issue with the pg_class table statistics columns reltuples and relpages, where the statistics were not restored correctly.
  • [172656786] Resolved an issue with the --incremental option (Beta) where the incremental restore was not properly filtering out existing external tables.
  • [172182425] When performing multiple, concurrent restores that use the gpbackup DD Boost storage plugin, some of the operations might not complete successfully.
  • [172462743] Resolved an issue where a restore operation performed with both the --with-stats and --redirect-schema options was not correctly updating statistics.

gpbackup_manager v1.2.0

New Feature

  • When using the DD Boost plugin, you can run multiple, concurrent instances of gpbackup_manager with the --replicate-backup option. When running the concurrent instances of gpbackup_manager to replicate backups, each gpbackup_manager command must specify a different timestamp for a different backup.

Resolved Issues

  • [172413417] Resolved an issue where gpbackup_manager did not display the correct report when a user specified the --backup-dir option with gpbackup.

gpbackup_ddboost_plugin v1.3.0

New Features

  • Support for Data Domain OS 7.1 with DD Boost 7.1
  • Support for Data Domain OS 6.2 with DD Boost 3.5

gpbackup_s3_plugin v1.3.0

Changed Feature

  • The S3 plugin download and upload capability and speed were improved by using increased concurrency and reduced chunk size.

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.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

  • The gpbackup_s3_plugin v1.3.0 has a issue when the --metadata-only option is used.

    Workaround: You can either take a full backup, or install the v1.2.1 of the S3 plugin that can be found in the Pivotal Greenplum Backup and Restore v1.17.0 compressed tarball.

  • Running gpbackup with the --include-table or --include-table-file options to back up a set of tables incorrectly backs up user-defined functions and protocols. (Resolved in gpbackup version 1.18.1.)

    Workaround: When running gprestore to restore the tables from the backup, use the same --include-table or --include-table-file options that were used to create the backup.

  • A gprestore operation with the --incremental option (Beta) recreates existing postdata objects. The operation consequently errors out with an already exists message.
  • 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

Pivotal 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 Pivotal 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.