[DOCS-12006] CM page for Restoring Sharded clusters is incorrect Created: 28/Aug/18 Updated: 29/Oct/23 Resolved: 08/Sep/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Steven Connors (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharded-cluster | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 22 weeks, 5 days ago |
| Epic Link: | DOCSP-3127 |
| Story Points: | 0.2 |
| Description |
|
---------------------------- Original Descriptionhttps://docs.cloudmanager.mongodb.com/tutorial/restore-sharded-cluster/
This page is incorrect in explaining how to conduct a Point in time restore for a sharded cluster. Ops Manager 4.0 docs has it right.
Prior to conducting a sharded cluster PIT restore, users must enable checkpoints from the Backup Dashboard by selecting the appropriate Options dropdown on the cluster, clicking "Edit Snapshot Schedule", and checking the box for "Create Cluster checkpoint every x minutes", where x can be 15, 30, or 60 minutes.
This applies for both Automated Restores & Manual Restores. DescriptionScope of changes (files that need work and how much)Impact to other docs outside of this productMVP (work and date?)Resources (e.g. Scope Docs, Invision) |
| Comments |
| Comment by Githook User [ 08/Sep/18 ] |
|
Author: {'name': 'Anthony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 08/Sep/18 ] |
|
Author: {'name': 'Anthony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |