Source = W2K8 server running OpsCenter 8.1
Target= W2k16 server running OpsCenter 8.1 And a new hostname
I followed a slightly different approach as I didn't want to have an issue because of the name
Hope that helps
I did pretty much the same as Riaan, except I didn't copy the additonal folders - I just did an OpsCenter upgrade to highest version on 2012 R2, then did a DB backup, shutdown old VM, build new VM on Win2016, same name same IP same domain, install same version of OpsCenter, restore DB, all ok.
Hi bunsen82, Opscenter server has a config file ,db.conf that keeps the name of the Opscenter server . So if you recover the opscenter database , this file will be overwriten .So if the original server is ‘sourceopscenter’ , file will have opscenter server name as ‘sourceopscenter’ and if the new server name is ‘destinationserver, the restore will overwrite the server name from ‘destinationserver’ to ‘sourceopscenter . Please check the name of opscenter server in this file .
If we have wrong name here , opscenter server will not be able to access the database server , even though all the service are running .