Locality and HA Guidelines | Teradata Teradata Fabric Manager - Teradata Fabric Manager Locality and High Availability Guidelines - 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

A high availability environment requires at least two Teradata Fabric Manager instances to make sure there is no disruption to the Teradata Fabric functionality if one instance goes offline during a planned or unplanned outage. Teradata recommends that the Teradata Fabric Manager is kept in the same data center or region so that query metrics and logs generated by Teradata Fabric queries do not leave the region. If a region only has a small number of data source nodes, then it is okay to use Teradata Fabric Manager in a different region. The relationship between a data source node and Teradata Fabric Manager is based on the data center where each component resides. When adding new data source systems, choose the data center associated with the preferred Teradata Fabric Managers.