- Take CMS database back up
- Check DR FRS path with same service account and check that account should have read and write access for that path.
- If it is possible then pauses all recurring reports which is on prod server otherwise it will get trigger as soon as you will start DR server, some of the will get fail coz FRS is different
Suppose we have 3 servers A, B, C. server A & B is production server and both server are in cluster. Server C is DR server.
Part I: – FAILOVER to DR HOST
- Go to Server A and stop all notification services like HAWK Agent.
- Go to CCM and stop SIA and Tomcat server
- logon to the server B and stop all notification services
- Go to CCM and stop SIA and Tomcat server.
- Now copy your FRS directory to DR FRS directory
- Failover your CMS database
- Take Database back up.
- Flip CNAME of DB instance from primary to DR
- Flip CNAME of managed application server host
- Now login to your DR server (server C)
- Start your notification services
- Go to CCM and create new SIA on CMS database
- Go to SIA properties to system account, use your service account which is same as your prod account.
- Start Tomcat and SIA
- Check the new FRS path is accessible with your service account and you have read and write access to that path.
- Now go to IFR server and Stop IFR server
- go to properties of IFR server and change Temporary Directory: and File Store Directory:
- Go to OFR server and Stop OFR server
- Go to properties of OFR server and change Temporary Directory: and File Store Directory:
- Start both the servers i.e. IFR & OFR server
- Now DR is fully activated.
Part II: – TESTING
- Run test report
- Communicate that testing has been completed and request failback procedures are invoked.
Note:- Don�t check reports based on Events coz it will not work or you need to change event server properties for events.
Part III: – FAILBACK to PRIMARY HOST
- Go to server C which is your DR server
- Stop notification services
- Stop SIA and tomcat
- Go to SIA properties change start up time to manual
- Go to SIA start up tab
- Select Local CMS server go to properties check auto start check box click on ok (after windows server restart, DR SIA will not come up and under cluster name.)
- Flip CNAME of database instance from DR to primary
- Flip CNAME of Managed application server host
- DBA to confirm data server is up and running and against appropriate back-end host.
- Now go to server A
- Start your SIA and then tomcat
- Start notification services on server A
- Follow the same steps for server B (step 7 to 9)
- Test some sample reports