Scale Up/Scale Down VM Sizes | Teradata VantageCloud Enterprise on Azure (DIY) - Scaling Up or Scaling Down VM Sizes - Teradata® VantageCloud Enterprise on Azure

VantageCloud Enterprise on Azure (DIY) Installation and Administration Guide - 2.4
Product
Teradata® VantageCloud Enterprise on Azure
Release Number
2.4
Published
April 2024
ft:locale
en-US
ft:lastEdition
2024-04-29
dita:mapPath
ztq1662440257891.ditamap
dita:ditavalPath
fui1635951983017.ditaval
dita:id
eqk1475705518038
Product Category
Cloud
PrerequisiteTo perform this procedure, you must be assigned the Contributor role.
You can scale a Vantage up or down by changing the VM sizes in the system. Be sure to scale only supported VM sizes.
Scaling unsupported VM sizes may impact database performance. Data loss will occur if scaling local storage VM sizes.
  1. Stop the database.
    # tpareset -x -y scale up / down
  2. Run the following command on all nodes to confirm the database is down.
    # pdestate -w
    PDE state: DOWN/HARDSTOP
  3. Set pdeconf off using /usr/pde/bin/pdeconf -s autostart=0
  4. From the Azure portal, click Stop on every VM.
  5. Scale the VMs up or down.
    1. From the Azure portal, locate the Vantage resource group.
    2. For each deallocated VM, under the Settings pane, click Size and choose a different VM size.
      Select a VM that supports the number of drives you attached to your VM. You will get an error if you select a VM size that supports fewer drives.
    3. Verify all VMs were scaled.
  6. Start the VMs using one of these options.
    Option Actions
    Azure portal Use this option if you have a small number of VMs.
    1. From the Azure portal, locate the Vantage resource group.
    2. Locate each stopped VM and click Start.
    Azure CLI Use this option if you have a large number of VMs. Before proceeding, install the Azure CLI 2.0.
    1. From the CLI command prompt, type the following command:
      az vm start -n -rg
      where:
      • -n is the name of the Azure VM.
      • -rg is the name of the Azure resource group that contains the VM.
    2. Press Enter and repeat these steps until all VMs are started.
  7. Run the following command from a node to update the vconfig as per the new VM SKU:
    tdc-vmresize-update-vconfig
  8. Set pdeconf on using /usr/pde/bin/pdeconf -s autostart=on
  9. Identify any failed AMPs and bring them back online.
    1. From Vproc Manager, type STATUS to identify any failed AMPs.
    2. Type the following to bring each AMP or a set of AMPs online:
      Set ### to ### online, where the first ### is the first AMP number and the second ### is the last AMP number. For example, set 0 to 10 online.
    3. Type QUIT.
    4. From the command line, stop the database.
      # tpareset -x
    5. Confirm the database is down.
      # pdestate -w
      PDE state: DOWN/HARDSTOP
  10. Restart the database.
    # /etc/init.d/tpa start
  11. Confirm the database is running.
    # pdestate -a
    The PDE state should show RUN/STARTED on all VMs. If the PDE state shows DOWN/HARDSTOP, repeat the previous steps for stopping and restarting the database.
    If the PDE continues to show DOWN/HARDSTOP, contact Teradata Services.
  12. From Vproc Manager, type STATUS to confirm all AMPs are ONLINE.
Related information