A database should have high availability, which can be implemented with the Microsoft SQL Always On feature. The database should also have the capability to replicate data from one database server to another in a two-way fashion to prevent 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 Microsoft SQL internally determines which node acts as a primary and secondary node) so that there are no database inconsistencies.

A separate license is 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.

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.