Scaling a VM Up or Down - Teradata Software for Azure

Teradata Vantage™ on Azure (DIY) Installation and Administration Guide

Product

Teradata Vantage on Azure

Release Number

5.01

Published

July 2018

Language

English (United States)

Last Update

2018-07-18

dita:mapPath

kmk1523992471627.ditamap

dita:ditavalPath

TeradataAzure_PubCloud_5.01_5.01.01.ditaval

dita:id

B035-2810

lifecycle

Product Category

Cloud

Before starting, ask your Azure administrator to grant you access to the Contributor role.

You must stop a VM before you can change the VM size. You should scale up or scale down only supported VM sizes.

Scaling unsupported VM sizes up or down may impact database performance. Data loss will occur if scaling local storage VM sizes.

Scaling up or down has no effect on Teradata software that is running on a VM and is not supported for BYOL in the Azure cloud. See Azure Documentation Center.

Stop the database.
```
# tpareset -x stop system
```
Putting the database in this state may take a few minutes.
Wait for the database to shut down.
```
# psh pdestate -w
```
PDE State: DOWN/HARDSTOP
From the Azure portal, stop all VMs. Clicking Stop stops and deallocates only one VM. Make sure you stop each and every VM.
Resize the VMs. Before proceeding, check that all VMs are stopped and deallocated.
1. From the Azure portal, locate the Teradata Database resource group.
2. Under the Settings pane, click Size and choose a VM size. Select only supported VM sizes. Also select a VM that supports the amount of drives you attached to your VM. You will get an error if you select a VM size that supports fewer drives.
3. Repeat step b for all deallocated VMs.
4. Recheck that all VMs were resized.

Start the VMs.

Option	Actions
Using the Azure portal	Use this option if you have a small number of VMs. From the Azure portal, locate the Teradata Database resource group. Locate the first VM and click Start. Repeat step b until all VMs are started.
Using Azure CLI 2.0	Use this option if you have a large number of VMs. Before proceeding, install the Azure CLI 2.0. From the Azure CLI command prompt, enter the following: 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. Press Enter. Repeat steps a and b until all VMs are started.

Confirm your system is running.
```
# psh pdestate -a
```
If the PDE state shows RUN/STARTED on all VMs, you successfully resized all VMs and can skip the remaining steps. If the PDE state shows DOWN/HARDSTOP on any VM, continue to the next step.
From the command line, identify and connect to any VM in a RUN/STARTED state. If there are no VMs in a RUN/STARTED state, contact Teradata Customer Support for assistance and skip the remaining steps.
Using a combination of Vproc Manager and the command line, complete the following steps. See Utilities.
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. Repeat step b to bring each AMP online.
4. Type QUIT.
5. From the command line, stop the database.
```
# tpareset -x
```
  Putting the database in this state may take a few minutes.
6. Verify the database is shut down.
```
# psh pdestate -a
```
7. Restart the database.
```
# /etc/init.d/tpa start
```
8. Verify the database is started.
```
# psh pdestate -a
```
  The PDE state should show RUN/STARTED on all VMs. If it does not, proceed to step 8j.
9. From Vproc Manager, type STATUS to verify all AMPs are ONLINE.
10. If the PDE state shows DOWN/HARDSTOP, repeat the steps starting with step 8e. If the PDE still shows DOWN/HARDSTOP after performing this step, contact Teradata Customer Support for assistance.