How to setup a synchronously Mirrored Database
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
To guarantee maximum resilience, it is possible to deploy two separate database servers. At this, only one database server is connected to the DLS (single node or cluster), while the data are mirrored on the other server. In case the main server ("Principal") fails, the second server ("Mirror") assumes its function. For database mirroring, two models are supported:
- Synchronous Mirroring: A third server ("Witness") monitors the state of the main server. If the Principal should fail, the Witness will switch over to the Mirror, which will hereby become the Principal. Moreover, the Witness checks whether all transactions have been completed on the Mirror, too. Thus it is ensured that no data loss will occur. However, the performance will be slightly lower than with asynchronous mirroring.
- Asynchronous Mirroring: There is no Witness, and the switchover to the mirror server is done by "Forced Service", i. e., by the DLS.
The following requirements must be fulfilled for database mirroring:
- Microsoft SQL Server Enterprise Edition with latest Service Packs is installed on all servers needed for database mirroring (Principal, Mirror and Witness, where applicable).
- Microsoft SQL Server Management Studio has to be installed.
- At least the first DLS node should be installed because mirroring can be set up only for a DLS database that has already been set up. This is part of the installation process for the first DLS node.
- The service DeploymentService is stopped on all participating DLS nodes.
- For the DLS database (DLSdb), the recovery model "Full" is set.
- The size for the TransactionLog is unlimited.