PowerProtect Data Manager Deploy
What the Deploy domain covers
The PowerProtect Data Manager Deploy domain tests whether you can plan and stand up a PPDM instance correctly: choosing the form factor, validating vSphere and network prerequisites, sizing the appliance, completing the OVA deployment, performing first-boot configuration, and verifying the deployment before adding protection storage and asset sources. It is not a backup-workflow domain; the focus is the server itself and the dependencies it needs before any protection policy can run.
Core rules and concepts
- Form factor: PPDM is normally deployed as a virtual appliance from an OVA on supported VMware vSphere/ESXi. The DM5500 is a separate prebuilt appliance; do not mix deployment steps.
- Prerequisites: supported vCenter/ESXi version, static IP, FQDN, DNS A and PTR records, NTP, and a service account with the privileges PPDM needs. DHCP is not appropriate for the PPDM server.
- Sizing: use the PPDM sizing guidance based on protected capacity and asset count, not just VM count. Select small, medium, or large; undersizing RAM/CPU causes slow catalog and policy operations.
- Storage: PPDM needs its own datastore capacity; use thick-provisioned disks where required. PPDM is not the backup target - a Data Domain (or supported protection storage) provides capacity.
- First boot: set network, time zone, and admin credentials at the console/OVF customization; then log in to the UI, accept the EULA, apply licensing, configure alerting, and add protection storage and asset sources.
Worked example
A design must protect 400 TB across 800 VMs. The sizing table shows the large size for capacity above 300 TB. Choose large, even though the medium size might cover the VM count alone. During OVA deployment, assign a static IP, create both A and PTR records, point to two NTP servers, and use thick-provisioned disks. After power-on, set the admin password at the console, log in, add the Data Domain as protection storage, then register vCenter as an asset source. Validate by checking DNS resolution, NTP sync, service health, and a test asset discovery.
Traps
- Sizing from VM count only and ignoring protected capacity.
- Using DHCP or omitting the PTR record; both break name resolution and later integrations.
- Deploying with thin disks or on an unsupported vSphere version.
- Forgetting NTP, which causes certificate and authentication errors.
- Treating the DM5500 appliance guide as the OVA deployment procedure.
- Expecting PPDM to store backups locally; it requires protection storage.