To protect the Directory database so you do not lose any data if a failover occurs, you can set up Directory database failover to use Microsoft SQL Server Database Mirroring.
Before you begin
- Microsoft Database Mirroring is being phased out. For new installations, it is recommended to use SQL AlwaysOn.
- The Principal database server, the Mirror database server, and the Witness server (the Witness server is optional, but highly recommended) must be configured. For the configuration of SQL Server for mirroring, please refer to Microsoft SQL Server Database Mirroring documentation.
- Your Security
Center license must support
multiple Directory servers. If you need to update
your license, see the Security
Center
Installation and Upgrade Guide.NOTE: The Directory Manager (
) role is
created automatically in Config
Tool when
your license supports multiple Directory servers. - The database servers must be running on remote computers from the Directory servers. Move the databases to other computers.
- All database servers must be accessible from all Directory servers. You must configure the remote database server (SQL Server) to accept connection requests from the roles.
- The Principal and the Mirror databases must be of the same version. For more information on database mirroring, such as how to perform manual backup and restore, refer to the Microsoft SQL Server Database Mirroring documentation.
What you should know
NOTE: Following a database failover, the
first database query performed by Security
Center
client applications are likely to fail. When a query fails, the message "Database
transaction has failed" appears on screen. Close the message box and try again to resume
normal operation.
To use Database Mirroring as your Directory database failover solution:
-
Select the Directory Manager () role, and click the Database failover
tab.
