{"id":12841,"date":"2017-12-05T03:26:27","date_gmt":"2017-12-05T03:26:27","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=12841"},"modified":"2022-03-01T13:17:52","modified_gmt":"2022-03-01T20:17:52","slug":"planning-to-setup-dr-disaster-recovery-servers","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/planning-to-setup-dr-disaster-recovery-servers\/","title":{"rendered":"Setup a Disaster Recovery Server"},"content":{"rendered":"
This page presents important points to address when planning disaster recovery.<\/p>\n
A database should have high availability, which can be implemented by MSSQL Always On<\/strong> feature. The database should also have the capability to replicate data from one database server to another in a two-way fashion to prevent creating any data inconsistencies. Your main database server should have updated records of whatever is processed in your DR server (this is usually handled by High Availability where MSSQL internally decides which node acts as a primary & secondary node) so that there are no database inconsistencies.<\/p>\n There will be a separate license provided for the DR Server with a private MAC address and image count limit. The DR server is not intended to be used as a part of the main cluster.<\/p>\n The failover from the main cluster to the DR server requires manual intervention. Make sure that database and shared folders are fully replicated before failing over to DR servers.<\/p>\n","protected":false},"featured_media":0,"parent":23605,"menu_order":7,"comment_status":"closed","ping_status":"open","template":"","doc_tag":[],"yoast_head":"\nLicensing<\/strong><\/h3>\n
Execute DR Failover<\/strong><\/h3>\n