Number of Teradata Fabric Manager Instances - Teradata Fabric

Teradata® Fabric - Installation and User Guide - 3.11
Product
Teradata Fabric
Release Number
3.11
Published
August 2026
ft:locale
en-US
ft:lastEdition
2026-08-15
dita:mapPath
svw1780362788070.ditamap
dita:ditavalPath
ezw1784752870623.ditaval
dita:id
lxg1591800469257

For each Data Center, determine the number of Teradata Fabric Managers needed. One instance of Teradata Fabric Manager is installed on a TMS, customer-supplied server, or VM.

The following guidelines are based on the minimum hardware requirements for the TMS, server, or VM.

Requirements Description
TMS, Server, or VM for Teradata Fabric Manager One or more (separate server for each Teradata Fabric Manager instance).
Important: Do not install on existing TMS servers hosting Viewpoint, Data Mover, Ecosystem Manager, and so forth, unless those products are uninstalled and the server is re-purposed to be a Teradata Fabric Manager server.
Minimum number of Teradata Fabric Manager instances One instance for approximately every 200 Teradata Fabric-connected nodes:
  • This approximation is based on moderate query volume on minimum supported hardware requirements.
  • Actual required number varies depending on server specifications and query volume.
  • New Teradata Fabric Managers can be added if the load is high on existing instances to reduce the overall load.
Minimum number of Teradata Fabric Manager instances for high availability (HA) Two instances:
  • More than two instances can be deployed.
  • Multiple instances can be clustered for high availability and scalability.
  • Each instance in a cluster is fully active and maintains a full copy of the Teradata Fabric configuration.
Number of Teradata Fabric Manager instances to keep communication, heartbeats, query metrics, and log data local to a Data Center At least one per Data Center, more if the number of nodes in the Data Center exceed the resource requirements of the single Teradata Fabric Manager instance.

Server load is displayed by Linux utilities such as uptime and top. The load average should be less than the number of CPU cores. If the load is persistently higher than the number of CPU cores, this is a good indication that another Teradata Fabric Manager is needed.