Hot Standby Node

A Hot Standby Node (HSN) is a node that is a member oI a clique that is not
conIigured (initially) to execute any Teradata vprocs. II a node in the clique Iails, the
AMPs Irom the Iailed node move to the hot standby node. The perIormance
degradation is 0.
When the Iailed node is recovered/repaired and restarted, it becomes the new hot
standby node. A second restart oI Teradata is not needed.
Characteristics oI a hot standby node are:
O A node that is a member oI a clique.
O oes not normally participate in the trusted parallel application (TPA).
O Can be brought into the conIiguration when a node Iails in the clique.
O elps with unplanned outages.
O liminates the need Ior a restart to bring a Iailed node back into service.
ot Standby Nodes are positioned as a perIormance continuity Ieature.
Performance degradation is 0 as AMPs are moved to the Hot Standby Node
When node is recovered it becomes the new Hot Standby Node



HSN stands for Hot Stand By and in the event of failure of a node(s) in MPP system - HSN nodes takes over. HSN will be
configured into the system in such a way that they can take over the duty of failed node. The concept is in the event of failure
it will take all the work of the failed node it means the AMP Processes on failed node will be migrated to it and the failed node
moves out of configuration. AMP less node is sometimes the node is only configured with PEs on that. They are different. TD
Manual will have more information on this.
Crapler 1: v2R5.0.1 Fealures ard updales
Hot Standby Nodes
Re|ease 3urrary 1 - 9
ot Standby Nodes
The ot Standby Node Ieature allows a spare node to be specially conIigured
and added to a production system as a backup node. uring the restart caused
by a Iailed node, a system conIigured with a hot standby node automatically
migrates all vprocs Irom the Iailed node to the node that you designate as the
'hot standby. The hot standby node Iully replaces the Iailed production node.
When the Iailed node returns to service, it becomes the new hot standby.
ConIiguring a hot standby node can eliminate the system-wide perIormance
degradation associated with the loss oI a single node in a single clique. ot
Standby nodes must be conIigured as part oI an initial system installation or
expansion.
The hot standby node Ieature eliminates:
Restarts that were required to bring a Iailed node back into service
egraded service during the period vprocs migrate to other nodes in a
clique
#:es for Use
A ot Standby Node must be employed as Iollows:
Must be a member oI a clique (maximum one standby node per clique)
oes not normally participate in the Trusted Parallel Application (TPA)
Is brought into the TPA to compensate Ior the loss oI a node in the clique
Hot Standby Node Log
The Teradata atabase startup log has been revised to include inIormation on
ot Standby Nodes.
Previously, the Teradata atabase startup logged:
An event Ior each down node
The total number oI down nodes
V2R5.0.1 adds expanded logging inIormation as Iollows:
W nodes online
X oI Y standby nodes used
Z nodes down
T total nodes
The Iollowing table shows how the logging output changes depending on
whether the system has been conIigured with ot Standby Nodes, and
whether or not there are any down nodes.
Crapler 1: v2R5.0.1 Fealures ard updales
Hot Standby Nodes
1 - 10 Re|ease 3urrary
IF the system does not have. THEN the foIIowing information is omitted.
hot standby nodes conIigured X oI Y standby nodes used.
down nodes Z nodes down.
hot standby nodes conIigured, or the
number oI active standby nodes equals
the number oI down nodes
T total nodes.