Use PD MinIO S3 → Reconcile to compare configured MinIO deployments with the module’s storage-service records. The scan reports differences; it does not adopt, delete or repair the reported resources.

Run and inspect the scan

1. Confirm the intended module accounts are configured.
2. Open Reconcile and run its scan.
3. Check the time, accounts inspected, errors and warnings.
4. Review missing tracked buckets and orphaned buckets separately.
5. Compare each finding with its intended service and deployment before deciding on action.

Orphan reporting is filtered to the module’s naming scope. A similarly named resource is not permission to delete it. An interrupted provisioning operation or changed account relationship can leave a bucket needing investigation.

Distinguish a failed read from absence

A refused or incomplete provider listing cannot prove a bucket is missing. Inspect the named account, result and credential scope before declaring data lost. Have the storage administrator establish actual native state where needed.

Missing-bucket findings check tracked primary buckets; they do not establish that every additional bucket exists. Check required additional buckets separately with your storage administrator.

This MinIO scan does not enumerate native users for stray-credential reconciliation. Do not infer that an unreported user is unused or remove an unfamiliar one on the basis of this bucket scan.

Keep repair separate

Reconcile cannot attach an arbitrary bucket to a new order or recover objects already purged. Retention approval and native administrator changes are separate deliberate workflows.

Retain the service, scan time and exact redacted finding while your hosting team checks its actual deployment. Exclude full account inventories, credentials and object contents. Use provisioning checks when the difference follows an uncertain setup rather than creating another order immediately.

Interpret the scan result

Your hosting team should compare the scan time, intended account, errors/warnings and exact finding with the original service and its actual MinIO deployment. Your storage administrator should distinguish a refused read, an absent primary bucket, an additional bucket and a resource with no known service association. A clean bucket scan is not proof of complete credential or additional-bucket coverage, and a reported orphan is not permission to remove it.

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