The minimum requirements for hardware, Teradata software, and virtualization software are described in the table below. If you want to deploy a Server Management VM, you must have a valid Site ID. For assistance, contact Teradata Customer Support.
| Component | Minimum Requirements (unless noted) | |
|---|---|---|
| Teradata licensing | A Teradata license is required and this guide provides the information you need to deploy the Teradata Database Base, Advanced, or Enterprise database license tiers. For general licensing information, see the Teradata Entitlement Management System (EMS) Customer User Guide. For sites with Internet access, port 443 must be open to connect to the Teradata EMS server to successfully deploy Teradata Database on VMware.
|
|
| vCPU |
|
|
| Memory |
|
|
| Datastores for database storage | Recommended: 24 internal HDDs configured in RAID-1, equating to a total of 12 LUNs, sized according to specifications. Each datastore should correspond to a single RAID-1 HDD. You can also deploy on a large storage area network that is sufficient for your needs, but it is not optimal for the best performance. | |
| Datastore formatting | VMFS 5 file system | |
| Datastore space for template deployment | Total size of all drives in each image:
|
|
| RAID | RAID-1 LUNs recommended. We suggest a configuration of 1 LUN used exclusively for each of the 12 datastores used for database storage, and the thirteenth datastore reserved for the deployment of Teradata Database operating system, Teradata Viewpoint, DSC, Teradata Ecosystem Manager, and Server Management. For more information, see Physical Storage Considerations. |
|
| Server | Dell PowerEdge R720xd/R730xd, or an HP Gen9 or similar system. Hyper-threading (HT) must be enabled. |
|
| Network |
|
|
| VM deployment sizes |
|
|
| VMware ESXi | ESXi 5.5 release 2 and later | |
| VMware licensing | A full VMware vSphere 6.0 license or VMware vSphere Essentials 6.0 license for at least one physical CPU (unlimited cores per CPU) | |
| VMware vCenter | vCenter 5.5 release 2 and later | |
| VMware vSphere Client |
|
|
| VMware vSphere vSwitches |
If all the vNodes are within the same pNode, no physical adapters need to be attached to the vSphere standard vSwitch. If there are any physical adapters attached to the vSphere standard vSwitch, ensure they are cabled correctly. For more information on virtual switches, see Networking Considerations. |
|
| Physical Switches | Physical switches are required to use Jumbo Frame (MTU 9000) for the BYNET and Teradata DSC private network or file transfer issues will occur when configuring the Teradata Database. | |
| PowerCLI |
|
|
Following is an example of a minimum (2 or more) pNode configuration:
- CPU: 2 physical CPUs with 8 to 12 physical cores each for a total of 32 to 48 virtual cores per physical node
- Memory: 256GB
- Network:
- BYNET: Two 10 GB networks to support redundancy
- Server Management: Two 10 GB 1 GB separate (isolated) physical networks for CMIC connectivity
- DSC: 10 GB separate network
- Storage: 26 internal drives of 1.2TB each with RAID-1 pairs yielding 13 ESXi datastores (1 for operating system images, 1 for the operating system installation datastore and 12 for database storage).
If you are using external storage or not using RAID-1, see Physical Storage Considerations.