Release Notes

Release Notes

Release Date: January 23, 2020

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

Version 1.16.0

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

New Features
  • gpbackup/restore .gppkg packages for Ubuntu 18 are now available to download from Pivotal Network.
  • Support for materialized views in Greenplum Database 6. Materialized view definitions are now backed up.
  • The gpbackup command checks that the executablepath field is set in the plugin configuration file. If executablepath is not set, the command prints -executablepath is required in config file and exits.
Changed Feature
  • The Pivotal Greenplum Backup and Restore distribution release number conventions have changed. A -n is no longer used to indicate that one or more included components is updated. See Release Numbering Conventions.

Resolved Issues

  • [30302] In certain cases, gpbackup may incorrectly back up statistics, which results in a gprestore error indicating a malformed array literal. This has been resolved.
  • [30374] In some cases when using gpbackup with BoostFS, the master metadata file was not explicitly closed at the end of a backup operation. This caused a zero byte file. This issue has been resolved.

gpbackup_helper v1.16.0

No changes since the previous release.

gprestore v1.16.0

New Features

  • When using gprestore with the --on-error-continue option, if metadata or data errors are encountered, gprestore writes text files in the backup directory with lists of the tables that encountered errors. Separate files are generated for metadata and data errors. The table names are listed in the format schema_name.table_name. These files can be used to:
    • identify tables to fix on the source system.
    • specify tables to include or exclude on subsequent restores using the --include-table-file or --exclude-table-file gprestore options.
  • Support is added for materialized views in Greenplum Database 6. Materialized view definitions are restored, but the views are not automatically refreshed. Administrators must manually run the command REFRESH MATERIALIZED VIEW view-name after the data has been restored to the view's source tables.
  • The restore command checks that the executablepath field is set in the plugin configuration file. If executablepath is not set, the command prints -executablepath is required in config file and exits.

Resolved Issue

  • [169235299 - gprestore] When performing a filtered restore, for example using the --include-table option, gprestore attempted to create all schemas present in the original backup. If a schema already existed in the target database, gprestore logged a warning:
    [WARNING]:-Schema <schema name> already exists
    This is fixed. Only schemas specified are created.
  • [30300] When a view was restored from a backup and the view definition contained the function gp_dist_random(), the definition of the restored view did not contain the function. This was an issue with how Greenplum Database handles of view definitions. This issue has been resolved in Greenplum Database 5.4.0 and 6.3.

gpbackup_manager v1.1.0

New Feature

  • A new replicate-backup field can be added to the DD Boost plugin configuration file to allow gpbackup_manager to perform Data Domain replication. The replication occurs outside the execution of gpbackup. You can replicate a backup set that has been backed up by gpbackup to a Data Domain system.

gpbackup_ddboost_plugin v1.2.0

New Feature

  • A new replication_streams field can be added to the plugin configuration file to specify the maximum number of streams used for Data Domain replication. If the field is not specified, the maximum number of streams is the number of segments.

gpbackup_s3_plugin v1.2.1

Changed Feature

  • Internal changes to better support the Go language. No functionality changes.

Known Issues

  • 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 adds:

  • Greenplum backup plugin for DD Boost
  • Greenplum backup_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.