Network Management

Hi. Our customer is installing a new iMC server with the intention of migrating the old database to the new one. The DB server is SQL Server 2016, and the old iMC server is currently version 7.3 E0705P10.

We already installed the new server, and we have it currently at the same version so we can perform the database backup and restore before upgrading the new iMC to E0706, then to E0708, then to E0710.

Problem is... when I instructed them to run installslave.bat in the SQL server, it turned out it was already there, because the new database is hosted in the same SQL server as the old database. And I imagine I cannot have dbman pointing to both installations at the same time.

So how should we proceed now at this point?

Hi,

if you want to migrate an iMC server to a new machine, you first should set up a new database server for the new iMC. Please first upgrade the old iMC to the latest possible major version (E0710, the upgrade path you mentioned is correct, if you have additional modules, they also should be upgraded accordingly) and backup the database using dbman (the build-in utility in iMC). Install the new DB server, then install the new iMC server (same version as on the old one - 710) and restore from the backup from the old machine. Then you need to transfer the licenses to the new machine (it will get a new serial number). If you have difficulties in transferring the licenses using my networking portal, please open a case for the TAC to do it for you.

Please use the following document to migrate iMC correctly - HPE Intelligent Management Center Windows Migration Guide

Thank you,

Ivaylo

Hi. Our customer is installing a new iMC server with the intention of migrating the old database to the new one. The DB server is SQL Server 2016, and the old iMC server is currently version 7.3 E0705P10.

We already installed the new server, and we have it currently at the same version so we can perform the database backup and restore before upgrading the new iMC to E0706, then to E0708, then to E0710.

Problem is... when I instructed them to run installslave.bat in the SQL server, it turned out it was already there, because the new database is hosted in the same SQL server as the old database. And I imagine I cannot have dbman pointing to both installations at the same time.

So how should we proceed now at this point?

Thanks for the reply.

So, it is necessary to install a completely new SQL server? Is it not possible to use a different instance on the same server? Because I'm not sure it will be possible to ask the customer to deploy a new database server.

Hi,

if you want to migrate an iMC server to a new machine, you first should set up a new database server for the new iMC. Please first upgrade the old iMC to the latest possible major version (E0710, the upgrade path you mentioned is correct, if you have additional modules, they also should be upgraded accordingly) and backup the database using dbman (the build-in utility in iMC). Install the new DB server, then install the new iMC server (same version as on the old one - 710) and restore from the backup from the old machine. Then you need to transfer the licenses to the new machine (it will get a new serial number). If you have difficulties in transferring the licenses using my networking portal, please open a case for the TAC to do it for you.

Please use the following document to migrate iMC correctly - HPE Intelligent Management Center Windows Migration Guide

Thank you,

Ivaylo

Hi. Our customer is installing a new iMC server with the intention of migrating the old database to the new one. The DB server is SQL Server 2016, and the old iMC server is currently version 7.3 E0705P10.

We already installed the new server, and we have it currently at the same version so we can perform the database backup and restore before upgrading the new iMC to E0706, then to E0708, then to E0710.

Problem is... when I instructed them to run installslave.bat in the SQL server, it turned out it was already there, because the new database is hosted in the same SQL server as the old database. And I imagine I cannot have dbman pointing to both installations at the same time.

So how should we proceed now at this point?

Hi,

you can use separate instance on the same database server, but you need to use different ports (for each instance). Attached you will find a configuration guide, how this can be accomplished.

Thank you,

Ivaylo

Thanks for the reply.

So, it is necessary to install a completely new SQL server? Is it not possible to use a different instance on the same server? Because I'm not sure it will be possible to ask the customer to deploy a new database server.

Hi,

if you want to migrate an iMC server to a new machine, you first should set up a new database server for the new iMC. Please first upgrade the old iMC to the latest possible major version (E0710, the upgrade path you mentioned is correct, if you have additional modules, they also should be upgraded accordingly) and backup the database using dbman (the build-in utility in iMC). Install the new DB server, then install the new iMC server (same version as on the old one - 710) and restore from the backup from the old machine. Then you need to transfer the licenses to the new machine (it will get a new serial number). If you have difficulties in transferring the licenses using my networking portal, please open a case for the TAC to do it for you.

Please use the following document to migrate iMC correctly - HPE Intelligent Management Center Windows Migration Guide

Thank you,

Ivaylo

Hi. Our customer is installing a new iMC server with the intention of migrating the old database to the new one. The DB server is SQL Server 2016, and the old iMC server is currently version 7.3 E0705P10.

We already installed the new server, and we have it currently at the same version so we can perform the database backup and restore before upgrading the new iMC to E0706, then to E0708, then to E0710.

Problem is... when I instructed them to run installslave.bat in the SQL server, it turned out it was already there, because the new database is hosted in the same SQL server as the old database. And I imagine I cannot have dbman pointing to both installations at the same time.

So how should we proceed now at this point?