Upgrade Operation Timeline

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
The following table outlines the general tasks involved when performing a SLES 10 to SLES 11 upgrade operation. The time required to complete the tasks depends on a number of factors including amount of third-party software that must be installed on the SLES 11 system post upgrade, and the number of rule sets for which workloads are being migrated. Likewise, the type and degree of manual intervention required may vary based on environment. The upgrade operation is led by Teradata Customer Services staff, who engage the customer as needed.
Activity Estimated Time Frame Tasks
Upgrade preparation 1 to 2 hours
  • Confirm that the customer has completed workload pre-migration activities, if applicable
  • Ensure that all users have exited the system
  • Stop system processes
  • Install all required software at required versions, including the Parallel Upgrade Tool (PUT) used to facilitate the upgrade process
  • Verify availability of all required licenses and software patches
  • Identify configuration settings that require modification prior to the upgrade
  • Resolve all system errors and warnings
  • Back up the TDWM database
  • Manually copy files not automatically moved as part of the upgrade process, such as third-party software configuration files and user-defined function (UDF) source code, if applicable
  • Identify any existing custom security hardening measures that the customer wants to also implement on SLES 11
PUT operation 2 to 4 hours
  • Confirm alternate boot environment health and alert absence
  • Use PUT to perform certain validation and operational steps including acquisition and distribution of software installation packages
  • Manually intervene as required, such as for password validation, file backup, and custom configuration setting restoration
Downtime 1 to 2 hours
  • Use PUT to shut down and restart database and nodes, perform required verification operations, install Teradata and Linux software, verify links in new environment, and related activities
  • Validate ethernet device renumbering
  • Install required third-party software
  • Restore files and configuration settings, as necessary
  • Validate various system parameters
  • Execute program to convert rule sets for workload-configuration migration
  • Confirm successful integration with Teradata Viewpoint
  • Verify that custom security hardening measures are implemented in the new environment, if applicable
Post-upgrade work 1 hour
  • Install hardware-specific BIOS-access software
  • Verify that the UDF source code is restored to original directories, if applicable
  • Execute PUT utility log collection function to gather information about the upgrade process