Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update restore.md #230

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Update restore.md #230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions docs/usage/restore.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,8 @@ To restore a backup, use the [`pbm restore`](../reference/pbm-commands.md#pbm-re

After the restore is complete, do the following:

1. Restart all `mongod` nodes.
1. Remove the contents of the datadir on any arbiter nodes
2. Restart all `mongod` nodes

!!! note

Expand All @@ -207,18 +208,18 @@ To restore a backup, use the [`pbm restore`](../reference/pbm-commands.md#pbm-re

This is expected behavior of periodic checks upon the database start. During the restore, the `config.system.sessions` collection is dropped but Percona Server for MongoDB recreates it eventually. It is a normal procedure. No action is required from your end.

2. Restart all `pbm-agents`
3. Restart all `pbm-agents`

3. Run the following command to resync the backup list with the storage:
4. Run the following command to resync the backup list with the storage:

```{.bash data-prompt="$"}
$ pbm config --force-resync
```

4. Start the balancer and start `mongos` nodes.
5. Start the balancer and start `mongos` nodes.

5. We recommend to make a fresh backup to serve as the new base for future restores.
6. [Enable point-in-time recovery](../features/point-in-time-recovery.md#enable-point-in-time-recovery) if required.
6. We recommend to make a fresh backup to serve as the new base for future restores
7. [Enable point-in-time recovery](../features/point-in-time-recovery.md#enable-point-in-time-recovery) if required


### Define a `mongod` binary location
Expand All @@ -240,7 +241,8 @@ To restore a backup, use the [`pbm restore`](../reference/pbm-commands.md#pbm-re
"node01:27017": /path/to/mongod
"node03:27017": /another/path/to/mongod
```

When running in Docker, include Percona Backup for MongoDB files together with your MongoDB binaries. See [Run Percona Backup for MongoDB in a Docker container](https://docs.percona.com/percona-backup-mongodb/install/docker.html) for more information.

### Parallel data download

!!! admonition "Version added: [2.1.0](../release-notes/2.1.0.md)"
Expand Down
Loading