Dell PPDM Deploy key terms

A software-defined data protection platform that discovers assets, applies protection policies, and orchestrates backups and restores across virtual machines, databases, file systems, and Kubernetes workloads from a single management interface.

A pre-packaged deployment form of the platform delivered as a validated appliance image, removing the need to install the operating system and application separately on customer-provided infrastructure.

The core node that hosts the management services, policy engine, catalog, and user interface, coordinating all protection activity and communicating with agents and storage targets.

The arrangement of Data Manager nodes, storage systems, and protected assets, chosen to meet scale, availability, and network segmentation requirements during installation planning.

A configuration in which multiple Data Manager nodes act together so that protection services continue if one node fails, typically paired with a load balancer and shared storage.

The process by which standby components take over the workload of a failed primary component, preserving protection schedules and management access with minimal interruption.

An individual member of a multi-node Data Manager deployment that shares configuration and state with its peers so that the cluster behaves as one logical system.

A network device or service that distributes management and agent traffic across Data Manager nodes, providing a single stable address for users and protected clients.

A registered system or platform from which Data Manager discovers protectable objects, such as a vCenter server, Kubernetes cluster, or database host.

The scheduled or on-demand process of scanning an asset source to enumerate the virtual machines, databases, or namespaces that can be protected, keeping inventory current.

A user-defined collection of discovered assets that can be targeted by a single protection policy, simplifying administration when many objects share the same requirements.

A rule set that binds assets to a schedule, retention period, storage target, and optional replication or cloud tiering, determining how and where their backups are created.

The component of a protection policy that defines backup frequency, start time, retention duration, and the storage unit receiving the copies.

The configured backup destination, such as a PowerProtect DD system, that receives copies created by protection policies and stores them under Data Manager control.

A logical partition of protection storage with its own quota and credentials, used to isolate backup data belonging to different policies or tenants.

A protocol and client library that lets backup software send deduplicated data directly to PowerProtect DD storage, reducing network load and improving throughput.

Dell's deduplicating storage product line used as primary protection storage, frequently referenced by its current branding PowerProtect DD in deployment documentation.

Software installed on a protected host that coordinates with native application interfaces to quiesce, back up, and restore databases or file systems consistently.

The mechanism by which application agents register themselves with Data Manager, enabling policy-driven, centrally managed backups instead of per-host scheduling.

A hypervisor-level snapshot taken during a virtual machine backup that briefly preserves a consistent state so data can be read without disrupting the running guest.

A governance control that prevents backup copies from being deleted or modified before their retention period expires, supporting compliance and protection against ransomware.

A backup copy written in a form that cannot be altered or removed for a defined period, typically enforced by protection storage rather than by the backup application alone.

An optional long-term retention layer that moves older backups from primary protection storage to object storage, lowering cost while keeping copies recallable.

The copying of backup data from one protection storage system to another, often at a remote site, to provide disaster recovery and an additional copy for retention.

The planned ability to restore protection services and data at an alternate location after a site-level failure, relying on replicated copies and documented recovery procedures.

The indexing component that catalogs backup metadata so administrators can search for and restore individual files or messages without scanning entire backup images.

The process of extracting and storing metadata from backup content, enabling fast file-level search and granular restore operations across large environments.

The operation of returning protected data to its original location or an alternate target, ranging from a full system recovery to a single file or mailbox item.

A capability that presents a backup copy as a live datastore or volume so virtual machines can be powered on almost immediately while data is copied in the background.

The practice of separating management, backup data, and replication traffic onto distinct networks or VLANs so that each path meets its own security and bandwidth needs.

The documented set of ports and protocols that must be open between Data Manager, agents, asset sources, and storage so that discovery, backup, and restore traffic flows.

Keeping clocks aligned across Data Manager, agents, and storage using a common time source, which is necessary for authentication, scheduling, and consistent log correlation.

The installation, replacement, and renewal of TLS certificates used by Data Manager services and its clients to authenticate endpoints and encrypt management traffic.

A permission model that assigns users predefined roles such as administrator, backup operator, or restore operator, limiting each account to the actions its role allows.

An external directory or single sign-on service that Data Manager can use to authenticate users and map their group memberships to local roles.

A record of administrative and user actions within the system, retained to support troubleshooting, compliance review, and accountability for configuration changes.

Continuous checking of Data Manager components, agents, and storage connectivity that surfaces alerts and service states so problems are found before backups fail.

The configuration that sends system events and failures to email recipients or an SNMP manager so operations staff can respond without watching the console.

A validation step run before applying a new software version that verifies component health, compatibility, and free capacity, flagging conditions that would block the upgrade.