Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Managed Service for MySQL®
  • Getting started
  • Access management
  • Terraform reference
    • Authentication with the API
      • Overview
        • Overview
        • Get
        • List
        • Delete
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • HTTP request
  • Query parameters
  • Response
  • Backup
  1. API reference
  2. REST
  3. Backup
  4. List

Managed Service for MySQL API, REST: Backup.List

Written by
Yandex Cloud
Improved by
amatol
Updated at April 18, 2025
  • HTTP request
  • Query parameters
  • Response
  • Backup

Retrieves the list of backups in a folder.

To list backups for an existing cluster, make a ClusterService.ListBackups request.

HTTP request

GET https://mdb.api.cloud.yandex.net/managed-mysql/v1/backups

Query parameters

Field

Description

folderId

string

Required field. ID of the folder to list backups in.

To get this ID, make a yandex.cloud.resourcemanager.v1.FolderService.List request.

pageSize

string (int64)

The maximum number of results per page to return.

If the number of available results is larger than pageSize, the API returns a ListBackupsResponse.nextPageToken that can be used to get the next page of results in the subsequent BackupService.List requests.

pageToken

string

Page token that can be used to iterate through multiple pages of results.

To get the next page of results, set pageToken to the ListBackupsResponse.nextPageToken returned by the previous BackupService.List request.

Response

HTTP Code: 200 - OK

{
  "backups": [
    {
      "id": "string",
      "folderId": "string",
      "createdAt": "string",
      "sourceClusterId": "string",
      "startedAt": "string",
      "size": "string",
      "type": "string",
      "status": "string",
      "journalSize": "string"
    }
  ],
  "nextPageToken": "string"
}

Field

Description

backups[]

Backup

List of backups.

nextPageToken

string

The token that can be used to get the next page of results.

If the number of results is larger than ListBackupsRequest.pageSize, use the nextPageToken as the value for the ListBackupsRequest.pageToken in the subsequent BackupService.List request to iterate through multiple pages of results.

Each of the subsequent BackupService.List requests should use the nextPageToken value returned by the previous request to continue paging through the results.

Backup

An object that represents MySQL backup.

See the documentation for details.

Field

Description

id

string

Required field. ID of the backup.

folderId

string

ID of the folder that the backup belongs to.

createdAt

string (date-time)

Creation timestamp (the time when the backup operation was completed).

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

sourceClusterId

string

ID of the cluster that the backup was created for.

startedAt

string (date-time)

Start timestamp (the time when the backup operation was started).

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

size

string (int64)

Size of backup, in bytes

type

enum (BackupCreationType)

How this backup was created (manual/automatic/etc...)

  • BACKUP_CREATION_TYPE_UNSPECIFIED
  • AUTOMATED: Backup created by automated daily schedule
  • MANUAL: Backup created by user request

status

enum (BackupStatus)

Status of backup

  • BACKUP_STATUS_UNSPECIFIED
  • DONE: Backup is done
  • CREATING: Backup is creating

journalSize

string (int64)

Size of the journal associated with backup, in bytes.

Was the article helpful?

Previous
Get
Next
Delete
Yandex project
© 2025 Yandex.Cloud LLC