Recording and other DB inserts use PMQ to persist that DB activity to disk. Once the DB is available again you can reprocess the PMQ files. This should avoid data loss.
I would recommend Always on Availability Group SQL cluster for production in one location and log shipping setup every 15 minutes to a DR DB in another georedundant location. In a true disaster recovery event where the prod DB is gone your risk is a max of up to 15 min of data loss.
You should test and document your steps for DR execution. Promote the DR DB to active, load the last log ship transactions, change DNS so CIC connects to the DR DB. Now you are back up and running. Reprocess PMQ.
------------------------------
Drew Drew Bisson
Chief Architect
Genesys - Employees
------------------------------
Original Message:
Sent: 11-12-2020 23:03
From: Chin Yaw Han
Subject: Protecting CIC Database and High Availability Options?
Hi all,
1. Currently with a standalone Database but often when the database is down and when you recover it back there are some possibility of data is lost and causing us not to recover and listen back to the recordings. The only way is to use the db transaction log plus the database backup to restore it. But no proper guide on how to do this. Not sure if anyone has such experience?
2. Working on a case where we like to proposed High Availability / Redundancy for Pureconnect not sure what are the common / recommended options? Cannot seems to find anything in the genesys portal. Appreciate if anyone can share some practise.
Regards,
Yaw Han.
#ArchitectureandDesign
------------------------------
Chin Yaw Han
------------------------------