Home > Data Protection > PowerProtect Data Manager > Dell PowerProtect Data Manager: Deployment Best Practices > Planning VMware vCenter resources
The following table outlines the minimum resource requirements to deploy a PowerProtect Data Manager OVA in VMware vSphere 6.7 U3 and later:
Specification | Value |
CPU | 10 CPU cores |
Memory | 36 GB RAM |
Disk |
|
Virtual Disk Format | Thick provision lazy zeroed |
Network interface card (NIC) | 1 GB |
Internet Protocol | IPv4 only or IPv6 only |
For application-aware backup on VM |
|
For Cloud DR |
|
The PowerProtect Search Engine enables backup administrators to quickly search and restore VM file copies. The Search Service can be enabled by adding a search node to the configurable Search Engine that is auto deployed during PowerProtect Data Manager installation.
The PowerProtect Search Engine indexes virtual machine file metadata to enable searches based on configurable parameters. To use this feature, add at least one search engine node to the Search Engine to form a search cluster. Adding a node enables the indexing feature.
Each search engine node must meet the following system requirements:
Specification | Value |
CPU | 4 vCPU * 2 GHz (4 virtual sockets, 1 core for each socket) |
Memory | 8 GB RAM |
Disk |
|
Internet Protocol | IPv4 only or IPv6 only |
Network interface card (NIC) | One vmxnet3 NIC with one port |
Note: You can add up to a maximum of five search engine nodes for a single PowerProtect Data Manager. One search node can index a maximum of one billion files or 1,000 virtual machines.
PowerProtect Data Manager comes prebundled with an embedded VM Direct Engine. The engine is automatically used as a fallback proxy for performing backup and restore operations when the added external proxies fail or are disabled. The VM Direct Engine facilitates data movement for both virtual machine protection policies and Kubernetes cluster protection policies.
Dell Technologies recommends that you always deploy an external protection engine, also known as a VM proxy, because the embedded proxy has limited capacity for performing parallel backups. The following table details the requirements for the external VM Direct Engine:
Specification | Value |
CPU | 4 vCPU * 2 GHz (4 virtual sockets, 1 core for each socket) |
Memory | 8 GB RAM |
Disk | Disk 1: 59 GB Disk 2: 98 GB |
Internet Protocol | IPv4 only or IPv6 only |
Network interface card (NIC) | One vmxnet3 NIC with one port |
SCSI controller | 4 (maximum) |
Notes:
Some best practices: