Storage / Backup / Procurement / RFQ / Retention / Licensing

PowerProtect DD: Freeze Retention TB?

Appliance quotes without usable retention TB and DD Boost years fail backup windows. Freeze ingest, Cloud Tier, shelves, and ATP on one Data Domain RFQ.

Quick Take

Quick Take: PowerProtect DD RFQs fail when retention and DD Boost are “TBD.” Freeze usable retention TB, ingest window, Cloud Tier scope, expansion shelves, and support years. Demand dated ATP for the appliance and entitlements together. BENQUAN GLOBAL LIMITED supplies DD packages.

When a DD Retention Checklist Matters

Quick Answer: Use this when buying or expanding PowerProtect DD, dual-quoting StoreOnce, or renewing backup targets under tighter retention. Also use it when finance approved the appliance but licenses, shelves, and Cloud Tier were left as follow-on POs — that pattern quietly breaks ingest windows and ATP leverage.

Threads titled “DD quote ready” rarely fail on chassis stickers — they fail when usable retention was never frozen, or when DD Boost and Cloud Tier entitlements arrive after the backup window is already live.
TB
Usable Retention
Boost
+ Cloud Tier
Shelf
Expansion Lines
ATP
Same Go-Live

Architecture Fork — Appliance vs License Risk

Quick Answer: Appliance design locks controller class and shelf count. License design locks DD Boost, Cloud Tier, replication, and support years. Treat them as two risk tracks under one RFQ — chassis ATP without entitlement ATP is still a half-complete PO that fails the first full backup week.

Track What you freeze Common miss
Appliance Controller SKU, shelves Chassis-only quote
Retention Usable TB + days Raw marketing capacity
Licenses Boost, Cloud Tier, years “Licenses TBD later”
Network 10/25/100G ports, optics Optics after cutover
ATP Dated ship all tracks Box lands; Boost waits

Naming traps

PowerProtect DD, legacy Data Domain nicknames, and DDVE are not one CapEx pool. Do not peer a shelf-expanded physical appliance to a virtual instance without rewriting usable TB, Boost licensing, and Cloud Tier assumptions on the RFQ.

Peer & Capacity Mapping (Intent, Not Nicknames)

Quick Answer: Map by retention intent carefully. Mid-size backup targets often dual-quote DD and StoreOnce Gen4+; cyber-isolated vaults may add a second site line. Confirm usable TB, ingest TB/hr, and cloud offload before ranking vendors on appliance stickers alone across unequal briefs.

Intent Typical DD path License note
Primary dedupe target Physical DD + shelves Boost + support years
Cloud offload DD + Cloud Tier Cloud Tier entitlement
Dual-vendor RFP DD vs StoreOnce columns Equal retention days
Software-heavy estate Keep Rubrik adjacency separate Do not mix BOM lines

License & Retention Matrix (Put Counts on the RFQ)

Quick Answer: Classify every capacity and license line before ranking CapEx. Usable retention TB, DD Boost, Cloud Tier, shelves, and support years belong on the brief. Wrong retention math wastes negotiation time and fakes a cheaper target until the first full retention cycle fails.

Line Prefer RFQ fields
Retention Usable TB after defended dedupe Days, daily ingest FE
DD Boost Required for ISV path Term years, host count notes
Cloud Tier If offload is in design Entitlement + object store note
Shelves / support Matched to growth plan SKU qty, support years

Usable TB is a written assumption

Do not accept raw marketing capacity as retention. State front-end daily ingest, retention days, and the dedupe ratio you will defend — then dual-quote StoreOnce on the same numbers via the DD vs StoreOnce guide.

Sizing Truth — Equal Assumptions

Quick Answer: Force equal usable retention TB, ingest windows, Cloud Tier scope, license years, and optics on every vendor column. If one quote includes Boost and shelves and another is bare chassis, stop ranking platforms immediately — fix the backup brief first, then re-quote.

  • Ingest window: TB/hr and backup start time change controller class more than stickers.
  • Retention days: compliance calendars dominate shelf count.
  • Licenses: Boost and Cloud Tier must year-match support terms.
  • Lead time: shelf and entitlement queues can exceed appliance ATP — shared go-live gate.
If the appliance is PO’d this week and DD Boost or Cloud Tier is “to follow,” treat that as a red flag. Align ATP dates or move the first full backup — do not hope entitlements clear after crates land.

RFQ Checklist — Retention + Licenses on One Brief

Quick Answer: One backup brief → DD appliance + shelves → usable retention TB → DD Boost / Cloud Tier years → optics → optional StoreOnce column → dated ATP. Optional Rubrik adjacency is fine only when those lines stay separate from the dedupe-target BOM.

What to put on the RFQ

  • Daily front-end ingest TB and backup window hours
  • Retention days and usable retention TB target
  • Defended dedupe / reduction assumption (written)
  • Exact PowerProtect DD controller SKU + shelf qty
  • DD Boost entitlement term years
  • Cloud Tier yes/no + entitlement years if yes
  • Replication / Cyber Recovery notes if in scope
  • Network ports + optics/DAC spare %
  • Support / ProSupport term years matched to licenses
  • Optional StoreOnce column with equal retention and ingest
  • Dated ATP for appliance, shelves, and entitlements vs one go-live

Use SKU Lookup, then submit the retention brief on rfq.html.

Frequently Asked Questions

Quick Answer: Missing Boost and retention honesty stall backup cutovers more often than chassis gaps on the critical path. Write usable TB and license years up front, itemize Cloud Tier and shelves, and demand dated ATP for appliance and entitlements on the same go-live before CapEx locks.

DD Boost, Cloud Tier, and shelves often trail the chassis. Appliance-only POs look done until retention or ingest features are incomplete. RFQ usable TB, licenses, and ATP together.

Usable retention TB after a defended dedupe assumption — not raw marketing capacity. State daily front-end ingest, retention days, and Cloud Tier offload separately.

Yes when dual-vendor is required. Equalize usable retention, ingest window, cloud tier, and license years before ranking. See the DD vs StoreOnce buying guide.

Submit one RFQ with retention TB, ingest window, license years, and go-live.

Key Takeaway

Key Takeaway: Freeze usable retention TB behind a written dedupe assumption, daily ingest and window hours, and retention days before pricing controllers. Put DD Boost and Cloud Tier years, shelf quantities, and optics on one dated ATP gate with the chassis — entitlements that trail crates fail the first full backup. BENQUAN supplies Dell PowerProtect DD with competitive pricing.

Not sure your PowerProtect DD BOM is optimal?

If usable retention TB, DD Boost/Cloud Tier years, shelf growth, or ATP alignment are unclear, click below for a free compatibility and delivery risk assessment. Fast global BOM validation and risk assessment.

Free Compatibility & Delivery Risk Assessment

Or call +852-21349834 · info@benquan.hk

Contents