Physical Storage Considerations | Teradata Vantage on VMware - Physical Storage Considerations - Teradata Vantage on VMware

Teradata Vantageā„¢ on VMware Base, Advanced, Enterprise Tiers Getting Started Guide

Product
Teradata Vantage on VMware
Release Number
Deployer 3.04
Published
October 2021
Language
English (United States)
Last Update
2021-10-29
dita:mapPath
qbi1545241606156.ditamap
dita:ditavalPath
lyx1526581533412.ditaval
dita:id
B035-5958
Product Category
Cloud

Vantage on VMware supports both local storage and shared storage (SAN or NAS). The difference between the two is that local storage provides higher performance while shared storage provides higher flexibility.

Local Storage

For performance and system up-time reasons, each Vantage system virtual disk should reside on a RAID-1 pair of physical disks. Common vSphere storage device configurations can use local storage or direct attached storage (for example, JBOD, RBOD).

Shared Storage

If you are using external storage, such as a disk array, consider the performance and data redundancy implications. The preferred configuration for shared storage is one pDisk (VMDK) per LUN. TPA vnodes have three database system pdisks which will be deployed as separate VMware VMDK files.

All TPA pdisks (.vmdk files) may be deployed to a common datastore by modifying the uniqueDisks property in the common.IT.properties.json file from the default of TRUE to FALSE.

Setting it to false may be useful when you have only a single large datastore. Determine the performance and data redundancy implications when using different RAID configurations, external versus internal storage.