Install HP SIM 7.6 as a fresh install using existing database

[P_H]

Current environment, HP SIM v7.6 on Windows Server 2008R2, database on SQL Server 2012.

This was upgraded from HP SIM v7.2 and SQL Server 2008 by upgrading to v7.3, then v7.5 and finally v7.6. The  database was then moved from SQL Server 2008 to SQL Server 2012. The system appears to be running fine, meeting expectations monitoring hundreds of Windows and Linux servers in a heavily virtualized environment.

The next step is getting to Windows Server 2012 and off Windows Server 2008.

We tried a fresh install of HP SIM v7.6 on WIndows Server 2012 with a different name and IP address which created a new HP SIM database. The fresh install was pointed to the previous database, but no tasks came across. The tasks were recovered by importing from  an export of tasks and changing the owners of the tasks. A couple event driven tasks could not be imported because the associated collections were not found. The lack of the event driven monitoring forced a fallback to the previous server, using the same database. Things are fine now back on tge Windows Server 2008.

Because of networking requirements with the new virtualization cluster, the new server must have a new IP address.

The new plan is to perform a mxexport on the existing Windows Server 2008, perform a fresh install of V7.6 on Windows Server 2012 to a new database, import the export from Windows Server 2008 and test with both systems active.. Once testing shows success, change the CNAME record for the trap ID and update systems with hardcoded trap IP addresses. and update firewall rules to reflect the new IP address/name. Then shut the Windows Server 2008 down..

Comments, suggestions, are these the right steps, what are we missing here, ANYTHING!? THANKS for your feedback.

[Andrew_Haak]

Please read the following PDF, and use it to point your new installation to the old database:

https://community.hpe.com/hpeb/attachments/hpeb/itrc-455/59388/1/SIM-db-migration.pdf

Page 22 point to all files to be edited. The file  hpsim-ds.xml is one that takes care of jobs an mutations in the database.

[P_H]

Andrew, THANK YOU for taking the time to respond.

Just to clarify, you would not suggest the method as described, export and then full import. Correct?

Instead you would recommend basically what we did, adding the editing of some additional configuration files.

Correct?

Thanks again

[Andrew_Haak]

Hello again,

The fast way is to do a new install and point to the old database. But if you don't have a lot of different server(types) you can also do an mxnode -ln > c:\nodes.txt and use this list to fill the new database. Both work just fine, i prefer the new setup way as it will create a new and clean database. The previous upgrades gave me some issues in the reporting fields. But if you don't use the reporting features you are free to choose.

[P_H]

Andrew,

Thanks again for all your comments and insight.

We did the process as the original documented, basically a fresh install, mxexport of the old guy and mximport into the new guy followed by the appropriate collections, queries, tasks running.

This seems to have worked pretty well. Version control doesn't seem to be able to phone home, but it cannot phone home on the old server either and this isn't seen as a show stopper, at least right now.

Again, thanks for your suggestions and support.

[Andrew_Haak]

Hello again,

If your VCA can't connect to the VCRM the SMH is probably not conpatible. You can downgrade the SMH or setup a seperate VCRM servet with an older SMH.

If you need more details let me know...

[P_H]

Please!

Any help getting VCRM to work is greatly appreciated!