---
name: cloud-databases-backups-faq
title: Backups FAQ
description: If an instance is deleted, the backup is deleted as well. However, Cloud Databases 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 IBM Cloud CLI or API to restore a deleted resource. For more information, see Using resource reclamations.
last-updated: 2026-03-10
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cloud-databases?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Backups FAQ
{: #faq-backups}
{: faq}
{: support}

## What happens to the backups if I accidentally delete an instance?
{: #faq-backups-data-deletion}
{: faq}
{: support}

If an instance is deleted, the backup is deleted as well. However, Cloud Databases 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](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-deprovisioning&format=markdown). You can also use IBM Cloud CLI or API to restore a deleted resource. For more information, see [Using resource reclamations](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation&format=markdown){: external}.

## Is it possible to restore an instance from a backup in a different instance?
{: #faq-backups-restore-new-instance}
{: faq}
{: support}

Cloud Databases backups are restored in a new service instance. For more information, see [Managing Cloud Databases backups](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-dashboard-backups&format=markdown).

Point-in-Time Recovery (PITR) is available for [Databases for MySQL](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-pitr&format=markdown){: external}, [Databases for PostgreSQL](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr&format=markdown){: external}, [Databases for MongoDB](https://cloud.ibm.com/docs/databases-for-mongodb?topic=databases-for-mongodb-pitr&format=markdown){: external} and

## Can I create a backup while another backup is pending?
{: #faq-backups-pending-backup}
{: faq}
{: support}

Cloud Databases does not create additional backups if there is already a pending backup in the queue, ensuring efficiency and avoiding redundancy in our backup processes. Cloud Databases automatically schedules a new daily backup if none is currently set up. You have the flexibility to initiate manual backups at your preferred cadence.


## Can I use Terraform IBM Modules to provision a new database instance from a backup instance ?
{: #use-terraform-ibm-modules}
{: faq}
{: support}

Yes, you can use [Terraform IBM Modules (TIM)](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-about-tim&format=markdown) 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](https://registry.terraform.io/modules/terraform-ibm-modules/icd-postgresql/ibm/latest/examples/backup){: external}.