Server Management - Systems Insight Manager
1832541 Members
6237 Online
110043 Solutions
New Discussion

SIM 5.0 Failover Architecture

 

SIM 5.0 Failover Architecture

I've searched and found a thread on doing failover with 4.2. It answered some things, but not everything.

I'll have 2 sites, each with a CMS front end connecting to a SQL farm. There will be a SQL farm at each site.

I think I understand regarding security certificates--each managed server will need a certificate from each SIM server.

1. Install SIM 5 at each site. Disable the SIM services at the secondary site and optionally delete the database
2. Configure the primary site and start managing servers
3. Enable SQL log shipping between primary and secondary, optionally creating the database on the secondary

Now the question is, what non-SQL based configuration data must be replicated or copied to the secondary server so when the SIM services are started, we are up and running?

Thanks---Drew
2 REPLIES 2
Rob Buxton
Honored Contributor

Re: SIM 5.0 Failover Architecture

The Certificates are the key, but each Server can have both.

But for our DR, I've configured HPSIM there to just include the DR Servers, not everything else.
In that way it exists as a separate entity.

You could restore the HPSIM Database from your live setup if you wanted access to historical material.

The one thing I know only works from a single HPSIM instance is VMM. So if you're using VMM to manage Virtual Servers you'll need to Unregister / register servers.

Re: SIM 5.0 Failover Architecture

I am looking at our dev server now; the config directory looks like one to replicate, but there are many subdirectories underneath. Anyone replicating this directory between servers--seems that would be important, assuming most of the config data is here instead of SQL.

Thanks--Drew