Upgrade Compared to Migration

Preparing to Move from SLES 10 to SLES 11

Published
January 2016
Language
English (United States)
Last Update
2018-05-04
dita:mapPath
bdv1467307738050.ditamap
dita:ditavalPath
ft:empty
dita:id
yiu1467244923010
Product Category
Hardware
Software
There are two paths for transitioning a Teradata system from SLES 10 to SLES 11: upgrade and migration.
Path Context
Upgrade If your existing hardware supports SLES 11, you can upgrade the operating system in place without migrating data.

This path is available for the following platforms: 560P, 670, 1XXX (1650 and above), 2XXX (2650 and above), 5XXX (5600 and above), and 6XXX (6650 and above).

Migration If you have purchased different hardware that supports SLES 11, you must migrate data from your SLES 10 system to your SLES 11 system.

This path is the only means of upgrading from the following platforms: 550P, 551P, 1XXX (below 1650), 2XXX (below 2650), and 5XXX (below 5600).

In either case, the required steps for transitioning a Teradata system vary depending on existing database and operating system versions.

Pre- and post-upgrade workload-management licensing, which may be dictated by existing hardware, also influence the following aspects of the upgrade:
  • Means of migrating workloads
  • Tasks to prepare workloads for migration
  • Workload-management options and required configuration post upgrade

Preparation and planning are key to a successful operating system upgrade. Consult with Teradata Customer Services well in advance to establish an approach for performing the upgrade, including roles and responsibilities.