| copyright |
|
||
|---|---|---|---|
| lastupdated | 2026-03-10 | ||
| keywords | backups, new service instance, deleted resource, undelete, pending backup | ||
| subcollection | cloud-databases |
{{site.data.keyword.attribute-definition-list}}
{: #faq-backups} {: faq} {: support}
{: #faq-backups-data-deletion} {: faq} {: support}
If an instance is deleted, the backup is deleted as well. However, {{site.data.keyword.databases-for}} waits for 3 days before it is deleted internally. Within those 3 days, you can either re-enable the instance or create a new service instance from the backup. For more information, see Deleting your Deployment and Removing your Data. You can also use {{site.data.keyword.cloud_notm}} CLI or API to restore a deleted resource. For more information, see Using resource reclamations{: external}.
{: #faq-backups-restore-new-instance} {: faq} {: support}
{{site.data.keyword.databases-for}} backups are restored in a new service instance. For more information, see Managing {{site.data.keyword.databases-for}} backups.
Point-in-Time Recovery (PITR) is available for {{site.data.keyword.databases-for-mysql}}{: external}, {{site.data.keyword.databases-for-postgresql}}{: external}, {{site.data.keyword.databases-for-mongodb}}{: external} and
{: #faq-backups-pending-backup} {: faq} {: support}
{{site.data.keyword.databases-for}} does not create additional backups if there is already a pending backup in the queue, ensuring efficiency and avoiding redundancy in our backup processes. {{site.data.keyword.databases-for}} automatically schedules a new daily backup if none is currently set up. You have the flexibility to initiate manual backups at your preferred cadence.
{: #use-terraform-ibm-modules} {: faq} {: support}
Yes, you can use Terraform IBM Modules (TIM) to create a new database instance from a backup instance. Terraform IBM Modules are pre-built, validated, and enterprise-ready modules that follow IBM Cloud best practices. For more information, see Restore from backup example{: external}.