- About
- Basic Features
- Introduction
- Platform Tenant Management
- Platform User Management
- TOTP Certification
- Basic Data Definition
- Media Management
- Command Management
- Mail Server Configuration
- Job Center
- Platform Host Resource Pool
- Platform Database Pool
- Platform Proxy Nodes Management
- Platform Components Management
- Additional Information Management
- Operation Log
- Connection Concurrency Configuration
- Customization of Platform Styles
- Parameter Templates
- License
- Monitor Large Screen
- Overview Display
- Tenant User Management
- Tenant Host Resource Pool
- Tenant Proxy Nodes Management
- Menu Management
- Report Center
- MogDB/openGauss
- Backup Recovery Center
- Monitoring
- Alert Center
- Inspect Center
Takeover With Hosts
Takeover of Primary Database
Function Entrance
Tenant Overview page --> Asset Overview --> Takeover --> MogDB/openGauss
Left-side function menu MogDB/openGauss --> Instance Management --> Takeover --> Takeover With Hosts
Function Description
The takeover of MogDB/openGauss database primary or single instance is to manage and monitor the already running MogDB/openGauss database primary or single instance in the database cloud platform.
The prerequisite for takeover is that the target host has been taken over to the platform (all nodes of the cluster must be taken over), and it can be found in the host resource pool.
Operating Instructions
Takeover process 1 - Select Host
Enter the primary database takeover page, select the host where the instance to be taken over is located, and click 【Connect】 to verify.
Takeover process 2 - Select Instance
After the host is connected successfully, the database instances not been taken over on the server will be displayed. Select the instance and enter the database administrator username and password.
Note: The database administrator should have the permissions to create users and view system parameters, otherwise, the takeover will fail.
Takeover process 3 - Set Cluster Information
After the user account is verified, cluster information needs to be set, including service name, Chinese name, database pool, and project group.
Takeover process 4 - Takeover of Standby Instances and CM Instances
If there are standby instances not taken over and CM nodes under the current primary instance, they will be scanned together and can be taken over together;
Note: If the standby instance and CM node are not in operation or the host is not taken over, they cannot be taken over.
Takeover process 4 - Complete Takeover
Click the 【Confirm】 button and wait for the takeover to complete.
After successful takeover, the database information can be viewed on the instance management page.
Takeover of Standby Instance
Function Entrance
Instance Management --> Click on the service name to enter details --> Below the instance list --> Click on Takeover Standby Instance
Function Description
The takeover of MogDB/openGauss database standby is to manage and monitor the already running MogDB/openGauss database standby in the database cloud platform. The prerequisite for takeover is that the target host has been taken over to the platform (all nodes of the cluster must be taken over), and it can be found in the host resource pool.
Operating Instructions
The zcloud platform will automatically recognize existing standby databases, and you can select the standby database or CM node to be taken over.
If there is a situation where the internal IP of the database is different from the management IP filled in during takeover, the correct internal IP must be filled in during takeover, otherwise, the corresponding management IP cannot be found through the internal IP.
Click "Confirm" to start the takeover.
After successful takeover, the managed database information can be viewed on the service details page.
CM nodes need to switch to the high availability page to view.
