Upgrade Overview | Teradata Fabric - About Teradata Fabric Upgrade - Teradata Fabric

Teradata® Fabric - Installation and User Guide - 3.11
Product
Teradata Fabric
Release Number
3.11
Publication Date
August 2026
Content Type
Administration
Configuration
Installation
User Guide
Publication ID
B035-5991-086K
ft:locale
en-US
ft:lastEdition
2026-08-15
dita:mapPath
svw1780362788070.ditamap
dita:ditavalPath
ezw1784752870623.ditaval
ft:sourceId
dita
dita:id
lxg1591800469257
Important: Before upgrading your Teradata Fabric 2.x system to Teradata Fabric 3.0 on Teradata, you must create a change request on https://support.teradata.com to receive special 3.0 upgrade instructions. For more information, go to https://support.teradata.com and search for KB0048892.

The following additional requirements are necessary when upgrading to Teradata Fabric 3.0:

  • The system must be running Teradata Fabric 2.15 or later.
  • You must first upgrade the system to Teradata Fabric 3.0 before upgrading to later Teradata Fabric 3.x versions.

    Once your system is upgraded to Teradata Fabric 3.0, any subsequent 3.x upgrades can follow the upgrade instructions in this section.

The steps for upgrading Teradata Fabric Manager are similar to those for installing it, whereas the upgrade processes for connectors, fabrics, and node software differs from the installation process.
If upgrading a site with a full Teradata stack and analytical nodes, open an incident with the Teradata Fabric GSO team for consultation before upgrading.
For connectors and fabrics, the upgrade process allows you to test new versions before deploying the new versions to production. Upgrades to these components are considered configuration changes. For each configuration, three versions can co-exist:
  • Active
  • Pending
  • Previous

This protocol provides for pushing changes to all systems before implementation, allowing you to test new connectors and fabrics on production deployments without affecting production workloads.

You can also update links, networks, and communication policies. Like connector and fabric upgrades, such updates are considered configuration changes and are subject to the same version and deployment protocol.

The upgrade process for Teradata Fabric node software differs from the installation process, with the final deployment steps being handled automatically by the pre-existing version of the software.