While I don't think we've done the exact case, our FoE product relies on being able to do a P2V(or Backup/Restore) to accomplish the initial push. I was talking with another dev, and the only thing we were worried about was the licensing, and we both felt things should be fine for a straight P2V. In the worst case, park the keys from the old machine, and re-license after doing the the P2V.
In terms of DB stuff, there shouldn't be anything you need to do. While you can run SQL Express, I would highly recommend getting it off to a dedicated server ASAP. If you move it to the dedicated server before the P2V, it should continue to run on the VM without a problem once you bring it up.
I'm curious to hear if folks have done this in their environments and how it went.
It would be great to get some solid answers on this but as an extra question to migration but slightly off the P2V line; if we were forced to build new server and reinstall products fresh on new server, how much tailoring is lost ? IE how information is stored in DBs and would be maintained. I imagine any EOC Web page customisation would be lost ? Atlas MAPS i believe are now all in DB? What would be lost with this upgrade process.? Appreciate any past experience.
Orion Core 2011.2.2, NCM 6.1, NPM 10.2.2, IVIM 1.2.0
1 of 1 people found this helpful
this document about NPM Server migration may not answer 100% of your questions, but still should be useful for you - http://www.solarwinds.com/documentation/orion/docs/OrionServerMigration.pdf