Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: https://docs.opsmanager.mongodb.com/v1.6/core/backup-preparations/#snapshot-frequency-and-retention-policy
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36
*Referrer*: https://jira.mongodb.org/browse/CS-23238
*Screen Resolution*: 1440 x 900
*repo*: REPONAME
*source*: core/backup-preparations
*Location*: https://docs.opsmanager.mongodb.com/v1.6/core/backup-preparations/#snapshot-frequency-and-retention-policy *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36 *Referrer*: https://jira.mongodb.org/browse/CS-23238 *Screen Resolution*: 1440 x 900 *repo*: REPONAME *source*: core/backup-preparations
Description
The edit schedule page is not documented for Ops Manager 1.6. Reading the docs it seems that it's present on Ops Manager 1.8 and not on 1.6.
On 1.8 documentation you say:
You can change a backed-up deployment’s schedule through its Edit Snapshot Schedule menu option, available through the Backup tab. Administrators can change snapshot frequency and retention through the snapshotSchedule resource in the API. If you change the schedule to save fewer snapshots, Ops Manager does not delete existing snapshots to conform to the new schedule. To delete unneeded snapshots, see Delete a Snapshot.
while on 1.6:
Administrators can change snapshot frequency and the retention policy through the snapshotSchedule resource in the API. If you change the schedule to save fewer snapshots, Ops Manager does not delete existing snapshots to conform to the new schedule. To delete unneeded snapshots, see Delete Snapshots for Replica Sets and Sharded Clusters.
Please fix it.