• API >
• Public API Resources >
• Backup and Restore >
• Backup Configurations >
• Update One Backup Configuration

Update One Backup Configuration

Base URL: {opsManagerHost}:{port}

Syntax

copy

PATCH /api/public/v1.0/groups/{GROUP-ID}/backupConfigs/{CLUSTER-ID}

Request Parameters

Request Path Parameters

Parameter	Required/Optional	Description
GROUP-ID	Required.	The unique identifier for the group that holds the cluster with the backup configuration you want to change.
CLUSTER-ID	Required.	The unique indentifier of the cluster whose backup configuration you want to change.

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
pageNum	integer	Page number (1-based).	1
itemsPerPage	integer	Maximum number of items to return, up to a maximum of 100.	100
pretty	boolean	Display response in human-readable format.	false

Request Body Parameters

Name	Type	Description
groupId	string	ID of the group that owns this backup configuration.
clusterId	string	ID of the cluster that this backup configuration is for.
statusName	string	The current (or desired) status of the backup configuration. Possible values are: INACTIVE PROVISIONING STARTED STOPPED TERMINATING
storageEngineName	string	The storage engine used for the backup. Possible values are: MEMORY_MAPPED WIRED_TIGER
authMechanismName	string	The name of the authentication mechanism to use when connecting to the sync source database. Only present when using authentication. Possible values are: MONGODB_CR (deprecated) SCRAM_SHA_1 GSSAPI PLAIN MONGODB_X509 NONE
username	string	The username to use to connect to the sync source database. Only present when backing up mongod instances that require clients to authenticate. You can send this field to Ops Manager only when updating the backup configuration for a replica set or sharded cluster that is not managed by Ops Manager Automation.
password	string	The password to use to connect to the sync source database. Only present when backup the mongod instances that require clients to authenticate. GET requests do not include this field. You can send this field to Ops Manager only when updating the backup configuration for a replica set or sharded cluster that is not managed by Ops Manager Automation.
encryptionEnabled	boolean	Specifies whether encryption is enabled for the backup configuration. You must include the syncSource field when enabling encryption for a backup configuration. For existing backups in a group, enabling encryption requires an initial backup sync to recreate the backups’ head databases.
sslEnabled	boolean	Is SSL enabled for the sync source database?
syncSource	string	The mongod instance to get backup data from. Possible values are either a specific hostname or one of: PRIMARY and SECONDARY. This field is only used when updating a backup configuration. It is not returned by a GET request.
provisioned	boolean	Reports if Ops Manager has provisioned the resources needed to store a backup. This field is only present when the amount of data to be backed up exceeds a certain threshold.
excludedNamespaces	string array	A list of database names and collection names to omit from the backup. Each string is a namespace in the form of {database} or {database}.{collection}. If this field is present the includedNamespaces field cannot be present. You must send the new full list of excluded namespaces, including any that were already listed. If the new list removes any namespaces from the previous list, you must also set the syncSource field, as the removal of an excluded namespace necessitates a full resync. Without the syncSource field, the request will fail. If the new list only adds to the previous list, you do not need to set syncSource.
includedNamespaces	string array	A list of database names and collection names to include in the backup. Each string is a namespace in the form of {database} or {database}.{collection}. Any namespace not listed in this array will not be backed up. If this field is present the excludedNamespaces field cannot be present. You must send the new full list of included namespaces, including any that were already listed. If the new list adds any namespaces to the previous list, you must also set the syncSource field, as the addition of an included namespace necessitates a full resync. Without the syncSource field, the request will fail. If the new list only removes namespaces from the previous list, you do not need to set syncSource.

Response Elements

Name	Type	Description
groupId	string	ID of the group that owns this backup configuration.
clusterId	string	ID of the cluster that this backup configuration is for.
statusName	string	The current (or desired) status of the backup configuration. Possible values are: INACTIVE PROVISIONING STARTED STOPPED TERMINATING
storageEngineName	string	The storage engine used for the backup. Possible values are: MEMORY_MAPPED WIRED_TIGER
authMechanismName	string	The name of the authentication mechanism to use when connecting to the sync source database. Only present when using authentication. Possible values are: MONGODB_CR (deprecated) SCRAM_SHA_1 GSSAPI PLAIN MONGODB_X509 NONE
encryptionEnabled	boolean	Specifies whether encryption is enabled for the backup configuration. You must include the syncSource field when enabling encryption for a backup configuration. For existing backups in a group, enabling encryption requires an initial backup sync to recreate the backups’ head databases.
sslEnabled	boolean	Is SSL enabled for the sync source database?
syncSource	string	The mongod instance to get backup data from. Possible values are either a specific hostname or one of: PRIMARY and SECONDARY. This field is only used when updating a backup configuration. It is not returned by a GET request.
provisioned	boolean	Reports if Ops Manager has provisioned the resources needed to store a backup. This field is only present when the amount of data to be backed up exceeds a certain threshold.
excludedNamespaces	string array	A list of database names and collection names to omit from the backup. Each string is a namespace in the form of {database} or {database}.{collection}. If this field is present the includedNamespaces field cannot be present. You must send the new full list of excluded namespaces, including any that were already listed. If the new list removes any namespaces from the previous list, you must also set the syncSource field, as the removal of an excluded namespace necessitates a full resync. Without the syncSource field, the request will fail. If the new list only adds to the previous list, you do not need to set syncSource.
includedNamespaces	string array	A list of database names and collection names to include in the backup. Each string is a namespace in the form of {database} or {database}.{collection}. Any namespace not listed in this array will not be backed up. If this field is present the excludedNamespaces field cannot be present. You must send the new full list of included namespaces, including any that were already listed. If the new list adds any namespaces to the previous list, you must also set the syncSource field, as the addition of an included namespace necessitates a full resync. Without the syncSource field, the request will fail. If the new list only removes namespaces from the previous list, you do not need to set syncSource.

Examples

Example Request

copy

curl --user "{username}:{apiKey}" --digest \
 --header "Accept: application/json" \
 --header "Content-Type: application/json" \
 --include --request PATCH "https://{opsManagerHost}:{port}/api/public/v1.0/groups/{GROUP-ID}/backupConfigs/{CLUSTER-ID}" \
 --data '
 {
   "statusName": "STOPPED"
 }'

Example Response

copy

HTTP/1.1 202 Accepted
Content-Type: application/json; charset=UTF-8

copy

{
  "groupId" : "5196d3628d022db4cbc26d9e",
  "clusterId" : "5196e5b0e4b0fca9cc88334a",
  "statusName" : "STOPPED",
  "storageEngineName" : "WIRED_TIGER",
  "sslEnabled" : false,
  "excludedNamespaces" : [ ],
  "links" : [ ... ]
}

←   Get One Backup Configuration from a Group Snapshot Schedule  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.