In disaster recovery scenarios such as primary-standby and cascading setups, OCP supports freely switching the synchronization configuration for a standby tenant. This facilitates cross-region switchover drills and enhances the relationship management capability between primary and standby tenants.
This section provides detailed instructions on how to change the synchronization configuration for a standby tenant.
Prerequisites
Only normally running standby tenants support changing the synchronization configuration.
Ensure the current OCP user has at least the following permissions:
- Cluster Maintenance or Tenant Maintenance resource permissions.
- Permission to access the Overview menu of the tenant.
Ensure the primary-standby protection mode of the current tenant is set to Maximum Performance.
Background information
When changing the synchronization configuration for a standby tenant, the following restrictions apply to the selected new source tenant:
- The new source tenant can be any upstream tenant, peer tenant, or downstream tenant at the same level as the current standby tenant, but downstream tenants of the current standby tenant cannot be selected.
- When the synchronization method between primary and standby tenants is Archived-Based, the new source tenant must have archive backup enabled. If its archive information is incomplete, manual supplementation is required when changing the synchronization configuration.
- Before changing the synchronization configuration, ensure the consistency of logs between the primary and standby tenants; otherwise, the primary-standby relationship may not be established.
Procedure
Log in to OCP.
In the left navigation bar, select Tenant. The system enters the Tenants page by default.
Select the standby tenant to operate on and click its name to enter the tenant's Overview page.
Click the ... icon in the upper-right corner and select Change Synchronization Configuration.
In the dialog box that appears, select a new source tenant and a synchronization method, and confirm whether the new tenant topology meets expectations.
- Network-based Synchronization synchronizes logs over the RPC network between OBServer nodes. The standby tenant can directly read the primary tenant's logs via
IP + port. - Archived-Based synchronizes logs through shared storage. The primary tenant writes logs to network disks or OSS storage, and the standby tenant reads data from the shared storage.
- Network-based Synchronization synchronizes logs over the RPC network between OBServer nodes. The standby tenant can directly read the primary tenant's logs via
Click Test to verify whether the log backup information of the new source tenant is complete.
- If the test passes, proceed to the next step.
- If the test fails, refine the relevant configuration as prompted on the page. After configuration, retest.
Click Save.
Confirm whether the primary and standby logs are consistent. If they are, click Change.
Related operations
In the topology diagram, you can perform the following adjustments:
- Drag the mouse in the blank area to freely move the topology diagram.
- Click the zoom-in/zoom-out icon or scroll the mouse wheel up and down to zoom in or out on the topology diagram.
- Click
to quickly restore the topology diagram to its original scale. - Click
to allow the topology diagram to dynamically adapt to the canvas size.