How manually failover / failback Persistent chat Server (mgc) SQL database?
Basically Failover for Persistent Chat Server is designed to be mainly a manual process.
The failover procedure is based on the assumption that the secondary data center is up and running, but the Persistent Chat Server services where the primary Persistent Chat database is located are completely unavailable, including the following:
· Persistent Chat Server primary database and Persistent Chat Server mirror database are down.
· Lync Server Front End Server is down.
The procedure is based on two basic steps:
· Recover the primary Persistent Chat database (mgc).
· Establish mirroring for the new primary database.
The Persistent Chat compliance database (mgccomp) is not failed over. The contents of this database are transient and are purged as the compliance adapter processes the data. It is your responsibility, as Persistent Chat Administrator, to correctly manage the adapter output to avoid data loss.
Manually failover Persistent chat server database:
Assume that “mgc” Database is principal on Server-sql01 and mirror on Server-sql02 so it shows like below image.
However SQL server-sql02 is primary server hence failover mgc database manually to Server-sql02.
1. Log on to SQL Server > open SQL Management Studio > connect server / database.
2. Expand database.
3. Right click on “mgc” database and open properties.
4. Click on Mirroring > click on ‘Failover’
Once you click on failover you will you receive confirmation?
Then refresh database and see that mgc DB is running on principle instead of (Mirror, Synchronized / restoring…).