Starting in release 17.00, DSA is the only supported backup and restore mechanism.
Two archive operations are required for a full system archive. First is a DBC All archive, followed by a DBC Only archive.
Databases to Exclude
The CRASHDUMPS database contains system- and release-specific crash information that will not be relevant to the destination system, so it should also be excluded from the migration.
SYSLIB database contains the GetTimeZoneDisplacement and algorithmic compression UDFs that may be referenced during the restoration process. SYSLIB is restored from the DBC All archive immediately after the DBC Only restore and before the DBC All restore. After all other user data is restored, the DIP scripts ensure that the SYSLIB database is current.
- If you were using non-Teradata geospatial data types on the source system, and want to keep using those data types on the destination system, you should archive and restore this database.
- If you were using non-Teradata geospatial data types on the source system, but want to use Teradata geospatial versions of the geospatial data types on the upgraded destination system, exclude SYSSPATIAL from the migration. The SYSSPATIAL database will be automatically created on the new system, and will contain definitions for the Teradata geospatial data types.
The Secure Zones feature allows creation of one or more separate and exclusive database hierarchies, called zones, within a single Advanced SQL Engine system. Access and administration for each zone is handled separately from the Advanced SQL Engine system and from other zones.
Only the owner of a Secure Zone can archive or restore databases within that zone, and that owner cannot be DBC. Each Secure Zone owner must create archive and restore jobs for the databases in their respective zones in order to perform a full-system migration. For more information, see Teradata Vantage™ - Advanced SQL Engine Security Administration, B035-1100.
Source Data Preservation
As a precaution, keep the source system operational with the original data until you are certain that the destination system is running correctly with the migrated data.