From 43de598852a92c1d91ceace18bb9e7199527d005 Mon Sep 17 00:00:00 2001
From: Ivan Groenewold <9805809+igroene@users.noreply.github.com>
Date: Wed, 31 Jul 2024 11:35:53 -0300
Subject: [PATCH 1/2] Update physical.md

---
 docs/features/physical.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/features/physical.md b/docs/features/physical.md
index 2f59bce8..885d69ab 100644
--- a/docs/features/physical.md
+++ b/docs/features/physical.md
@@ -7,6 +7,10 @@
 *  Percona Server for MongoDB starting from versions 4.2.15-16, 4.4.6-8, 5.0 and higher. 
 * WiredTiger is used as the storage engine in Percona Server for MongoDB, since physical backups heavily rely on the WiredTiger [`$backupCursor` :octicons-link-external-16:](https://docs.percona.com/percona-server-for-mongodb/6.0/backup-cursor.html) functionality.
 
+!!! warning 
+
+    During the period the backup cursor is open, database checkpoints can be created, but no checkpoints can be deleted. This may result in significant file growth.
+    
 !!! admonition "See also"
 
     Percona Blog

From 61117af49f9932e82495126702a17b47e77e090b Mon Sep 17 00:00:00 2001
From: Ivan Groenewold <9805809+igroene@users.noreply.github.com>
Date: Wed, 31 Jul 2024 11:37:42 -0300
Subject: [PATCH 2/2] Update start-backup.md

---
 docs/usage/start-backup.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/usage/start-backup.md b/docs/usage/start-backup.md
index 1e544d00..a5e34dac 100644
--- a/docs/usage/start-backup.md
+++ b/docs/usage/start-backup.md
@@ -38,7 +38,11 @@
      ```
 
      During a *physical* backup, Percona Backup for MongoDB  copies the contents of the `dbpath` directory (data and metadata files, indexes, journal and logs) from every shard and config server replica set to the backup storage. 
+     
+    !!! warning 
 
+        During the period the backup cursor is open, database checkpoints can be created, but no checkpoints can be deleted. This may result in significant file growth.
+    
      Starting with [2.4.0](../release-notes/2.4.0.md), PBM doesn't stop [point-in-time recovery oplog slicing](../features/point-in-time-recovery.md#oplog-slicing), if it's enabled, but runs it in parallel. This ensures [point-in-time recovery](pitr-tutorial.md) to any timestamp if it takes too long (e.g. hours) to make a backup snapshot.
 
 === ":material-select-multiple: Selective"