TencentDB for MongoDB allows to you create and manage disaster recovery instances in the console.
Background
TencentDB for MongoDB allows you to create one or more disaster recovery instances. For applications with high requirements of service continuity, data reliability, and compliance, such instances help enhance your capability to deliver continued services at low costs and improve data reliability.
Note:
Due to the delay in data sync, the real-timeness of data sync for disaster recovery instances may not be guaranteed. Sync latency between the disaster recovery instances and the primary instance can be viewed in the console.
A disaster recovery instance can only be read but not written during its lifecycle.
When a disaster recovery instance is disconnected from the primary instance during sync or is promoted to the primary instance manually in the console, it will become a general instance that can be normally read/written.
Version Requirement
Currently, only TencentDB for MongoDB 3.2, 3.6, and 4.0 instances support disaster recovery instance creation.
Use Limits
Up to three disaster recovery instances can be created for a primary instance.
Backup and rollback: They are not supported.
Data migration: Migrating data to disaster recovery instances is not supported.
Database management: Database creation and deletion are not supported.
Account management: Account creation/deletion, password reset, and account authorization are not supported.
The engine of a disaster recovery instance must be the same as that of the primary instance.
Due to network isolation, you cannot create disaster recovery instances in finance zones for primary instances in general regions, and vice visa.
1. On the DR Instance tab, find the target disaster recovery instance.
2. In the Operation column, click Adjust Configuration.
3. On the Adjust Configuration page, you can adjust the node specification, node capacity, and oplog capacity.
4. In the Switch Time option, select the specific time for instance specification switch.
If you select Upon modification completion, the instance specification adjustment task will be executed immediately.
If you select Maintenance time, the instance specification switch task will be executed during the maintenance time.
Note:
We recommend you set the maintenance time to be within off-peak hours of your business, and you need to regularly maintain your instance. If you select Upon modification completion, the instance configuration will be adjusted immediately, which may involve node migration or primary-secondary switch. As the switch time point is uncontrollable, we strongly recommend you make the instance configuration executed within the maintenance time. For more information, see Setting Instance Maintenance Period.
5. You can click Billing Details to view billable items and billing formula and confirm the fees.
6. After confirming that everything is correct, click Submit.
Renewing disaster recovery instance
1. On the DR Instance tab, find the target disaster recovery instance.
2. Click Renew above the instance list and select the renewal period in the Renew Selected Instance window.
3. Confirm the total renewal fees and click OK.
Setting auto-renewal
1. On the DR Instance tab, find the target disaster recovery instance.
2. Click Set Auto-Renewal above the instance list and confirm the auto-renewal item and renewal expiration time in the Set Auto-Renewal window.
3. Confirm the total renewal fees and click OK.
Disabling auto-renewal
1. On the DR Instance tab, find the target disaster recovery instance.
2. Click Disable Auto-Renewal above the instance list and confirm the instance information.
Yes
No
Was this page helpful?