Inspect retained storage before taking recovery action for a PD MinIO S3 service that has ended. Retention preserves a recovery opportunity only while the required objects still exist.

Establish the original recovery point

Identify the original service, MinIO account, primary and additional buckets. Inspect Retention and Activity, then place the intended purge on Hold while reviewing recovery. Confirm the module state is terminated, not purging or purged, and that the required objects and versions remain stored.

Hold does not undo deletion already performed during a partial purge. An inventory or billing record is not a copy of the missing objects.

Reopen the original retained service

1. Open the original cancelled service in Blesta and use Uncancel with Use module enabled. Changing only the billing record does not reopen its storage.
2. Inspect Activity and Clients & Storage for successful reactivation.
3. Confirm the original buckets are attached and the purge countdown has stopped.
4. Obtain the newly issued service credentials and update applications.
5. Verify the required data, versions and actual read/write access.

The module recognises the original terminated storage and reissues its scoped credentials. A new unrelated order does not automatically adopt the old buckets. Reactivation cannot restore purged objects. Verify which historical versions remain after any independent lifecycle cleanup.

Resolve failures deliberately

Do not create duplicate orders or change internal service records to bypass a failed recovery. Your hosting team’s storage administrator should review the actual retained buckets and required versions. Where a deliberate recovery to a separate destination is appropriate, use your authorised storage recovery process and verify the copy before allowing further purge work. This is separate from asking PD Modules support to investigate a module failure.

Keep host credentials private. Give customer applications only the current service connection details.

Check the recovered service

Your hosting team should compare the original service identity, selected MinIO account, Retention state, saved Hold and original reactivation result with the actual buckets and current service credentials. Your storage administrator must establish which required objects and versions still exist; successful credential reissue is not a file-integrity or historical-version check. If the module reports a failure after changing a credential or policy, inspect the current state before trying again.

See the PD MinIO S3 Blesta guide for related tasks, or explore the module.