This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Get the Snapshot Schedule


Groups and projects are synonymous terms. Your {GROUP-ID} is the same as your project id. For existing groups, your group/project id remains the same. This page uses the more familiar term group when referring to descriptions. The endpoint remains as stated in the document.

Base URL: https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0


GET /groups/GROUP-ID/backupConfigs/CLUSTER-ID/snapshotSchedule

Request Parameters

Request Path Parameters

Parameter Type Description
GROUP-ID string (Required.) The unique identifier for the group that holds the cluster with the snapshot schedule you want to get.
CLUSTER-ID string (Required.) The unique indentifier of the cluster whose snapshot schedule you want to get.

Request Query Parameters

This endpoint may use any of the HTTP request query parameters available to all Ops Manager API resources. These are all optional.

Name Type Description Default
pretty boolean Indicates whether the response body should be in a prettyprint format. false
envelope boolean

Indicates whether or not to wrap the response in an envelope.

Some API clients cannot access the HTTP response headers or status code. To remediate this, set envelope=true in the query.

For endpoints that return one result, the response body includes:

Name Description
status HTTP response code
envelope Expected response body

Request Body Parameters

This endpoint does not use HTTP request body parameters.


Name Type Description
groupId string Unique identifier of the group that owns the backup configuration.
clusterId string Unique identifier of the cluster to which this backup configuration applies.
snapshotIntervalHours number Number of hours between snapshots. Supported values are 6, 8, 12, and 24.
snapshotRetentionDays number Number of days to keep recent snapshots. Supported values are 2 - 5.
clusterCheckpointIntervalMin number Number of minutes between successive cluster checkpoints. This only applies to sharded clusters. This number determines the granularity of point-in-time restores for sharded clusters. Supported values are 15, 30, and 60.
dailySnapshotRetentionDays number Number of days to retain daily snapshots. Supported values are 1 - 365.
weeklySnapshotRetentionWeeks number Number of weeks to retain weekly snapshots. Supported values are 1 - 52.
monthlySnapshotRetentionMonths number Number of months to retain monthly snapshots. Supported values are 1 - 36.
pointInTimeWindowHours number Number of hours in the past for which a point-in-time snapshot can be created.
referenceHourOfDay number Hour of the day to schedule snapshots using a 24 hour clock. Default value is 0 (midnight), and supported values are 0 - 23.
referenceMinuteOfHour number Minute of the hour to schedule snapshots. Default value is 0 and supported values are 0 - 59.
referenceTimeZoneOffset string The ISO-8601 timezone offset where the Ops Manager host resides. To avoid problems with daylight saving time, use UTC. The default is +0000, which is equivalent to UTC. Z is also a supported value and equivalent to UTC.
links object array One or more links to sub-resources and/or related resources. The relations between URLs are explained in the Web Linking Specification

Example Request

curl --user "{username}:{apiKey}" --digest \
 --header "Accept: application/json" \
 --include \
 --request GET "https://{opsManagerHost}:{port}/api/public/v1.0/groups/{GROUP-ID}/backupConfigs/{CLUSTER-ID}/snapshotSchedule"

Example Response

Response Header

HTTP/1.1 401 Unauthorized
Content-Type: application/json;charset=ISO-8859-1
Date: {dateInUnixFormat}
WWW-Authenticate: Digest realm="MMS Public API", domain="", nonce="{nonce}", algorithm=MD5, op="auth", stale=false
Content-Length: {requestLengthInBytes}
Connection: keep-alive
HTTP/1.1 200 OK
Vary: Accept-Encoding
Content-Type: application/json
Strict-Transport-Security: max-age=300
Date: {dateInUnixFormat}
Connection: keep-alive
Content-Length: {requestLengthInBytes}

Response Body

  "clusterId" : "{CLUSTER-ID}",
  "dailySnapshotRetentionDays" : 7,
  "groupId" : "{GROUP-ID}",
  "links" : [],
  "monthlySnapshotRetentionMonths" : 13,
  "pointInTimeWindowHours": 24,
  "snapshotIntervalHours" : 6,
  "snapshotRetentionDays" : 2,
  "weeklySnapshotRetentionWeeks" : 4