Node Failure Recovery of Single-Node Systems | Teradata Vantage on Azure (DIY) - 2.3 - Node Failure Recovery of Single-Node Systems - Teradata Vantage on Azure

Teradata Vantageā„¢ on Azure (DIY) Installation and Administration Guide

Teradata Vantage on Azure
Release Number
April 2022
Last Update
Content Type
Publication ID
English (United States)
Last Update
For single-node systems, recovering failed nodes is automatic in the following scenarios. You do not need to create a post-upgrade restore image.
  • If hardware issues occur on the host, Azure migrates the VMs to other hosts.
  • If platform issues occur, such as Hypervisor or guest agent issues, the VM might restart.
  • If planned maintenance is scheduled, updates to the host might pause the VM for about 30 seconds. For some updates, the VM might restart.

For unexpected restarts, check the Azure Activity Log. If you do not find information related to the restart, create an Azure support request to see if Azure can look for issues in their backend availability logs. See Azure Documentation Center.

If your VM does not automatically restart after 10 minutes, check the alerts in Server Management or Viewpoint. If a kernel fails or becomes unresponsive due to Azure Guest OS issues, the failed node is not recovered automatically and might require manual debugging.

For assistance, contact Teradata Customer Support.