---
title: "Update Snapshot Schedule for One Cluster"
method: PATCH
path: "/api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule"
tags: ["Legacy Backup"]
deprecated: true
---

# Update Snapshot Schedule for One Cluster

`PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule`

> **Deprecated.**

Updates the snapshot schedule for one cluster in the specified project.

 Effective 23 March 2020, all new clusters can use only Cloud Backups. When you upgrade to 4.2, your backup system upgrades to cloud backup if it is currently set to legacy backup. After this upgrade, all your existing legacy backup snapshots remain available. They expire over time in accordance with your retention policy. Your backup policy resets to the default schedule. If you had a custom backup policy in place with legacy backups, you must re-create it with the procedure outlined in the Cloud Backup documentation.

## Path parameters

- `groupId` string, required
- `clusterName` string, required

## Query parameters

- `envelope` boolean
- `pretty` boolean

## Response `200`

OK

## Other responses

- `400` — Bad Request.
- `401` — Unauthorized.
- `403` — Forbidden.
- `404` — Not Found.
- `429` — Too Many Requests.
- `500` — Internal Server Error.

---

[API](https://skmtc.dev/mongodb/apis/atlas-admin-api.md) · [All operations](https://skmtc.dev/mongodb/apis/atlas-admin-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mongodb/atlas-admin-api/revisions/e37e8ef8429f/schema)