Enabling Node Failure Recovery

Prerequisite
You must create a service principal before enabling the node failure recovery feature. See Creating an Azure Active Directory Application and the Service Principal.
When the failed node is stopped, you may lose the diagnostic information.
  1. From the Azure portal, note the private IP and either the public IP or private DNS of the Teradata Database VM.
  2. From the SSH client console, connect to the VM by logging on to the VM using the same authentication type you chose when you deployed the VM using the Teradata ecosystem solution template.
    Authentication type Action
    SSH public key Enter the following:
    # ssh -i ssh-private-key.pem azureuser@VM-public-IP-address or VM-public-DNS-address
    where:
    • The ssh-private-key is the private key file (.pem) specified when you deployed the VM.
    • The azureuser is the user name specified when you deployed the VM.
    • The VM-public-IP-address or VM-public-DNS-address is the DNS host name or public IP address of the VM.
    Password Enter the following:
    # ssh azureuser@VM-public-IP-address or VM-public-DNS-address
    Password: password
    where:
    • The azureuser is the user name specified when you deployed the VM.
    • The VM-public-IP-address or VM-public-DNS-address is the DNS host name or public IP address of the VM.
    • The password is the password specified when you deployed the VM.
  3. Switch to the root user environment.
    # sudo su -
  4. Enable the node failure recovery feature and enter responses to the prompts.
    1. Run tdc-nodestart-init without arguments.
      # tdc-nodestart-init
    2. Enter the client ID of your service principal.
    3. Enter the secret key of your service principal.
    4. Enter the tenant of your service principal.
    5. Enter your Azure subscription ID.
    Credentials validation succeeded displays. Service principal details are written to /etc/opt/teradata/tdconfig/service_principal_config.json.
  5. While the feature runs, do the following:
    1. Check /var/log/tdc-nodestart-PMA-ID.log for errors.
    2. Check /var/log/messages for messages.
    3. Check /var/log/boot.log for information.
  6. After the feature finishes, go to the Azure portal to check the deployment logs to see if the deployment of the replacement node was successful.

results matching ""

    No results matching ""