Backup and restoration
Database backups can be used to restore data when needed. Availability depends on the deployment environment and organization plan. If the page says that backups are unavailable, ask your administrator which backup options are supported.
Open the backup page
In the console, open your project, select Databases, select a database, and open Backups. Database write permission is required to create backups or policies, delete them, and start a restoration.
Create a backup
Where backups are available, select Create backup and confirm. Backups take time. The list shows the creation time, size, and status; only completed backups can be restored.
For recurring backups, create a policy with an optional name, a required Cron schedule expression, and a retention period. The default expression is 0 0 * * *; confirm the schedule timezone and execution time for your environment. The form rejects an invalid expression or custom retention period; correct the error before submitting. Available options and limits depend on your plan. Deleting a policy also permanently deletes the backups associated with it. Confirm which data must be retained before deletion.
Restore a backup
Select a completed backup and choose Restore. Enter a new database name and either provide a database ID or leave it blank to generate one. After submission, monitor the restoration status. Once it completes, open the new database and check the required tables and data.
The current console restoration form creates a new database; it does not offer an option to overwrite the current database. Duration and availability depend on the environment and data volume; check the task status for the result.
Before you begin
Confirm the organization, project, and database. The page shows policies and backup records for the selected database; a backup from another database is not automatically a recovery point for this one.
If backups are unavailable, ask an administrator to check the deployment and organization plan. If the create button is disabled, also check database write permissions, whether the policy list loaded successfully, and the plan's policy limit. Do not repeatedly submit the same request to test availability.
Agree on a retention period, backup frequency, and recovery target. Follow your organization's change and retention process before restoring or deleting production data.
Manage policies and backup records
A policy schedules future backups. Manual backups use a separate creation entry. The policy list displays its name, enabled status, schedule, and retention period; the backup list shows creation time, size, and status. After an operation, refresh the list or wait for it to update, then inspect the resulting record.
When creating a policy, the name is optional and the Cron schedule expression is required. Its default is 0 0 * * *. To use a different schedule, enter a valid Cron expression and first confirm the timezone used by the deployment. Choose a retention preset or enter a custom count and unit; the page validates the custom value. If the form reports an invalid value, correct the indicated field before submitting again. An error does not mean the policy was saved.
Before deleting a policy, check whether its associated backups must be retained. Deleting the policy also deletes its associated backups and cannot be undone. Follow your team's recovery and retention procedures before making that decision. You can also delete an individual backup from its list; confirm that the recovery point is no longer needed first.
Status and troubleshooting
Why can't I restore a backup immediately after creation?
A completed create request does not mean that the backup is ready for restoration. Check its status in the backup list; the console enables restoration only for a completed backup. If the status does not progress or shows a failure, ask the environment administrator to inspect the backup service and task information. Do not treat a pending backup as a usable recovery point.
How do I confirm a restoration?
After submission, the page shows the restoration task and its status and offers a refresh action. Once the task completes, open the new database and verify the required tables and data. If it fails, preserve the task identifier and error information for the administrator. Confirm the data through application queries and business checks; an accepted request alone is not proof of a successful recovery.
Why is the policy or backup list empty?
First confirm the organization, project, and database, then check the list loading status and permissions. If loading failed, resolve the displayed error or contact an administrator. An empty list describes only the current view; it does not establish the backup state of another project or database.