Help Center/ Cloud Bastion Host/ User Guide/ Managing Instances/ Changing an Instance from Single-Node to Primary/Standby Deployment
Updated on 2026-08-11 GMT+08:00
Changing an Instance from Single-Node to Primary/Standby Deployment
Scenarios
This section describes how to change an instance from single-node to primary/standby.
Notes and Constraints
- A standard edition single-node instance that supports 200 or more assets cannot be converted into a primary/standby instance.
- Only CBH instances of the latest edition can be changed from single-node to primary/standby deployment. You can upgrade the instance edition if needed by referring to Upgrading the Instance Version.
Changing an Instance from Single-Node to Primary/Standby
- Log in to the CBH console.
- Click
in the upper left corner on the displayed page and select a region. - Locate the row containing the target instance. In the Operation column, choose More > Change to Primary/Standby.
- In the New Configuration area, select the standby AZ, confirm the configuration, and click Pay.
- Complete the payment.
- On the CBH instance list page, the instance status changes from Running to in sequence.
When the CBH instance status changes to Running, the CBH system is available.
Parent topic: Managing Instances
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot