Use the original storage service when correcting an accidental cancellation or termination. PD DigitalOcean Spaces can reactivate retained terminated storage while the required buckets and data remain.

Establish whether recovery is still possible

1. Identify the original service and its tracked bucket or buckets.
2. Open PD DigitalOcean Spaces → Retention and put its pending purge on Hold.
3. Review the recorded state and Activity for any purge already started.
4. Establish which required objects and versions remain.
5. Keep any independent recovery copy available before changing service state.

A service already purging or purged is not a retained-data recovery promise. Hold does not reverse deletion. Your hosting team and DigitalOcean administrator should establish the actual retained state before another operation, rather than approving deletion or creating another paid order.

Reactivate the original service

Open the original WHMCS service and use its supported module Create action to reactivate retained terminated storage after checking the service and payment decision. Restore the billing status deliberately as part of the same review; editing the status field alone does not prove module reactivation ran.

Inspect the operation result and Clients & Storage. Reactivation issues fresh service credentials; update the dependent applications with the current full key pair rather than expecting revoked keys to work again.

Verify data and application access

Confirm the original bucket, region and expected data. Test the application’s necessary operations and its recovery path. A successful billing change or an empty current-object view cannot prove every historical version is present.

If reactivation fails, retain the original service, action time, retention state and exact redacted error. Your hosting team should compare that result with the actual retained data, credential and access state before another attempt. Never include secrets or signed object URLs, and do not use a purge as a reset.

Check the recovered service

Your hosting team and DigitalOcean administrator should compare the original service, account/region, saved Hold, current module state and actual retained buckets and required data before another reactivation attempt. Inspect the original Activity result and any changed key or access state; fresh credentials do not establish that every object or version survived.

See the PD DigitalOcean Spaces WHMCS guide for related tasks, or explore the module.