Upgrade Planning 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

Although each situation is unique, the general milestones in planning an upgrade from SLES 10 to SLES 11 are outlined in the following table.

Milestone	Timing	Tasks
Professional Services Upgrade Readiness Assessment	Starting at least 90 days before targeted upgrade date and finishing within 2 days	Ascertain upgrade type and focus Identify affected software (both Teradata and third-party) Determine software and hardware procurement requirements Detail workload management migration steps based on pre- and post-upgrade environment including licensing Itemize potential risks Determine required level of engagement with Professional Services Identify reference documents relevant to the upgrade scenario
Initial Risk Mitigation	Starting at least 60 days before and finishing at least 30 days before targeted upgrade date	Identify any existing custom security hardening measures that the customer wants to also implement on SLES 11 Provide the customer with the Pre-Migration Tool, if applicable based on upgrade scenario
Customer Support Core Pre-Upgrade Assessment	Starting at least 30 days before and finishing at least 10 days before targeted upgrade date	Collect system data and analyze system status Communicate identified issues to site team Confirm whether customer will be pre-migrating workloads
Report and Final Risk Mitigation	Starting at least 10 days before and finishing by targeted upgrade date	Present recommendations