Installation/Migration Path - Teradata Database

Teradata Database Node Software Upgrade Guide: Overview and Preparation

Product
Teradata Database
Release Number
16.10
15.10
Published
July 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
ecl1480972909700.ditamap
dita:ditavalPath
ft:empty
dita:id
cvc1467245366194
Product Category
Software

A migration process involves archiving user data from a source system, then restoring that data to a destination system. The destination system must already have Teradata Database installed before the migration process occurs.

Teradata supports migrations from no more than two previous versions of the Teradata Database using the migration process. If your starting version is more than two versions removed from the target version, you may need to use a multi-step migration, involving intermediary Teradata versions.

When moving from one operating system to another, a migration process is required. For example, moving from an MP-RAS system to a Linux system requires archiving user data from the source MP-RAS system, then restoring the data to a destination system running Linux. The destination system may be the same physical system as the source. In this case, after archiving the user data, the system requires a fresh installation of the operating system, the Teradata Database (either the same version or a more recent version), and other node software. Additionally, some hardware upgrades may be required. Consult your Teradata Services Consultant for details specific to your Teradata system.