topic Re: Windows CMS failover solution in Server Management - Systems Insight Manager

Windows CMS failover solution

ms.tim — Sat, 02 Apr 2005 04:32:34 GMT

is it possible to configure SQL log shipping from primary to secundary CMS and by that have exact data on secundary (backup) server as in at primary server?
managed systems would be configured like this:
1. deliver snmp traps to dns alias, which in failover situation would be edited to point to the secundary server;
2. discovery & identify would be done on both servers
3. trusts would be set for both servers - certificates of both CMS's copied to managed systems and managed systems certificates copied to both CMS's

does anybody else has something to add?
CMS is a Windows 2000 Advanced Server + SP4 with MS SQL 2000 EE + SP3a

tnx in advance

Re: Windows CMS failover solution

ms.tim — Sun, 03 Apr 2005 03:43:20 GMT

after a good night sleep :) figured it out that SIM is almost cluster aware. in manuals is stated that SIM has to be installed on both nodes but the database is on shared storage device, so, if log shipping is configured it is the same thing, the databases are the same.
I just node the confirmation, or not, for my thoughts.
the only thing that worries me are the database names.

Re: Windows CMS failover solution

David Claypool — Mon, 04 Apr 2005 09:18:07 GMT

This might help: "Deploying HP Systems Insight Manager 4.2 on MSCS Clusters" from http://www.hp.com/go/hpsim --> Information Library

Re: Windows CMS failover solution

Thomas Jönsson — Tue, 05 Apr 2005 01:40:20 GMT

The labguide in the course "Implementing MS Windows Server 2003 on HP ProLiant Cluster Solutions v4.41" (22577D) descibes exactly how to set up a CMS in a Windows Cluster with SQL on one node and CMS on the other node as default.

The course material for this course is downloadable for free if you are HP certified.

Re: Windows CMS failover solution

ms.tim — Tue, 05 Apr 2005 13:16:06 GMT

I am not deploying on MSCS environment.
I just stated that if I am deploying on MSCS environment then CMS's are installed on both nodes, database is on shared storage and SIM services on secundary node are stoped.
If I have 2 servers (one in primary data center and other in backup data center) I would need to install CMS on both nodes, SQL on both nodes, stop SIM services on secundary server and configure log shipping from primary to secundary server.
In that case I would have the same thing, right?