I85PREP
⌘ K
Dell PowerProtect DD Deploy 2023 study materials
Dell PowerProtect DD Deploy 2023 study resources

Dell PowerProtect DD Deploy 2023: Data Protection Protocols and Client Integration

Dell PowerProtect DD Deploy 2023 · Work through your exam, one topic at a time.

All guide sections

Data Protection Protocols and Client Integration

What this domain covers

The protocols domain checks that you can select the right ingest method for a workload and sequence the client-side pieces so the first backup succeeds - storage unit, user role, export or share, plug-in.

Protocol selection

  • DD Boost over IP - the default for enterprise backup applications: distributed segment processing (client-side dedupe), in-flight encryption, load balancing across links, and managed file replication.
  • DD Boost over Fibre Channel - same feature set over FC for SAN-attached media servers; requires zoning and DD Boost enabled on the FC ports.
  • DD BoostFS - a Linux mount that gives applications a file system view while keeping DD Boost dedupe.
  • NFS - export an MTree (nfs add export /data/col1/<name> <host>(rw,no_root_squash)), commonly NFSv3 for backup targets.
  • CIFS/SMB - cifs setup joins Active Directory, then shares are created on MTrees; disable SMB1 for security.
  • VTL - emulated tape drives and libraries over FC or iSCSI for legacy backup software.
  • NDMP - accelerates NAS file-server backups, either two-way or three-way depending on topology.

Client integration sequence (DD Boost)

  1. Create or reuse an MTree for the workload.
  2. ddboost enable if it is not already on.
  3. Create a DD Boost user and assign the DD Boost role - a storage unit alone is not enough.
  4. ddboost storage-unit create <su> user <user>.
  5. Install the DD Boost plug-in or library on the media server, point the backup job at the storage unit, and confirm the job reports a reduction ratio.

Worked example

An Oracle RMAN backup fails with an authentication error after the storage unit was created. Reasoning: RMAN authenticates as a DD Boost user, and the account used for the job was never granted the DD Boost role. The corrected order is user, role, storage unit, then the SBT_LIBRARY pointing at the DD Boost library on the media server. Once the role is assigned, the same job connects and dedupe statistics appear.

Retention and encryption services

  • Retention Lock Governance can be reverted by an admin; Compliance cannot be shortened or removed once set. Both require correct time synchronisation, and the minimum retention period applies to the MTree.
  • DD Encryption is enabled system-wide at the file system level and must match across replication peers.

Traps that cost marks

  • Creating a storage unit but never assigning the DD Boost role.
  • A CIFS join failing because DNS reverse lookup or time skew is wrong.
  • NFS exports that root-squash the backup account, causing permission denials on writes.
  • Mixing retention-locked and ordinary data in one MTree, or expecting a compliance lock to be reversible.