Switching deployment control from the main site console to the destination site console
When you activate the destination site, Ariel data synchronization and all Ariel copy profiles are disabled on the main site but services are not suppressed.
For the following scenarios, you can switch deployment control from the main site console to the destination site console.
An actual disaster recovery where the console is not available but the other deployment hosts are still running
When both the main and destination sites are active, all referenced managed hosts are in the Unknown state on the main site. This state occurs because the managed hosts are linked to the destination console during activation. Remove the managed hosts that are in the Unknown state from the main site before you run the failback operation on the main site.
After you activate the destination site and the main site is live, the pairing connection between both the sites is removed. To establish the pairing connection again, you must run the following pairing commands from both the sites:
- On the main site QRadar
Console,
run the following script:
/opt/ibm/si/dr/bin/dr_create_ssh.sh -i <destination_site_ip>
- On the destination site QRadar
Console, run the following script:
/opt/ibm/si/dr/bin/dr_create_ssh.sh -i <main_site_ip>
A disaster recovery exercise where the main site is still available during the disaster recovery process
- On the destination QRadar Console, click .
- Open the app menu and select Activate destination site.
- Click Activate and then confirm the activation.
The restoration process starts on the main site with the last backup that was transferred from the destination site. After the main site restoration, the destination site restoration starts with the last backup that was transferred from the main site.
- On the Admin tab on the main site and the destination site, click .
- On the main site QRadar
Console,
run the following script:
/opt/ibm/si/dr/bin/dr_create_ssh.sh -i <destination_site_ip>
- On the destination site QRadar
Console, run the following script:
/opt/ibm/si/dr/bin/dr_create_ssh.sh -i <main_site_ip>
- If apps are on the console, take the data backup of the apps by running the
app-volume-backup.py
backup script. Then, transfer the backup to the other console, initiate a failover or failback operation, and restore apps manually by running theapp-volume-backup.py
script. - If apps are on AppHost, move all installed apps to the console, and take a data backup of the
apps by running the
app-volume-backup.py
backup script. Then, initiate a failover or failback operation so that the AppHost moves from the main console to disaster recovery, and from disaster recovery to the main console, without apps. As a last step, restore apps manually by running theapp-volume-backup.py
script.
qappmanager
utility
(/opt/qradar/support/qappmanager
).