HP SIM 5.3 Replication

[Tobie Joeckel]

I have 2 SIM CMS boxes (1 primary, 1 backup/contingency). Is there a way to implement data redundancy or replication between the two so that all configurations, settings, managed servers, groups, etc. from and done to primary would trickle down to the secondary? They are also VC boxes. Thanks!

[David Claypool]

The only documented and supported methods are with Microsoft Cluster Services on Windows and Serviceguard on Linux/HP-UX.

[Tobie Joeckel]

Ok, thanks. I thought I recalled a way in which to setup a new CMS box by importing all settings and such from another one, is that correct? Essentially, I've landed in a role where these 2 boxes already existed, but they aren't in synch as far as alarming, managed server collections, etc...I'd like to get that in line. I can still use them independently and have the managed boxes send traps to both, then manage them forward, but in the meantime, I'd prefer not to have to go through every managed box, setting, config, etc. to get there. Thanks again!

[Tobie Joeckel]

*bump*

Still curious if this can be accomplished. I would even settle for not maintaining the historical data (if that had to be the case), but still being able to import all config settings, event handling settings, system / event collections. Any thoughts on how I can stand up a new SIM 5.3 instance and import all data from another one?

[Rob Buxton]

HPSIM 6.0, due very soon seems to have a utility that will let you copy all of the settings across to a new server.
HP SIM 6.0 is, according to the HP web site, due in January 2010.
As regards historical data, that will remain. You can leave the old database intact and access the historical data via standard SQL queries.