Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

How to restore a backup

This is a guide on how to perform a basic restore of a local backup of your Charmed MongoDB replica set or sharded cluster.

Prerequisites

Summary


Determine the application to run backup actions on

The application to pass to juju when running backup and restore actions depends on whether your deployment is a replica set or sharded cluster:

When running Charmed MongoDB as a replica-set, this will be the name of your MongoDB application.

When running Charmed MongoDB as a sharded cluster, this will be the name of your MongoDB application running with the “config-server” role - never the shard applications.

List all backups

To list all backups available, run:

juju run <replica-set name | config-server name>/leader list-backups

This will display available backups similar to the output below:

    backup-id             | backup-type  | backup-status
    ----------------------------------------------------
    YYYY-MM-DDTHH:MM:SSZ  | logical      | finished 

Restore a backup

Before restoring a backup, check that your Charmed MongoDB deployment is active and idle with juju status.

To restore a backup from the list, run the restore command using the backup-id:

juju run <replica-set name | config-server name>/leader restore backup-id=YYYY-MM-DDTHH:MM:SSZ

The restore will now be in progress.

Last updated 8 months ago. Help improve this document in the forum.