3.01.01 - Upgrade Overview - Teradata Database on VMware

Teradata Database on VMware Base, Advanced, Enterprise Tiers Getting Started Guide

Teradata Database on VMware
Deployer 3.01.01
January 2018

Major and minor upgrades, reconfigurations, and expansions require a system redeployment. For information on how to upgrade the Teradata Database running in a virtual or public cloud environment, log on to https://access.teradata.com and search for KCS001779.

Before a minor or e-fix upgrade in a virtual or public cloud environment, the requirements related to the listed considerations are shown in the table.
Upgrade Consideration Requirement
Bundle Download Mechanism You obtain software upgrade bundles from Teradata Support, which uses Akamai for the download process. If you are a new Akamai user, you are prompted to complete additional steps related to Akamai setup when first downloading an upgrade bundle.
Operating System Updates Because the operating system software bundle includes both important security updates and the latest version of the utility used to upgrade Teradata components (PUT), you must download this bundle whenever upgrading other Teradata components with the exception of Server Management, for which the required updates are included in the image itself.
Outage Preparation When upgrading the operating system and Teradata components including Server Management, PUT does not set a maintenance window but does automatically reboot the system. Be sure to plan accordingly.
Data Backups If performing a major or minor upgrade, use DSC to archive the existing Teradata Database. After the upgrade, use DSC to restore the archive. For more information, see DSC Configuration. You do not need to archive and restore data for maintenance and efix upgrades.
Cross-Tier Migration You cannot migrate from the Teradata Database on VMware Base, Advanced, or Enterprise Tiers to the Teradata Database on VMware Developer Tier. They are separate products.