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.

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

PBM-815 PITR for physical restores #124

Merged
merged 2 commits into from
Jul 13, 2023
Merged

PBM-815 PITR for physical restores #124

merged 2 commits into from
Jul 13, 2023

Conversation

nastena1606
Copy link
Collaborator

modified: docs/reference/pbm-commands.md
modified: docs/usage/oplog-replay.md
modified: docs/usage/pitr-tutorial.md

modified:   docs/reference/pbm-commands.md
	modified:   docs/usage/oplog-replay.md
	modified:   docs/usage/pitr-tutorial.md
@render
Copy link

render bot commented Jul 5, 2023


4. After the oplog replay, make a fresh backup and enable the point-in-time recovery oplog slicing.
1. Due to the physical restore logic and flow, PBM replays oplog events on the primary node of every shard when Percona Server for MongoDB is shut down. After the database start, the remaining nodes receive the data during the initial sync.
2. When doing point-in-time recovery for deployments with sharded collections, PBM only writes data to existing ones and doesn’t support creating new collections. Therefore, whenever you create a new sharded collection, make a new backup for it to be included there.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doesn’t support creating new collections
@sandraromanchenko @olexandr-havryliak, did you check if it is any collections or only shared ones?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dAdAbird Restore with non-shared collections works ok.

docs/usage/pitr-tutorial.md Outdated Show resolved Hide resolved
	modified:   docs/features/point-in-time-recovery.md
@nastena1606 nastena1606 merged commit c413087 into main Jul 13, 2023
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants