From 735c3ece79b6694c9841d234e054bbd731d1ccb9 Mon Sep 17 00:00:00 2001 From: David Yozie Date: Fri, 28 Jun 2019 14:35:47 -0700 Subject: [PATCH] Docs: Remove 4.x info from gpcopy migration instructions; focus on 5 to 6 migration --- .../admin_guide/managing/gpcopy-migrate.xml | 87 ++++++------------- 1 file changed, 25 insertions(+), 62 deletions(-) diff --git a/gpdb-doc/dita/admin_guide/managing/gpcopy-migrate.xml b/gpdb-doc/dita/admin_guide/managing/gpcopy-migrate.xml index c0a832bc55..4d26e418f9 100644 --- a/gpdb-doc/dita/admin_guide/managing/gpcopy-migrate.xml +++ b/gpdb-doc/dita/admin_guide/managing/gpcopy-migrate.xml @@ -9,8 +9,7 @@ a high-performance utility that can copy metadata and data from one Greenplum database to another Greenplum database. You can migrate the entire contents of a database, or just selected tables. The clusters can have different Greenplum Database versions. For example, you - can use gpcopy to migrate data from Greenplum Database version 5.9.0 or later - to version 6.0.

+ can use gpcopy to migrate data from Greenplum 5 to Greenplum 6.

The gpcopy utility is available only in the commercial release of Pivotal Greenplum Database.

The gpcopy interface includes options to transfer one or more full @@ -53,12 +52,8 @@ compatible Greenplum Clients package to meet the gpcopy dependencies.

-

gpcopy supports migrating data from a Greenplum Database 4.3.26 or later - cluster to a Greenplum Database 5.9 or later cluster. However Greenplum Database 4.3.26 and - later do not include the actual gpcopy utility. You must manually copy the - gpcopy utility from your version 5.9 or later cluster into the older - version cluster to migrate data. For - example:$ cp /usr/local/greenplum-db-5.9.0/bin/gpcopy /usr/local/greenplum-db-4.3.26.0/bin/

+

gpcopy supports migrating data from a Greenplum 5 cluster to a Greenplum + Database 6 cluster.

gpcopy does not currently support SSL encryption for its connections.

@@ -67,8 +62,7 @@

If you are copying data between Greenplum Database clusters having different versions, each cluster must have gpcopy installed locally. gpcopy is - installed with Pivotal Greenplum Database starting with versions 5.9.0. For Greenplum - Database 4.3.x, gpcopy is supported for versions 4.3.26.0 and later.

+ installed with Pivotal Greenplum Database starting with version 5.9.

gpcopy transfers data from user databases only; the postgres, template0, and template1 databases cannot be transferred. Administrators must transfer configuration files manually @@ -161,19 +155,13 @@

  • Start both the source and destination clusters.
  • Perform a full database backup in the source Greenplum Database system. See .
    • -
  • (Migrating from 4.3.x) While Greenplum Database 4.3.26 and later support migration - with gpcopy, Greenplum Database 4.3.x does not include the - gpcopy utility. If you are migrating from a version 4.3.x system, - Pivotal recommends that you copy the utility from your Greenplum Database 5.x - installation to the 4.3.x installation. For - example:$ cp /usr/local/greenplum-db-6.0/bin/gpcopy /usr/local/greenplum-db-4.3.26.0/bin/
    • -
  • (Migrating from 4.3.x) As a best practice, source the - greenplum_path.sh file in the source Greenplum Database 4.3.x - installation, so that you execute gpcopy from the source system. For - example:$ source /usr/local/greenplum-db-4.3.26.0/greenplum_path.sh
    • +
  • As a best practice, source the greenplum_path.sh file in the source + Greenplum 5 installation, so that you execute gpcopy from the source + system. For + example:$ source /usr/local/greenplum-db-5.20.0/greenplum_path.sh
  • Use gpcopy with the --full option to migrate your data to the destination system. A full migration automatically copies all database - objects including tables, es, views, roles, functions, user defined types (UDT), + objects including tables, indexes, views, roles, functions, user defined types (UDT), resource queues, and resource groups for all user defined databases. Include the --drop to drop any destination tables that may already exist (recreating es as necessary). For example: @@ -185,11 +173,10 @@ destination tables to validate the data transfer (--validate count option). The other gpcopy options specify the source and destination Greenplum Database system master hosts, ports, and the User ID to use to connect to - the Greenplum Database systems. - While the example command performs a full system copy, consider migrating only - portions of the your data at a time, so that you can reduce downtime while - addressing table errors or validation failures that may occur during the copy - operation.

    • + the Greenplum Database systems. While the example command performs a full system + copy, consider migrating only portions of the your data at a time, so that you can + reduce downtime while addressing table errors or validation failures that may occur + during the copy operation.

  • The gpcopy utility does not copy configuration files such as postgresql.conf and pg_hba.conf. You must set up the destination system @@ -197,23 +184,14 @@
  • The gpcopy utility does not copy external objects such as Greenplum Database extensions, third party jar files, and shared object files. You must recreate these external objects as necessary to match the source system.
    • -
  • (Migrating from 4.3.x) Greenplum Database 5.0 and later removes automatic implicit - casts between the text type and other data types. After you migrate from Greenplum - Database version 4.3.x to version 6.0, this change in behavior may impact existing - applications and queries. Refer to About Implicit Text Casting in Greenplum Database in - the Greenplum Database Installation Guide for information, including a - discussion about supported and unsupported workarounds.
  • After migrating data you may need to modify SQL scripts, administration scripts, and user-defined functions as necessary to account for changes in Greenplum Database version - 6.0. Look for Upgrade Action Required entries in the Pivotal Greenplum - 6.0 Release Notes for features that may necessitate post-migration tasks.
    • + 6.0. See the Pivotal Greenplum 6.0 Release + Notes for features or changes that may necessitate post-migration tasks.

    See the gpcopy reference - page - in the Greenplum Database Utility Guide - for complete syntax and usage information.

    + page for complete syntax and usage information.

    @@ -274,16 +252,10 @@ ORDER BY 4 DESC LIMIT 5; free enough disk space to cover the sum of the table sizes shown in the above query, or consider using a smaller --jobs value to reduce the free space requirements.

    -
  • (Migrating from 4.3.x) While Greenplum Database 4.3.26 and later support migration - with gpcopy, Greenplum Database 4.3.x does not include the - gpcopy utility. If you are migrating from a version 4.3.x system, - Pivotal recommends that you copy the utility from your Greenplum Database 6.0 - installation to the 4.3.x installation. For - example:$ cp /usr/local/greenplum-db-6.0/bin/gpcopy /usr/local/greenplum-db-4.3.26.0/bin/
    • -
  • (Migrating from 4.3.x) As a best practice, source the - greenplum_path.sh file in the source Greenplum Database 4.3.x - installation, so that you execute gpcopy from the source system. For - example:$ source /usr/local/greenplum-db-4.3.26.0/greenplum_path.sh
    • +
  • As a best practice, source the greenplum_path.sh file in the source + Greenplum 5 installation, so that you execute gpcopy from the source + system. For + example:$ source /usr/local/greenplum-db-5.20.0/greenplum_path.sh
  • Use a gpcopy with the --truncate-source-after and --validate options to migrate your data to the destination system. A full migration automatically copies all database objects including tables, es, views, @@ -313,23 +285,14 @@ ORDER BY 4 DESC LIMIT 5;
  • The gpcopy utility does not copy external objects such as Greenplum Database extensions, third party jar files, and shared object files. You must recreate these external objects as necessary to match the source system.
    • -
  • (Migrating from 4.3.x) Greenplum Database 5.0 and later removes automatic implicit - casts between the text type and other data types. After you migrate from Greenplum - Database version 4.3.x to version 6.0, this change in behavior may impact existing - applications and queries. Refer to About Implicit Text Casting in Greenplum Database in - the Greenplum Database Installation Guide for information, including a - discussion about supported and unsupported workarounds.
  • After migrating data you may need to modify SQL scripts, administration scripts, and user-defined functions as necessary to account for changes in Greenplum Database version - 6.0. Look for Upgrade Action Required entries in the Pivotal Greenplum - 6.0 Release Notes for features that may necessitate post-migration tasks.
    • + 6.0. See the Pivotal Greenplum 6.0 Release + Notes for features and changes that may necessitate post-migration tasks.

    See the gpcopy reference - page - in the Greenplum Database Utility Guide - for complete syntax and usage information.

    + page for complete syntax and usage information.

    -- GitLab