Check the backup list that PD DigitalOcean Databases makes available to a customer for a supported database engine and edition. This page is a view, not a self-service restore workflow.

Check the engine and feature switch

The module lists automated backups for Standard Edition PostgreSQL and MySQL when Client: Backups is enabled on the product. It does not offer this client backup list for Advanced Edition, MongoDB, Valkey, Kafka or OpenSearch.

That is a boundary of this module’s client interface. It does not mean every other engine lacks provider-managed backups or recovery facilities.

Open the list

Open the intended database service, then Backups. Review the displayed backup dates and sizes. The Overview page shows only a short preview; use the full page to inspect the returned list.

Compare the entries with the recovery period you need. A backup being listed is not proof that your application data has been restore-tested or that every desired point in time is recoverable.

When the page or entries are missing

If the tab is absent, check the engine, edition and feature switch first. If an expected list is empty, check whether the provider read succeeded: an empty display alone does not prove there are no backups.

Check recovery options separately

For a planned recovery, identify the intended service and required recovery date and timezone. Establish the available recovery option and its impact before making changes. Do not delete or recreate the service to make a backup appear, and do not assume a Backups entry is a restore button.

See the PD DigitalOcean Databases WHMCS guide for related setup, or explore PD DigitalOcean Databases.