Deploying Data Mover from a Solution Template - Teradata Software for Azure

Teradata Vantage™ on Azure (DIY) Installation and Administration Guide
Product
Teradata Vantage on Azure
Release Number
6.0
Published
November 2018
Language
English (United States)
Last Update
2018-12-10
dita:mapPath
nep1519417426771.ditamap
dita:ditavalPath
TeradataAzure_PubCloud_6.0.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud
  • You must log into the Azure portal using an account with sufficient permissions in the Azure subscription and be assigned the Contributor role at the subscription level. See Azure Documentation Center.
  • You might need to increase Azure service limits. See Azure Service Limits.
Deploying Data Mover from a solution template creates a new Azure resource group and connects the Data Mover VMs to an existing subnet in the same VNet as the Teradata Database VM and the software application VMs.

During the deployment process, this template creates one NSG for Teradata Data Mover. All ports to the NSG automatically open after completing this procedure.

If you want to use public IP addresses, you must create the public IP addresses after the VMs are created and adjust the NSG rules to accept connections using public IP addresses.

If the interface times out while performing the steps in this procedure, return to the previous blade and click OK again so you can continue where you left off.

  1. Log in to the Azure Marketplace.
  2. Click in the upper left and search the Marketplace for Teradata Data Mover.
  3. In the Results pane, select one of the following:
    Software Description
    Teradata Data Mover Individual purchase
    Teradata Data Mover (IntelliSphere) Included with Teradata IntelliSphere, whether hourly or BYOL.
  4. Click Create.
  5. Click the Basics blade to configure basic settings.
    Parameter Name Action
    User name Enter the operating system admin name used to log in.
    Authentication type Select an authentication method.
    For security reasons, Teradata strongly recommends an SSH public key.
    SSH public key
    Copy and paste an Open SSH public key which can be generated with tools such as PuTTY or SecureCRT.
    Password
    Enter a password of at least 12 characters, using at least 1 lower case character, 1 upper case character, 1 number, and 1 special character. Enter the password again to confirm.
    Subscription Select an Azure subscription.
    Resource group Select one of the following:
    • Create new and enter a name for the resource group.
    • Use existing and select an empty existing resource group.
    Location Select a region where you want to deploy the solution and where all resources will be created.
  6. Click OK.
  7. Click the Data Mover blade to configure the settings.
    Parameter Name Action
    DBC user password Enter a new default Teradata Database user password for the Data Mover internal repository, using 12 to 15 characters. It can consist of letters and numbers, but numbers are not required.

    For security reasons, you must change the default dbc password.
    Confirm DBC user password Enter the password again to confirm.
    DATAMOVER user password Enter the user password to be used to access the internal DATAMOVER repository, using 12 to 15 characters starting with a letter. It can consist of only letters and numbers.

    For security reasons, you must change the default datamover password.
    Confirm DATAMOVER user password Enter the password again to confirm.
    Data Mover system name prefix Enter a prefix for all Data Mover nodes.
    After the VM is created, this prefix appears in the Azure portal followed by the agent name and number. For example, a 4-node Data Mover cluster displays the following:
    • prefix-DM-Master-Agent1
    • prefix-DM-Agent2
    • prefix-DM-Agent3
    • prefix-DM-Agent4
    Additional agents Enter the number of additional agents (nodes) you want to deploy from 0 to 3. One node is already included for the master.
    VM size
    1. Click to display a list of VM sizes for the storage type you want.
    2. Highlight the size you want, then click Select.

      Although other sizes are available, the recommended size for production workloads is DS5_v2.

    Storage size is per node.
  8. Click OK.
  9. Click the Network Settings blade to configure the virtual network.
    Parameter Name   Action
    Virtual network Existing virtual network Select the existing virtual network containing the Teradata Database VM.

    Although you are not prevented from creating a new VNet, the purpose of this procedure is to deploy the Data Mover VMs on the same VNet as the Teradata Database VM and all software application VMs, such as Teradata Viewpoint, and so on.
    Subnets VM subnet name Select the existing VM subnet named vmsubnet.

    The Teradata Database and software application VMs will be attached to this private subnet.
    Allow remote SSH access from (CIDR block) Enter a CIDR block for the private subnet. The template creates a new private subnet in the selected VNet using this CIDR address.

    Check to ensure the CIDR address you enter is not being used by existing subnets in the same VNet by going to the Azure portal.
    NTP server list Use the default or enter one or more network time protocol servers, separated by commas.
    Time zone Enter the operating system time zone (UTC is the default).
  10. Click OK.
  11. Click the Summary blade, review the summary, and click OK.
  12. Click the Buy blade, review the terms of use and privacy policy, and click Purchase. This process can take 20 to 60 minutes depending on your configuration and the availability of resources in your region.
    Trying to SSH into the VM might cause the creation of the VM to fail. Do not try to SSH into the VM until you receive either a confirmation the VM was created or a failure notification.
  13. To monitor the VM creation progress, do the following from the Azure portal:
    1. Click to see notifications to determine if the deployment has started. Notifications send alerts only if you have set them prior to starting the deployment.
    2. From the left panel, click the Resource groups blade.
    3. Under the Name column, select a resource.
    4. Under Settings, click Deployments.
    5. Select any of the resources and look at the pane to the right to see if they are being deployed. The deployment is not complete until all VMs in the cluster are provisioned and the automatic process of configuring the database has finished. Under Operation details, a blue status symbol appears in the first column next to each resource to indicate the deployment process is continuing.
    6. Click located at the top of the right pane to refresh the pane. Under Operation details, the blue status symbol changes to a green check mark in the first column next to each resource to indicate the deployment process has finished.
    7. Under Operation details, when the STATUS column displays OK, select the resource. The PROVISIONING STATE displays Succeeded.
  14. If you want to use public IP addresses, do the following after the VMs are created.
    1. Create the public IP addresses and assign these addresses to a VM. See https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-public-ip-address.
    2. Adjust the NSG rules to accept connections using public IP addresses to allow access. The solution template defines an NSG for each software product VM.
Related information