Skip to content

Commit 4a58295

Browse files
Update backup-selective.md
1 parent 0b3ea71 commit 4a58295

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/usage/backup-selective.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,13 +68,13 @@ This command backs up all collections in the **invoices** database along with it
6868

6969
### Use cases
7070

71-
=== "Split/partial Migration of a single database"
71+
=== "Partial Migration for a database"
7272
Organizations often start with a shared cluster hosting multiple databases for different services. Over time, scaling, performance, or compliance needs may require isolating one database into its own dedicated cluster.
7373

7474
=== "Roll back access control changes"
7575
A recent modification to custom roles in `mydb` introduced permission failures. Applications that rely on those roles can no longer perform required operations. To ensure full recovery, you need to restore not just the data but also the users and roles tied to the database’s access-control.
7676

77-
=== "Staging/test environment"
77+
=== "Staging environment"
7878
You need a production-like copy of `mydb` in a separate environment to reproduce issues, validate fixes, or conduct testing.
7979

8080
By backing up mydb together with its users and roles, the copy reflects not only the data but also the access-control model. This enables accurate reproduction of permission-related behavior such as read/write restrictions, role grants, and user privileges.

0 commit comments

Comments
 (0)