ApsaraDB for MongoDB automatically backs up data according to the default backup policy. You can also set a backup policy based on business requirements to automatically back up data for your ApsaraDB for MongoDB instances as required.
MongoDB replica set is composed of a group of MongoDB instances (processes), including one primary node and multiple secondary nodes. All the data on the MongoDB Driver (client) is written to the primary node, and the secondary node synchronizes the written data from the primary node to ensure that all the members in the replica set store the same datasets to achieve high availability of data.
The figure below (contributed by the official documents of MongoDB) shows a typical MongoDB replica set including a primary node and two secondary nodes.
Because the hidden node will not accept requests from the Driver, you can use the hidden node for data backup, offline computing, and other tasks without affecting the service provided by the replica set.
In the current database ecosystem, most database systems support data synchronization among multiple node instances such as MySQL Master/Slave synchronization and Redis AOF master/slave synchronization. MongoDB even supports replica set synchronization among three or more nodes; this solidly ensures the high availability of a logical unit's data redundancy.
Note that data backup is MongoShake's core function, but data backup is not its only function. Using MongoShake as a platform service, you can meet your needs in different business scenarios by means of data subscription and consumption.
In this tutorial, we’ll show you how to get started with Alibaba Cloud ApsaraDB for MongoDB. In particular, we will be exploring how to create, migrate, and back up database files with Alibaba Cloud ApsaraDB for MongoDB.
Creating regular backups is a vital part of managing a database server, whether it's cloud-based or running on your own premises. It may be that your application already handles this by automatically retrieving its key data from the database server and creating backup files at regular intervals. If this is not the case, you will need to create and manage your backups as part of the process of running an ApsaraDB for RDS instance.
ApsaraDB for RDS includes an automatic backup system as standard, and it's important that you configure this to ensure that your data is being backed up at suitable times.
Backing up databases is not always as straightforward as backing up document files, as one or more applications might be updating the database at the time it's being backed up. If an update involves amending more than one table in the database, and if the backup takes place before all updates are complete, the backup will not be reliable.
This tutorial will cover how to get started with the ApsaraDB Stack and how to ensure your data is backed up, including both automatic and manual backups and covering how to access your data from the backup, if case problems do occur.
You can log on to the ApsaraDB for MongoDB console to download a physical backup file from an ApsaraDB for MongoDB instance. This topic describes how to recover ApsaraDB for MongoDB physical backup data in a user-created MongoDB instance.
Replica set and sharded cluster instances support logical backup. You can start a full logical backup to back up instance data and download the logical backup file. Then, you can run a mongorestore command to recover the downloaded backup data in a user-created MongoDB instance.
Alibaba Cloud Database Service has been recognized as A Strong Performer by Forrester. To celebrate the achievement and progress made by Alibaba Cloud database, we are now giving out attractive offers exclusively for our customers. Please refer to the Terms and Conditions section for details and rules of the offers.
Alibaba Clouder - August 2, 2019
Alibaba Clouder - March 18, 2019
Alibaba Clouder - April 3, 2018
Alibaba Cloud Product Launch - December 17, 2018
- December 5, 2017
Alibaba Clouder - August 12, 2019
More Posts by Alibaba Clouder