Dialogic® ControlSwitch™
Disaster Recovery User’s Manual
Release 5.11.1
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 2
Copyright and Legal Notice
Copyright © 2015-2016 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission
in writing from Dialogic Corporation at the address provided below.
All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a
commitment on the part of Dialogic Corporation and its affiliates or subsidiaries (“Dialogic”). Reasonable effort is made to ensure the accuracy
of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept
responsibility for errors, inaccuracies or omissions that may be contained in this document.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED
AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR
IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS
FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in certain safety-affecting situations. Please see
http://www.dialogic.com/company/terms-of-use.aspx for more details.
Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries,
and thus may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the
countries where such use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on
the web at www.dialogic.com.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing
collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by
third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such
product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a
signed agreement with Dialogic. More detailed information about such intellectual property is available from Dialogic’s legal department at
6700 Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Dialogic encourages all users of its
products to procure all necessary intellectual property licenses required to implement any concepts or applications and does not condone or
encourage any intellectual property infringement and disclaims any responsibility related thereto. These intellectual property licenses may
differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with
different national license requirements.
Dialogic, Dialogic Pro, Dialogic Blue, Veraz, Brooktrout, Diva, BorderNet, PowerMedia, PowerVille, PowerNova, MSaaS, ControlSwitch, I-Gate,
Mobile Experience Matters, Network Fuel, Video is the New Voice, Making Innovation Thrive, Diastar, Cantata, TruFax, SwitchKit, Eiconcard,
NMS Communications, SIPcontrol, Exnet, EXS, Vision, inCloud9, NaturalAccess and Shiva, among others as well as related logos, are either
registered trademarks or trademarks of Dialogic Corporation and its affiliates or subsidiaries. Dialogic's trademarks may be used publicly only
with permission from Dialogic. Such permission may only be granted by Dialogic’s legal department at 6700 Cote-de-Liesse Road, Suite 100,
Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Any authorized use of Dialogic's trademarks will be subject to full respect of the
trademark guidelines published by Dialogic from time to time and any use of Dialogic’s trademarks requires proper acknowledgement.
The names of actual companies and products mentioned herein are the trademarks of their respective owners.
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open
source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present
or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property
rights.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 3
Document History
Revision
Release date
Notes
01
June 2012
Release 5.9.0 – Initial version
01
Dec. 2015
Release 5.10.2 – editorial and styles
1.0
June 2016
Release 5.11.1
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 4
Table of Contents
INTRODUCTION ............................................................................................................................................ 6 1.
1.1 Purpose of this Document........................................................................................................................... 6
1.2 Glossary ....................................................................................................................................................... 6
1.3 Contact Us ................................................................................................................................................... 6
OVERVIEW .................................................................................................................................................... 7 2.
2.1 Description and Operational Steps ............................................................................................................. 7
2.2 Database Synchronization ........................................................................................................................... 7
DISASTER RECOVERY METHODS ................................................................................................................... 9 3.
3.1 Switchover ................................................................................................................................................... 9
3.2 Failover ........................................................................................................................................................ 9
EMS Failover Causes ............................................................................................................................... 9 3.2.1
Failover Decision ................................................................................................................................... 10 3.2.2
3.3 Terminologies ............................................................................................................................................ 10
CS-BORDERNET INTEGRATED SYSTEMS ....................................................................................................... 11 4.
REQUIREMENTS AND PERFORMANCE ......................................................................................................... 12 5.
5.1 Platform Requirements ............................................................................................................................. 12
5.2 System Performance ................................................................................................................................. 12
PROVISIONING ............................................................................................................................................ 13 6.
6.1 Installation ................................................................................................................................................ 13
User Interface ....................................................................................................................................... 13 6.1.1
6.2 Site Preparation ........................................................................................................................................ 13
Preparing the Standby Database .......................................................................................................... 13 6.2.1
Creating Database Backup .................................................................................................................... 14 6.2.2
Transferring Backup to Standby Host ................................................................................................... 15 6.2.3
Restoring Backup on Standby Host ....................................................................................................... 16 6.2.4
Configuring Database on Remote Site as Standby ................................................................................ 16 6.2.5
Restarting Secondary EMS .................................................................................................................... 17 6.2.6
6.3 Monitoring the Databases......................................................................................................................... 17
Data Guard Status ................................................................................................................................. 17 6.3.1
Brief Data Guard Information ............................................................................................................... 18 6.3.2
Detailed Data Guard Information ......................................................................................................... 19 6.3.3
Checking Switchability of Standby Host ................................................................................................ 19
6.3.4
6.4 Graceful Switchover .................................................................................................................................. 20
Shutting Down Processes on the Primary EMS ..................................................................................... 21 6.4.1
Performing Database Role Switch ........................................................................................................ 21 6.4.2
Starting Processes on Active Secondary EMS ....................................................................................... 23 6.4.3
GUI Test on Secondary EMS .................................................................................................................. 24 6.4.4
Switching Back to the Primary EMS ...................................................................................................... 24 6.4.5
Starting the Processes on the Active Primary EMS ............................................................................... 26 6.4.6
GUI Test on Primary EMS ...................................................................................................................... 26 6.4.7
6.5 Failover ...................................................................................................................................................... 27
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 5
Failover to Secondary EMS ................................................................................................................... 27 6.5.1
Starting the EMS ................................................................................................................................... 29 6.5.2
GUI Test on Secondary EMS .................................................................................................................. 29 6.5.3
6.6 Failback Procedures .................................................................................................................................. 29
Un-configuring Standby Database ........................................................................................................ 29 6.6.1
Creating Database Backupset ............................................................................................................... 30 6.6.2
Transferring Backupset to Standby Host .............................................................................................. 31 6.6.3
Restoring Backupset on Standby Host .................................................................................................. 32 6.6.4
Configuring Database on Remote Site as Standby ................................................................................ 32 6.6.5
Switching Back to the Primary EMS ...................................................................................................... 33 6.6.6
Starting Processes on the New Active EMS .......................................................................................... 34 6.6.7
GUI Test on Primary EMS ...................................................................................................................... 34 6.6.8
EMS DISASTER RECOVERY LOGS .................................................................................................................. 35
7.
7.1 Setup Remote ............................................................................................................................................ 35
7.2 Test Remote Connection ........................................................................................................................... 36
7.3 Create Database Backupset ...................................................................................................................... 36
7.4 Remote Copy Backupset ........................................................................................................................... 38
7.5 Restore Standby Database ........................................................................................................................ 39
7.6 Configure Database as Standby ................................................................................................................ 41
7.7 Show Status ............................................................................................................................................... 42
7.8 Display Configuration (Brief) ..................................................................................................................... 42
7.9 Display Configuration (Detail) ................................................................................................................... 43
7.10 Check Standby State .................................................................................................................................. 46
7.11 Remove Configuration .............................................................................................................................. 46
7.12 Recovery Switch to Standby ...................................................................................................................... 47
7.13 Failover ...................................................................................................................................................... 49
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 6
Introduction 1.
1.1 Purpose of this Document
This document provides detailed information on the disaster recovery capability, and its provisioning
guidelines on the ControlSwitch System (CS).
1.2 Glossary
For the purposes of this document the following abbreviations apply:
Term
Abbreviation
CS
ControlSwitch
1. EMS
2. Element Management System
Table: Glossary
1.3 Contact Us
For a list of Dialogic locations and offices, please visit: https://www.dialogic.com/contact.aspx.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 7
Overview 2.
2.1 Description and Operational Steps
The CS is managed by ONE Element Management System (EMS). The Disaster Recovery solution
provides a mechanism to failover the EMS, in case of unavailability or error, to another EMS. For the
Disaster Recovery capability to function, two EMS elements are needed: primary EMS (active and in
normal condition), and secondary EMS (standby - activated manually by the operator)
Note:
The Disaster Recover solution is not a High Availability (HA) solution.
The following lists the solution's major steps:
Installation and configuration of two EMS platforms (including software and databases).
Duplication of the primary EMS database, to the secondary EMS database.
Setting the secondary EMS to standby mode. The Data Guard mechanism transfers the modified
data from the primary EMS database and to the secondary EMS database (keeping it updated).
Manually running the scripts on the standby platform to bring it to an active state, when the active
EMS fails. During the failover the database completes its update from the primary EMS database, up
to the last transaction.
When the standby EMS turns active, the operator may rebuild the database on the failed EMS, and
to switch back to the recovered primary EMS, by:
Shutting down the secondary EMS, and disabling its processes
Invoking scripts to switch active database from the secondary to primary EMS
Bringing up and enabling the elements on the primary EMS. As the switchover operation takes
a matter of minutes no data loss should be experienced.
Note:
For a successful switchover, both platforms must have an identical time, and the same release and patch release.
Switchover may also be used for system maintenance or dry switchover testing.
The standby database recovery states, and the connectivity state between the two EMS elements shall
be displayed on the Alarms window.
2.2 Database Synchronization
The Oracle RDBMS release 11.2 Data Guard is used to handle the database synchronization between the
primary and the secondary EMS platforms.
The primary (active) and secondary (standby) databases are physically identical. Data synchronization
from the active to the standby database is performed by the redo logs, including online logs, standby
logs, and archived logs. The following diagram shows the database synchronization between the two
EMS platforms.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 8
Figure 1: Database Synchronization
The data is stored in the primary EMS Oracle database, and when the secondary EMS is setup, it
continuously receives the provisioning and data modifications from the primary EMS.
Data changes from the primary EMS database transactions are transferred to the secondary EMS in a
timely manner to minimize data loss. Data changes on the primary EMS are applied to the secondary
EMS when the logs are available to reduce the system's recovery time.
After recovery and when the primary EMS and the database have been rebuilt, there will be no data loss
during the switching back operation to the primary EMS, as a result of a short down-time.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 9
Disaster Recovery Methods 3.
Disaster Recovery offers the following two methods to handle both the planned and the unplanned
outages in a production site:
Switchover
Failover
3.1 Switchover
Switchover is a reversal between the active and standby databases, commonly used to handle a planned
maintenance on the production database.
The main difference between the switchover and the failover operations is that the switchover is
performed when the active production database is still available. The switchover does not require re-
instantiation of the database. This allows the active production database to assume the role of a
standby database within a matter of minutes (typically in 5 to 10 minutes). As a result, a scheduled
maintenance is performed easily. As an example, switchover may be used to perform an upgrade on the
primary site by switching over all the database clients to standby during the hardware upgrade.
3.2 Failover
Failover allows the operator to set the active production database to offline, and the standby database
to online, as the new active database.
A failover operation is invoked when an unplanned failure occurs on the active production database,
and there is no possibility for recovery in a timely manner.
In the failover operation the standby database takes the active role when disaster situations occur. In
EMS Disaster Recovery, the choice of the Maximum Performance mode, when setting up the standby
environment, does not prevent data loss during the failover operation.
Note:
After a failover, the original active database on the primary EMS (now the standby) must be re-instantiated using the new
active database on the standby EMS to assume its new role as a standby database. Precautions should be taken to consider the
Disaster Recovery as the one of the last resorts for data recovery.
There is no automatic failover from the secondary to the primary EMS. The operator needs to perform a
graceful fallback from the secondary to the primary EMS.
EMS Failover Causes 3.2.1
Examples of failover causes are as following:
The EMS became unavailable due to local site disasters such as fire, flood, or larger scale regional
natural disasters
The site hosting the EMS experienced extensive power outages and could not be restored in a
reasonable time
The EMS experienced a major hardware failure such as:
Bad CPU or memory
Broken disk controllers
Disk storage failure with no mirrored copy available
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 10
Redundant network interfaces were not accessible
The EMS major components were do not function because of a file system failure that cannot be
easily repaired
The EMS DB is corrupted and not operational, as a result of corruption or loss of data files, Redo
Logs and control files
Failover Decision 3.2.2
The operator makes the decision to failover, invoking the following operations on the standby EMS:
Apply the remaining transactions from the standby Redo Log to the standby database
Stop the managed recovery mode for the standby database
Force the standby database open to accept connections and transactions
Enable the startup scripts for EMS components and start the components
3.3 Terminologies
Active (state) - EMS/database that is currently the primary platform
Standby (state) - EMS/database that is not currently the primary platform
Primary (designation) - When an EMS is installed, one system is considered as Primary (typically this
is also the active EMS/database)
Secondary (designation) - When an EMS is installed one system is considered as Secondary (typically
this is also the Standby EMS/database)
In a disaster condition, the operator decides to failover to the secondary standby EMS. Figure 2 shows
the secondary platform's take over after a failover. Upon the primary EMS recovery, the secondary EMS
remains active until the operator switches over from the secondary to the primary EMS.
Figure 2: Failover
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 11
CS-BorderNet Integrated Systems 4.
If the CS is integrated with a BorderNet 4000 Session Border Controller (SBC), the CS information must
be re-sent to the SBC after the switchover/failover, even if the status of the failed EMS is displayed as
Success in the BorderNet configuration window.
→ To push the CS information to the SBC:
1. Select SBC BorderNet (Bnet)/Access Points (BNAP). The following window opens:
2. Select an SBC.
3. Click on the Send EMS Info button.
4. Repeat the steps 2 and 3 for all the involved SBCs.
5. Check the result of the Provisioning Status in the CS (applicable when DR EMS is deployed).
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 12
Requirements and Performance 5.
5.1 Platform Requirements
The following lists the disaster recovery requirements:
Primary and Secondary EMS platforms with the same or similar configurations.
A high-speed network interface and sufficient bandwidth between the two platforms for efficient
data transport.
Sufficient disk space for archive/backup directories for active and standby EMS platforms.
5.2 System Performance
The following tables provide disaster recovery performance, based on the following assumptions:
T1 = 1.54 Mb/s
T3 = 45 Mb/s
Compression rate = 4:1 for initial database copy
Each redo log size = 10 MB
3. Initial DB Copy
Size Compressed
T1
T3
4. DB Size 2 GB
5. 500 MB
6. 0.9 hours
7. 2.5 minutes
8. DB Size 4GB
9. 1 GB
10. 1.8 hours
11. 5 minutes
12. DB Size 8 GB
13. 3 GB
14. 3.6 hours
15. 10 minutes
Table 1: Redo log Transfer Performance Estimation
16. Redo Log Generate
Redo Logs
17. Typical data load
18. 1/5 minutes = 10 MB/300 seconds = 300 kb/s < T1
19. Light data load
20. 1/2 minutes = 10 MB/120 seconds = 0.8 MB/s < T1
21. Medium data load
22. 1/1 minutes = 10 MB/60 seconds = 1.5 MB/s = T1
23. Heavy data load
24. 1/30 seconds = 10 MB/30 seconds = 3 MB/s > T1
Table 2: Ongoing Log Transfer
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 13
Provisioning 6.
This chapter provides detailed procedures on the disaster recovery provisioning for switchover and
failover modes.
6.1 Installation
The disaster recovery setup is performed as a part of the CS installation. Please refer to ControlSwitch
Installation Guide for details.
User Interface 6.1.1
The EMS disaster recovery main menu provides access to all the disaster recovery functions, as depicted
in the figure below:
6.2 Site Preparation
Site preparation should be performed only once. When the standby database configuration is
completed, this step should not be repeated.
→ For site preparation:
1. Shutdown the secondary EMS applications:
Log into the secondary EMS as root.
Execute:
# /etc/init.d/stopems
2. Prepare the standby database.
3. Create the database backup.
4. Transfer the backup to the standby host
5. Restore the backup on standby host
6. Configure the database on the remote site as standby
7. Restart the secondary EMS
Preparing the Standby Database 6.2.1
Ensure that the EMS modules are down, excluding the database.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 14
→ To prepare the standby database:
1. Login to the primary EMS as oracle:
# su - oracle
2. Execute:
# /opt/IPVRdbut1/dataguard/mainmenu.sh
The EMS Disaster Recovery main menu window opens:
3. Enter 1 or I to select Standby Database Instantiation. The Setup Menu opens:
4. Enter 2 or N to check network connectivity. Expected Results:
Test network configuration completed successfully
Remote host 'jangle' has been chosen
See Test Remote Connection for the log example.
5. Enter 0 or Q to return to the Disaster Recovery Main menu.
Creating Database Backup 6.2.2
Note:
This operation may take between 5 -10 minutes, depending on the database.
Prior to starting this operation, archive Log mode, for the database on the primary EMS, needs to be
enabled.
→ To create a database backup:
1. From the EMS Disaster Recovery Main menu enter 1 or I. The Setup Menu opens:
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 15
2. Enter 3 or B to create a database Backup. Expected results:
An example of this log is available in Create Database Backupset.
3. Enter 0 or Q to return to the Disaster Recovery Main menu.
Transferring Backup to Standby Host 6.2.3
Note:
The time for a database transfer depends on the database size and network bandwidth. For example, large database transfer
over a T1 can take hours. Transfer over T3 is faster. Please refer to Table 1 for details.
→ To transfer backup to remote standby host:
1. From the Disaster Recovery Main menu enter 1 or I. The Setup Menu opens:
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 16
2. Enter 4 or T to transfer backup to the remote standby host. Expected results:
Backupset transfer completed successfully
An example of this log is available in Remote Copy Backupset.
3. Enter 0 or Q to return to the Disaster Recovery Main menu
Restoring Backup on Standby Host 6.2.4
Note:
A database restore takes between 5-10 minutes.
→ To restore transferred backupset on remote standby host:
4. From the EMS Disaster Recovery Main menu enter 1 or I. The Setup Menu opens:
5. Enter 5 or R to restore transferred backupset on the remote standby host. Expected results
Backupset restore completed successfully
An example of this log is available in Restore Standby Database.
6. Enter 0 or Q to return to the Disaster Recovery Main menu.
Configuring Database on Remote Site as Standby 6.2.5
→ To configure the database on the remote site as standby:
1. From the EMS Disaster Recovery Main menu enter 1 or I. The Setup Menu opens:
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 17
2. Enter 6 or C to configure the database on the remote site as standby. This action shuts down
the host. To continue enter y. Expected results
Dataguard configuration has been created successfully
Dataguard setup completed successfully
An example of this log is available in Configure Database as Standby.
3. Enter 0 or Q to return to the Disaster Recovery Main menu
Restarting Secondary EMS 6.2.6
After the initial database configuration the secondary EMS should be restarted.
→ To restart the secondary EMS:
1. To reboot secondary EMS as root:
init 6
Expected Results: None of the processes except the database (standby mode) comes up.
6.3 Monitoring the Databases
This section describes the monitoring procedures that can be carried out at any time.
Data Guard Status 6.3.1
→ To display the Data Guard status:
1. Log on to the connected EMS as oracle:
# su - oracle
2. Execute:
# /opt/IPVRdbut1/dataguard/mainmenu.sh
The EMS Disaster Recovery Main Menu is displayed.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 18
3. From the EMS Disaster Recovery Main Menu enter 2 or S. The Status Menu opens.
4. Enter 1 or S to view a Data Guard status table. Expected results:
The system checks the data guard configuration status and displays it in a table format. For a
detailed explanation of this log refer to Show Status.
5. Enter 0 or Q to return to the Disaster Recovery Main Menu.
Brief Data Guard Information 6.3.2
→ To view a brief Data Guard status on the EMS:
1. From the EMS Disaster Recovery Main Menu enter 2 or S. The Status Menu opens.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 19
2. Enter 2 or B to select a brief list of Data Guard configuration details. Expected results
Dataguard configuration has been displayed successfully
Display configuration completed successfully
Refer to Display Configuration (Brief) for a sample log.
3. Enter 0 or Q to return to the Disaster Recovery Main Menu.
Detailed Data Guard Information 6.3.3
→ To view a detailed Data Guard status on the secondary EMS:
1. From the EMS Disaster Recovery Main Menu enter 2 or S. The Status Menu opens.
2. Enter 3 or D to select a detailed list of Data Guard configurations. Expected results:
Dataguard configuration has been displayed successfully
Display configuration completed successfully
Please refer to Display Configuration (Detail) for a sample log.
3. 3. Enter 0 or Q to return to the Disaster Recovery Main menu.
Checking Switchability of Standby Host
6.3.4
→ To check switchability of any host:
1. From the EMS Disaster Recovery Main menu enter 2 or S. The Status Menu opens.
ControlSwitch (v.5.11.1) Disaster Recovery User’s Manual
Dialogic Inc. Proprietary Page 20
2. Enter 4 or C to check switchability of the standby host. Expected results:
Please refer to Check Standby State, for a sample log.
3. Select 0 or Q to return to the Disaster Recovery Main menu.
6.4 Graceful Switchover
→ To gracefully switchover between the primary and the secondary EMS hosts:
Before Database switchover:
1. Stop processes on the active EMS
2. Perform Database role switch
3. Perform Database switch on the active EMS
After switchover:
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/