System Seeding Best Practices - Teradata Ecosystem Manager

The full system seeding workflow has the following features:

• Uses the Teradata ARC utility and Ecosystem Manager workflows to run.
• Allows target systems anywhere (on-premises systems, private/public cloud systems).
• Provides REST APIs to support workflow generation, deployment, and execution.
• Supports the Teradata Database 14.10 and later.

• Data copying is limited to the Ecosystem Manager appliance infrastructure and network bandwidth between the source and target Teradata systems and Ecosystem Manager Appliance.
• This feature only supports the all-AMP ARC main copy and does not support the multi-ARC copy using the TARA server.
  • There is limited support for the Teradata MAPS feature when using ARC. ARC requires using an all-AMP map, if the source system has maps that are not all-AMP maps, those maps will not be copied as part of the full system seeding.
• The Rollback option only deletes user data. If a full recovery from the system seeding is needed, run the sysinit and dipall commands to return the target system back to the original state.

• Both the source and target system must be Teradata Database 14.10 or later.
• The Teradata source system version cannot be greater than the Teradata target system version. For example, if the source system is 16.10, the target system must be 16.10 or later.
• The target system should not contain any user data.
• For the target system, enable only dbc logon. This is important during the dictionary copy step. See Enabling dbc Logons.

• Copying a primary Teradata system, including dictionary and data, to a newer or existing empty Teradata system for disaster recovery.
• Copying a primary Teradata system to a cloud-based instance for on-demand analytics and reporting.
• Copying an initial dictionary only.