Backup

Available in VPC

In Backup, you can check the backup information configured per server for safe storage of cache data for users using Cloud DB for MongoDB. Also, when the cache data is damaged due to a failure, you can perform restoration using the backup file that was in storage. To use the backup and restoration, it is recommended to first understand the basic execution rules for the backup provided by Cloud DB for MongoDB. The basic backup execution rules are as follows:

• Backup execution methods

  • Performed daily, once a day
  • Backups are performed within 15 minutes from the time selected by the user
    • Exceptional situations
      • If the backup from the previous day is still being performed due to a large backup size, the backup schedule for that day is skipped
      • Since the admin Database includes system collection and internal logic, it is excluded from backup
        • You must avoid storing user data in the admin Database

• Backup file

  • Retention period: You can store for up to 30 days according to the user settings.
  • Storage location: Separate data storage (storage contracts are made according to the backup file size)

Backup page

The basics of using the backup are as follows:

Check backup settings list

You can check the backup settings list per MongoDB server in operation. To check the backup settings list:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to > Services > Database > Cloud DB for MongoDB.
2. Click the Backup menu.
3. When the backup settings list appears, check the required information.
   
   • DB Services name: Service name specified by the user
   • Backup retention date: Maximum number of days for the backup file to be stored in data storage
   • Backup start time: Time at which the backup is performed once a day.
   • Backup data size: Size of the completed backup file
   • Latest succeeded backup date: Date for the latest backup that was performed
   • View details: Details and restoration of the backup file list created per server, saved to Object Storage.

Check backup file list per server

To check the backup file list created for each server after completing the backup:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to > Services > Database > Cloud DB for MongoDB.
2. Click the Backup menu.
3. Click [Details] from View details of the backup settings row you want to check the details for.
4. Check the details for the backup file.
   
   • Backup date: Date that the backup was performed
   • Shard (replica set): Shard that performed the backup
   • Backup start time: Time when the backup was started
   • Backup completion time: Time when the backup was completed
   • Backup speed: Number of collections to be backed up concurrently.
   • Elapsed time: Time it took for the backup to be completed.
   • Backup size: Size of the created backup file upon completion of backup
   • Data storage: Data storage usage of the shard that performed the backup
     • You can check the required storage size when you need to perform a restoration using the backup.

Restoration

Cloud DB for MongoDB provides a service that enables you to restore lost data using backup files, and easily and quickly create a MongoDB Server. It allows the user to restore the data up to the desired time within the range available for recovery. To restore:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to > Services > Database > Cloud DB for MongoDB.
2. Click the Backup menu.
3. Click [Details] in the backup settings row you want to restore.
4. Select the item to restore and click [Restore Backup file].
   
5. When the Restore Backup pop-up window appears, check or enter the required information for restoration
   • Backup time: Checks the backup completion time
   • MongoDB Cluster Type: Select the type of the MongoDB cluster.
   • DB Server name: Enter the name of the MongoDB Server to restore.
     • Enter between 3 and 15 characters using English letters, numbers, and hyphens (-).
     • Duplicate names are not allowed.
     • Random text will be added to avoid duplicate host names.
   • DB Services name: Enter the DB service name for the restored DB.
     • Enter between 3 and 15 characters using Korean letters, English letters, numbers, and hyphens (-).
   • Data storage type: Checks the type of data storage to restore
   • Set the following items depending on the selected cluster type:
   • If you've selected stand-alone for the cluster type, then set the following items:
     
     • Stand-Alone Server Spec: Selects the specifications for the stand-alone server
     • Port: Enters the port number for the Stand-alone server between 10000-65535
       • Default: 17017
       • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities
   • If you've selected single replica set for the cluster type, then set the following items:
     
     • Number of members per replica set (primary & secondary): Select the number of member servers in each shard (3 to 7 including the arbiter server)
     • Member Server Spec: Selects the specifications of the member server
     • Number of Arbiters per Replica Set: Selects the number of arbiter servers per shard (0-1 unit)
     • Arbiter Server Spec: Selects the specifications of the arbiter server
     • Port: Enters the port number for each server between 10000-65535
       • Default: 17017
       • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities
   • If you've selected Sharding for the cluster type, then set the following items:
     
     • Number of members per replica set (primary & secondary): Select the number of member servers in each shard (3 to 7 including the arbiter server)
     • Member Server Spec: Selects the specifications of the member server
     • Number of Arbiters per Replica Set: Selects the number of arbiter servers per shard (0-1 unit)
     • Arbiter Server Spec: Selects the specifications of the arbiter server
     • Number of shards: Selects the number of shards
       • 2 or 3 can be selected upon initial installation.
       • Up to 5 shards can be added in the management page after installation
       • If you need more than 5 Shards, then make an inquiry to Customer support
     • Number of Mongos (Router) Servers: Selects the number of Mongos Servers (2-5 units)
     • Mongos Server Spec: Selects the spec of the Mongos server
     • Number of Config Servers: Checks the number of Config Servers (3 fixed units)
     • Config Server Spec: Selects the specifications of the config server
     • Port: Enters the port number for each server between 10000-65535
       • Default: 17017
       • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities
6. Click [Restore].
7. Click [OK].
8. Click the DB Server menu.
9. Check the status of the server restoration.
   • Creating: Status in which the MongoDB is being created (restored) with the information entered by the user
   • Configuring: Status in which the MongoDB server is being created (restored) for configuration with the information entered by the user
   • Running: Status in which the creation (restoration) and configuration of the MongoDB server has been completed with the information entered by user, and access to the MongoDB from the application servers is available

Store in Object Storage

In Cloud DB for MongoDB, you can store the created backup files in Object Storage and use them when performing backup. To save a stored backup file to Object Storage:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to > Services > Database > Cloud DB for MongoDB.
2. Click the Backup menu.
3. Click [Details] in the backup settings row for the backup file you want to save to Object Storage.
4. Click [Send to Object Storage].
   
5. When the Send to Object Storage popup window appears, click and select the bucket you want to save into.
   
6. Click [Send to Object Storage].
7. Click [OK].