Changed wording for unsharding a collection

percona · Oct 1, 2024 · c2d833f · c2d833f
1 parent 1a6f276
commit c2d833f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 5 deletions.
diff --git a/docs/features/point-in-time-recovery.md b/docs/features/point-in-time-recovery.md
@@ -54,9 +54,9 @@ If you just enabled point-in-time recovery, it requires 10 minutes for the first
 
     If you [reshard :octicons-link-external-16:](https://www.mongodb.com/docs/manual/core/sharding-reshard-a-collection/) a collection, make a fresh backup and re-enable point-in-time recovery oplog slicing to prevent data inconsistency and restore failure.
 
-    **For MongoDB 8.0**
+    **For MongoDB 8.0 and higher versions**
 
-    Oplog slicing is not supported during the [unshardCollection :octicons-link-external-16:](https://www.mongodb.com/docs/v8.0/reference/command/unshardCollection/) operation.
+    If you [unshard a collection :octicons-link-external-16:](https://www.mongodb.com/docs/v8.0/reference/command/unshardCollection/), make a fresh backup and re-enable point-in-time recovery oplog slicing to prevent data inconsistency and restore failure.
 
 Starting with version [2.4.0](../release-notes/2.4.0.md), oplog slicing runs as follows:
 

diff --git a/docs/usage/start-backup.md b/docs/usage/start-backup.md
@@ -153,9 +153,8 @@ The following diagram illustrates the backup flow.
 
 !!! important
 
-    If you reshard a collection in MongoDB 5.0 and higher versions, make a fresh backup to prevent data inconsistency and restore failure.
-
-    Note that oplog slices are not saved when you unshard a collection. 
+    If you reshard a collection in MongoDB 5.0 and higher versions or unshard a collection in MongoDB 8.0 and higher versions, make a fresh backup to prevent data inconsistency and restore failure.
+
 
 ### Adjust node priority for backups