Skip to content

Commit 35c00dc

Browse files
committed
Updated after the review
1 parent 4b0824a commit 35c00dc

File tree

2 files changed

+9
-7
lines changed

2 files changed

+9
-7
lines changed

docs/features/split-merge-backup.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
!!! admonition "Version added: [2.11.0](../release-notes/2.11.0.md)
44

5-
As your database grows, so do your backups. Eventually, a backup file may become so large that it exceeds the maximum object size limit of your cloud or local storage. When this happens, Percona Backup for MongoDB (PBM) can't upload the file, which can disrupt your backup strategy.
5+
As your database grows, so do your backups. Eventually, a collection or index may become so large that its backup file exceeds the maximum object size limit of your cloud or local storage. When this happens, Percona Backup for MongoDB (PBM) can't upload the file, which can disrupt your backup strategy.
66

77
The following table provides default size limits for the supported backup storages:
88

@@ -13,7 +13,9 @@ The following table provides default size limits for the supported backup storag
1313
| **Azure Blob Storage** | 190 TB |
1414
| **Filesystem storage** | 4.9 TB |
1515

16-
To ensure that PBM successfully uploads backups, you can configure the maximum size for backup files for the storage you use. Define the file size in GB for the `maxObjSizeGB` configuration parameter.
16+
These defaults are sufficient to satisfy the majority of use cases. However, you can fine-tune the limits and configure a new maximum size for backup files for the storage you use.
17+
18+
To ensure that PBM successfully uploads backups, you can configure the . Define the file size in GB for the `maxObjSizeGB` configuration parameter.
1719

1820
This is the configuration example for the AWS S3 storage:
1921

@@ -27,7 +29,7 @@ storage:
2729
credentials:
2830
access-key-id: <your-access-key-id-here>
2931
secret-access-key: <your-secret-key-here>
30-
maxObjSizeGB: 100
32+
maxObjSizeGB: 5018
3133
```
3234
3335
## How it works

docs/reference/configuration-options.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -249,7 +249,7 @@ The maximum time to wait before the next retry, specified as a *time.Duration*.
249249

250250
### storage.s3.maxObjSizeGB
251251

252-
*Type*: int <br>
252+
*Type*: float64 <br>
253253
*Required*: NO <br>
254254
*Default*: 5018
255255

@@ -344,7 +344,7 @@ Each time PBM fails and tries again, it increases the wait time by multiplying i
344344

345345
### storage.gcs.maxObjSizeGB
346346

347-
*Type*: int <br>
347+
*Type*: float64 <br>
348348
*Required*: NO <br>
349349
*Default*: 5018
350350

@@ -369,7 +369,7 @@ The path to the backup directory
369369

370370
### storage.filesystem.maxObjSizeGB
371371

372-
*Type*: int <br>
372+
*Type*: float64 <br>
373373
*Required*: NO <br>
374374
*Default*: 5018
375375

@@ -427,7 +427,7 @@ Your access key to authorize access to data in your storage account.
427427

428428
### storage.azure.maxObjSizeGB
429429

430-
*Type*: int <br>
430+
*Type*: float64 <br>
431431
*Required*: NO <br>
432432
*Default*: 194560
433433

0 commit comments

Comments
 (0)