Skip to content

Commit 6e7814b

Browse files
Merge pull request #10558 from mendix/olu-restore-size
Adding Backup Size Requirement
2 parents d222405 + 9af06f1 commit 6e7814b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ You cannot transfer data from one app to another by restoring a backup from one
2828

2929
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.
3030

31-
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.
31+
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.
3232

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

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

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

96-
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.
96+
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.
9797

98-
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.
98+
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.
9999

100-
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).
100+
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.
101101

102-
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.
102+
If a backup restore fails, you will need to retry the restore. Before retrying, make sure your database meets the size requirements detailed above.
103103

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

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

0 commit comments

Comments
 (0)