Skip to content

Adding Backup Size Requirement #10558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OlufunkeMoronfolu merged 2 commits into from
Jan 9, 2026
Merged

Adding Backup Size Requirement #10558

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4a49e8c
Adding Backup Size Requirement
OlufunkeMoronfolu Jan 7, 2026
9af06f1
Updating DB size with overhead info
OlufunkeMoronfolu Jan 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ You cannot transfer data from one app to another by restoring a backup from one

If the database in your plan is not large enough to contain all the restored data, the restore operation will fail. This leaves the database only partially restored. If this occurs, you will need to upgrade your plan to increase the database size or restore a smaller database to ensure that the database is complete.

Your database must be large enough to hold the decompressed size of the database as stored in the [db folder](#db-folder) of your backup file, plus an overhead of 2.25 GB used during the restoration process. The decompressed database size can be determined by [restoring the backup locally](/developerportal/operate/restore-backup-locally/) and using the pgAdmin statistics page.
Your database must be large enough to hold the decompressed size of the database as stored in the [db folder](#db-folder) of your backup file, plus approximately 30% additional space for overhead during the restoration process. You can determine the decompressed database size by [restoring the backup locally](/developerportal/operate/restore-backup-locally/) and checking the pgAdmin statistics page.

Contact [Mendix Support](https://support.mendix.com/) if you need further assistance.

Expand Down Expand Up @@ -93,15 +93,15 @@ If the app is still running, you have to stop it by clicking **Stop Application*

## Restoring After a Backup Fails{#restore-after-fail}

If a backup restore fails, the failure is logged in your app's **Backup Activity** log, which you can view on the **Backups** page when you open your app in [Apps](https://sprintr.home.mendix.com/). If this happens, only data that was restored until the point of failure will be present in your database, leaving the database only partially restored.
If a backup restore fails, the failure is logged in your app's **Backup Activity** log, which you can view on the **Backups** page when you open your [app](https://sprintr.home.mendix.com/). If this happens, only the data restored up to the point of failure will be present in your database, leaving it partially restored.

Your database must be large enough to hold the decompressed size of the database as stored in your backup file's [db folder](#db-folder), plus additional free space for overhead during the restoration process. For example, if you run your app in an S21 Cloud Resource Pack, then your database size is 10 GB. To restore a backup, the size of your decompressed database in the **db** folder must not exceed 7.75 GB to allow for 2.25 GB of overhead.
To ensure a successful restore, Mendix recommends that your database is large enough to hold the decompressed size of the database as stored in your backup file's [db folder](#db-folder), plus additional free space substantially exceeding this decompressed size to allow for overhead during the restoration process.

While a minimum of 2.25 GB is often sufficient for smaller backups, the actual required free space varies significantly based on the backup's size. To ensure a successful restore, Mendix recommends that your database has free space substantially exceeding the decompressed backup size to accommodate the restoration process. For more information on the resource pack sizes Mendix offers, see [Cloud Resource Packs](/developerportal/deploy/mendix-cloud-deploy/#resource-pack).
For example, when restoring any app running in any of the available Mendix [Cloud Resource Packs](/developerportal/deploy/mendix-cloud-deploy/#resource-pack), the decompressed database in the **db** folder should not exceed 70% of the database size, reserving approximately 30% for overhead during restore.

In the event that a backup restore fails in this way, you will need to retry the backup restore. Before you retry, ensure your database meets the size requirements detailed above.
If a backup restore fails, you will need to retry the restore. Before retrying, make sure your database meets the size requirements detailed above.

Contact [Mendix Support](https://support.mendix.com/) if you need further assistance with this issue.
Contact [Mendix Support](https://support.mendix.com/) if you need further assistance.

## Format of a Backup File{#format-of-backup-file}

Expand Down