Dynamics Community Forum Thread Details

Management Reporter 2012 on a Failover Cluster

Hello:

A Management Reporter 2012 CU15 user plans on creating a new environment where there is a failover cluster.

This cluster will contain two boxes, or two application servers - "DB1" and "DB2".

I want to know if this is the best practice, for installing and configuring Management Reporter in a failover cluster:

(1) The end user installs Management Reporter Server on DB1 and DB2,

(2) The end user accesses the Management Reporter Client on the client boxes ensuring that Tools...Connection points to DB1,

(3) If DB1 goes down, the end user once again accesses the Management Reporter Client on the client boxes ensuring that Tools...Connection, instead, points to DB2.

Again, is this the best practice in a failover cluster?

If not, please let me know the best practice.

Thank you!

John

Hi John,

From my experience i installed the Management reporter server on a separate server (application server in my case) and of coarse all the clients machines would be setup to connect on that Management reporter server.

- the Management reporter server will be setup to look on either of the databases ( like to DB1 in your case)

- in case of Failover you will have to only switch servers from the management reporter server to DB2

FYI if you installed two Management reporter servers on each database server, if failover happens you will have to modify each client to look at the other Management reporter server, if you got a lot of clients that would take time.

so i will suggest the solution i made for easier modification if Failover happens.

Regards,

Quick Links

Leaderboard