« back to Support Page
: Backup & Restore
MongoDB is a general purpose NoSQL database developed by MongoDB, Inc.
Anti-Cloud Backup & Restore supports backing up MongoDB databases as a Protected Item type.
No temporary disk space is required: database content is streamed directly from the MongoDB server into Anti-Cloud's chunking deduplication engine without requiring any temporary disk space. All backup jobs require only incremental storage using Anti-Cloud's chunking technology.
Backing up data from your MongoDB server will cause some additional load on the MongoDB server for the duration of the backup job.
The underlying technology is
mongodump. Anti-Cloud will use your system installed
mongodump version for best compatibility with the exact feature set of your MongoDB server. This is the officially supported mechanism for backing up a MongoDB database.
This technology is also compatible with MongoDB forks, variants and cloud services, including but not limited to
- Self-hosted MongoDB server software
- MongoDB Community Server
- MongoDB Enterprise Server
- TokuMX / Percona Server for Mongo
- Cloud hosted MongoDB services (SaaS)
Anti-Cloud will search the PC for the system installed
mongo shell binaries. If your binaries are installed in a normal system location, Anti-Cloud will find and use the most recent available binary. If you have special requirements, or if Anti-Cloud is unable to automatically detect the binary path, you can override the binary path to use a custom
mongo shell binary.
Connection details should be set before picking databases for backup. Enter your MongoDB connection details in the lower part of the window.
Anti-Cloud supports connecting to MongoDB in different ways:
- Direct connection
- Enter a hostname and port for the MongoDB server (
mongos). The default port is 27017.
- Direct connection through SSH tunnel
- Anti-Cloud will open an SSH tunnel to the remote server, and then run the locally installed
mongodump binary against the forwarded port connection. The use of SSH as a transport layer is independent of whether SSL is also enabled (described below).
- Replica set
- You must specify the name of the replica set (e.g.
- Add the hostname and port for each of the replica set members that are reachable from the Anti-Cloud device.
- When using Replica Set connection in Anti-Cloud, Anti-Cloud will only read data from one of the members. You can use the "read preference" option to choose which MongoDB server Anti-Cloud will prefer to back up from.
- Anti-Cloud will attempt to back up from the primary. If the primary server is unreachable, the backup job will fail.
- Primary preferred
- Anti-Cloud will attempt to back up from the primary, but will back up from the secondary if the primary is unreachable.
- Anti-Cloud will attempt to back up from the secondary. If the secondary server is unreachable, the backup job will fail.
- Secondary preferred
- Anti-Cloud will attempt to back up from the secondary, but will back up from the primary if the secondary is unreachable.
- This option will back up data from the server in the replica set that has the lowest latency (ping) to the Anti-Cloud device.
Anti-Cloud supports the following transport layers:
- SSL (TLS)
- If your MongoDB server is using self-signed certificates, you can choose whether to trust an invalid SSL certificate from the MongoDB server.
Anti-Cloud supports the following authentication mechanisms:
- Username/password (
- You must specify the authentication database for looking up the credentials inside MongoDB. The default authentication database is
- Client certificates (
- This option is only available if the MongoDB server connection is going over an SSL (TLS) transport layer.
- To use this feature, you should have a
.pem file that contains the client SSL (TLS) certificate, intermediates, and private key in text
- A private key password is optionally supported.
Other authentication mechanisms are not currently supported in Anti-Cloud (e.g. neither Kerberos / LDAP when using MongoDB Enterprise; nor, custom authentication mechanisms used by MongoDB software variants).
Anti-Cloud can backup a MongoDB replica set with a consistent point-in-time snapshot.
Anti-Cloud can back up a sharded MongoDB cluster, but depending on your MongoDB server version, there are some limitations:
- In MongoDB 4.2 and later, the backup may not be point-in-time consistent, unless writes are temporarily suspended to the MongoDB cluster (e.g. by running custom Before and After commands on the Anti-Cloud Protected Item configuration).
- If you are using a variant MongoDB engine (e.g. Amazon DocumentDB or Azure CosmosDB), different consistency guarantees may apply to sharded backups. You should check with your vendor for additional information.
To back up a sharded cluster in Anti-Cloud, enter the
mongos front-end server in the Anti-Cloud connection details.
When backing up from a
mongos server, Anti-Cloud cannot make use of the "read preference" selection as data is proxied through
mongos. The backup will read from the primary replica set member of each shard replica set.
Use the plus button on the right to open a database browser, allowing you to select individual MongoDB databases for backup.
Anti-Cloud will back up all MongoDB collections within the selected MongoDB databases.
Anti-Cloud's MongoDB Protected Item type produces a
.bson file for each selected MongoDB database. You can restore all databases, or selected databases only.
When restoring, you can choose to either
- restore back to a
.bson files on disk, and then import them into your MongoDB server; or
- you can use the Program Input restore type to pipe the restore data directly back into your MongoDB server
« back to Support Page