Contact UsGet started
© 2024 Iron Hive LLC Belgrade

Managing backups in Managed Service for MongoDB

Written by
Updated at October 29, 2024

You can create backups and restore clusters from existing backups.

Managed Service for MongoDB also creates automatic daily backups. You can set the backup start time and retention period.

Restoring clusters from backups

The Point-in-Time Recovery (PITR) technology allows you to restore your cluster to any state in the time interval between the oldest backup and the archiving of the most recent oplog collection. For more information, see Backups.

For example, if the backup operation ended on August 10, 2020 at 12:00:00 UTC, the current date is August 15, 2020, 19:00:00 UTC, and the most recent oplog collection was saved on August 15, 2020, 18:50:00 UTC, the cluster can be restored to any state between August 10, 2020, 12:00:01 UTC and August 15, 2020, 18:50:00 UTC, inclusive.

Warning

PITR is not supported for clusters with sharding enabled. Such clusters can only be restored to the time point of the selected backup.

When you restore a cluster from a backup, you create a new cluster with the backup data. If the folder has insufficient resources to create such a cluster, you will not be able to restore from the backup. The average backup recovery speed is 10 MBps.

For a new cluster, you should set all the parameters required during creation, except for cluster type (a MongoDB backup cannot be restored as a PostgreSQL cluster).

When restored to the current state, the new cluster will match the state of:

  • Existing cluster at the time of recovery.
  • Deleted cluster at the time of archiving the last oplog.

To restore an existing cluster from a backup:

  1. Go to the folder page and select Managed Service for MongoDB.

  2. Click the name of the cluster you need and select the Backups tab.

  3. Click for the backup you need and then click Restore cluster.

  4. Set up the new cluster. You can select a folder for the new cluster from the Folder list.

  5. To restore the cluster to a particular point in time after creating this backup, configure Date and time of recovery (UTC) accordingly. You can enter the date manually or select it from the drop-down calendar.

    If you do not change the setting, the cluster will be restored to the state when the backup was completed.

  6. Click Restore cluster.

To restore a previously deleted cluster from a backup:

  1. Go to the folder page and select Managed Service for MongoDB.

  2. In the left-hand panel, select Backups.

  3. Find the backup you need using the backup creation time and cluster ID. The ID column contains IDs formatted as <cluster_ID>:<backup_ID>.

  4. Click for the backup you need and then click Restore cluster.

  5. Set up the new cluster. You can select a folder for the new cluster from the Folder list.

  6. To restore the cluster to a particular point in time after creating this backup, configure Date and time of recovery (UTC) accordingly. You can enter the date manually or select it from the drop-down calendar.

    If you do not change the setting, the cluster will be restored to the state when the backup was completed.

  7. Click Restore cluster.

Managed Service for MongoDB will launch the operation to create a cluster from the backup.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To restore a cluster from a backup:

  1. View a description of the CLI restore MongoDB cluster command:

    yc managed-mongodb cluster restore --help

  2. Getting a list of available MongoDB cluster backups:

    yc managed-mongodb backup list

    Result:

    +--------------------------+---------------------+----------------------+---------------------+--------+-----------+
|            ID            |     CREATED AT      |  SOURCE CLUSTER ID   |     STARTED AT      |  SIZE  |   TYPE    |
+--------------------------+---------------------+----------------------+---------------------+--------+-----------+
| c9qlk4v13uq7********:... | 2020-08-10 12:00:00 | c9qlk4v13uq7******** | 2020-08-10 11:55:17 | 3.3 KB | AUTOMATED |
| ...                                                                                         |                    |
+--------------------------+---------------------+----------------------+---------------------+--------+-----------+

    The backup completion time is shown in the CREATED AT column of the list of available backups, in yyyy-mm-dd hh:mm:ss format (2020-08-10 12:00:00 in the example above). You can restore a cluster to any point in time starting with the point when the backup is created.

  3. Run the command to create a new cluster from a backup (the example shows only some parameters):

     yc managed-mongodb cluster restore \
    --backup-id <backup_ID> \
    --recovery-target-timestamp <time_point> \
    --mongodb-version <MongoDB_version> \
    --name <new_cluster_name> \
    --environment <environment> \
    --network-name <network_name> \
    --host zone-id=<availability_zone>,`
          `subnet-id=<subnet_ID> \
    --mongod-resource-preset <host_class> \
    --mongod-disk-size <storage_size_in_GB> \
    --mongod-disk-type <disk_type> \
    --performance-diagnostics=<enable_diagnostics>

    Where:

    • --recovery-target-timestamp: Time point to restore the MongoDB cluster to, in UNIX time format. If you do not specify the parameter, the cluster will be restored to when the backup was completed.

    • --environment: Environment, PRESTABLE or PRODUCTION.

    • --mongod-disk-type: Disk type, network-hdd or network-ssd.

    • --performance-diagnostics: Enables cluster performance diagnostics, true or false.

To restore an existing cluster from a backup, use the restore REST API method for the Cluster resource or the ClusterService/Restore gRPC API call and provide the following in the request:

  • ID of the backup you need, in the backupId parameter. To find out the ID, get a list of cluster backups.
  • Name of the new cluster that will contain the data recovered from the backup, in the name parameter. It must be unique within the folder.

In the recoveryTargetSpec.timestamp parameter, specify the time point to restore the MongoDB cluster to, in UNIX time format. If you do not specify the parameter, the cluster will be restored to when the backup was completed.

Creating a backup

  1. Go to the folder page and select Managed Service for MongoDB.
  2. Click the name of the cluster you need and select the Backups tab.
  3. Click Create backup.

The service will start creating a backup without an additional confirmation.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To create a cluster backup:

  1. View a description of the CLI create MongoDB backup command:

    yc managed-mongodb cluster backup --help

  2. Request a backup to be created by specifying the cluster name or ID:

    yc managed-mongodb cluster backup <cluster_name_or_ID>

    You can get the cluster ID and name with a list of clusters.

To create a backup, use the backup REST API method for the Cluster resource or the ClusterService/Backup gRPC API call and provide the cluster ID in the clusterId parameter of your request.

You can get the cluster ID with a list of clusters in the folder.

Warning

While you are creating your backup, the cluster performance might degrade.

Getting a list of backups

To get a list of cluster backups:

  1. Go to the folder page and select Managed Service for MongoDB.
  2. Click the name of the cluster you need and select the Backups tab.

To get a list of all backups in a folder:

  1. Go to the folder page and select Managed Service for MongoDB.
  2. In the left-hand panel, select Backups.

These lists contain the following information:

  • Backup name.
  • Source shard.
  • Backup size.
  • Backup type: Automatic (Automated) or manual (Manual).
  • Start time of backup creation in UTC (Coordinated Universal Time).
  • End time of backup creation in UTC.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To get a list of MongoDB cluster backups available in the default folder, run the command:

yc managed-mongodb backup list

Result:

+--------------------------+---------------------+----------------------+---------------------+--------+-----------+
|            ID            |     CREATED AT      |  SOURCE CLUSTER ID   |     STARTED AT      |  SIZE  |   TYPE    |
+--------------------------+---------------------+----------------------+---------------------+--------+-----------+
| c9qlk4v13uq7********:... | 2020-08-10 12:00:00 | c9qlk4v13uq7******** | 2020-08-10 11:55:17 | 3.3 KB | AUTOMATED |
| c9qpm90p3pcg********:... | 2020-08-09 22:01:04 | c9qpm90p3pcg******** | 2020-08-09 21:30:00 | 30 KB  | MANUAL    |
+--------------------------+---------------------+----------------------+---------------------+--------+-----------+

The resulting table contains the following information:

  • ID of the backup.
  • End time of backup creation in UTC (Coordinated Universal Time).
  • ID of the cluster that the backup was created for.
  • Start time of backup creation in UTC.
  • Backup size.
  • Backup type: Automatic (AUTOMATED) or manual (MANUAL).

To get a list of cluster backups, use the listBackups REST API method for the Cluster resource or the ClusterService/ListBackups gRPC API call and provide the cluster ID in the clusterId parameter of your request.

You can get the cluster ID with a list of clusters in the folder.

To get a list of backups for all the Managed Service for MongoDB clusters in the folder, use the list REST API method for the Backup resource or the BackupService/List gRPC API call and provide the folder ID in the folderId parameter of your request.

Getting information about backups

To get information about the backup of an existing cluster:

  1. Go to the folder page and select Managed Service for MongoDB.
  2. Click the name of the cluster you need and select the Backups tab.

To get information about the backup of a previously deleted cluster:

  1. Go to the folder page and select Managed Service for MongoDB.
  2. In the left-hand panel, select Backups.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To get information about a MongoDB cluster backup, run the command:

yc managed-mongodb backup get <backup_ID>

You can retrieve the backup ID with a list of backups.

To get information about a backup, use the get REST API method for the Backup resource or the BackupService/Get gRPC API call and provide the backup ID in the backupId parameter of your request.

To find out the ID, retrieve a list of backups.

Examples

Create a new Managed Service for MongoDB cluster from a backup with the following test characteristics:

  • Recovery backup: c9qlk4v13uq7********:....
  • Time point to recover to: 1597060810 (2020-08-10 12:00:10).
  • Version: 5.0.
  • Name of the new cluster: mynewmg.
  • Environment: PRODUCTION.
  • Network: default.
  • One s2.micro host in the ru-central1-a availability zone and b0rcctk2rvtr******** subnet.
  • Network SSD storage (network-ssd): 20 GB.
  • With databases and users that existed in the cluster at the time of recovery.

Run the following command:

yc managed-mongodb cluster restore \
   --backup-id c9qlk4v13uq7********:... \
   --recovery-target-timestamp 1597060810 \
   --mongodb-version 5.0 \
   --name mynewmg \
   --environment PRODUCTION \
   --network-name default \
   --host zone-id=ru-central1-a,subnet-id=b0rcctk2rvtr8efcch64 \
   --mongod-resource-preset s2.micro \
   --mongod-disk-size 20 \
   --mongod-disk-type network-ssd
Previous
Migrating hosts to a different availability zone
Next
Deleting a cluster