Deploying Teradata Data Mover from a Solution Template

Prerequisite
You must be logged into the Azure portal using an account with a sufficient level of permissions in the Azure subscription and be assigned the role at the subscription level. For more information, see the Azure Documentation Center and search for Get started with access management in the Azure portal and Use role assignments to manage access to your Azure subscription resources. In addition, check if Azure service limits need to be increased. For more information, see Azure Service Limits.
The deployment 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 all the software application VMs.

This template creates one NSG for Teradata Data Mover during the deployment process. All ports to the NSG are opened automatically after completing this procedure. For information on which ports are opened, see Network Security Groups and Ports.

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.

For information on taking down an Azure VM, Stop, Deallocate, or Delete a VM in Azure.

  1. Log in to Azure Marketplace portal using your user name and password.
  2. Click located in the upper left and search for Teradata.
    A list of Teradata products appears under the Results pane.


  3. Select Teradata Data Mover.
  4. Click the Basics blade to configure basic settings.
    Parameter NameAction
    User nameEnter the operating system admin name used to log in.
    Authentication typeSelect an authentication method.
    Note
    For security reasons, an SSH public key is strongly recommended.
    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.
    SubscriptionSelect an Azure subscription.
    Resource groupSelect one of the following:
    • Create new and enter a name for the resource group.
    • Use existing and select an empty existing resource group.
    LocationSelect a region where you want to deploy the solution and where all resources will be created.
  5. Click OK.
  6. Click the Data Mover blade.
    Parameter NameAction
    DBC user passwordEnter a new default Teradata Database user password for the Data Mover internal repository between 8 and 15 characters long, consisting of letters and numbers, but it does not have to contain numbers. It must start with a letter.

    For security reasons, you must change the default dbc password to a different password.

    Confirm DBC user passwordEnter the password again to confirm.
    DATAMOVER user passwordEnter the user password to be used to access the internal DATAMOVER repository.

    For security reasons, you must change the default datamover password to a different password.

    Confirm DATAMOVER user passwordEnter the password again to confirm.
    Data Mover system name prefixEnter 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 agentsEnter the number of additional agents (nodes) you want to deploy from 0 to 3. One node is already included for the master.
    VM sizeTo change the size, do the following:
    1. Click to display a list of VM sizes for the storage type you want.
    2. Click to highlight the size you want.

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

    3. Click Select.

    The storage size is per node. For more information, see Supporting Software VM Sizes.

  7. Click OK.
  8. Click the Network Settings blade to configure the virtual network.
    Parameter Name Action
    Virtual networkExisting virtual networkSelect 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.

    SubnetsVM subnet nameSelect the existing VM subnet named vmsubnet.

    The Teradata Database and software application VMs will be attached to this public subnet.

    Allow remote SSH access from (CIDR block)Enter a CIDR block for the public subnet. The template creates a new public subnet in the selected VNet using this CIDR address.

    For more information, see VNets.

    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 listUse the default or enter one or more network time protocol servers, separated by commas.
    Time zoneEnter the operating system time zone.

    The default time zone is UTC.

  9. Click the Summary blade, review the summary, and click OK.
  10. Click the Buy blade, review the terms of use and privacy policy, and click Purchase.
    This process can take anywhere between 20 to 60 minutes depending on your configuration and the availability of resources in your region.
    Note
    Trying to SSH into the VM may cause the creation of the VM to fail. Do not try to SSH into the VM until either you get confirmation the VM has been created or you receive a failure notification.
  11. 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 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.
  12. If you want to use public IP addresses, do the following after the VMs are created.
    1. Create the public IP addresses.
    2. Adjust the NSG rules to accept connections using public IP addresses.
      The solution template defines an NSG for each software product VM.
Postrequisite
Complete the applicable procedures under Data Movement Using Teradata Data Mover.

results matching ""

    No results matching ""