we don't offer official migration tool for IPAM but you may the following scenarios:
- Backup your existing NPM Database - please read this how to do that: http://www.solarwinds.com/support/Orion/docs/MovingYourOrionNPMDatabase.pdf
- Install IPAM 3.0 on the NPM server.
- Copy the file "…\SolarWinds\Orion\Information Service\2.0\Schemas\IPAM.Attributes.xml" from the evaluation IPAM server to the NPM server.
- Copy and modified or created report files from …\SolarWinds\Orion\Reports\ directory from the evaluation IPAM server to the NPM server.
- Transfer content of all tables starts with “dbo.IPAM_” prefix - you may read this for SQL command details - http://thwack.solarwinds.com/message/171186#171186
- If you have DHCP and DNS servers, you will need to create credentials on destination machine manually (by IPAMSettings website) and assign them to DHCP servers.
Credentials could not be copied because they are encrypted so you need to create new ones/update existing when you finish your migration.
Let us know how it went.
The migration to our new IPAM server was successful.
I have only two comments:
First, we lost our custom properties. The custom property still exist but without any value for the supernet and subnets. That isn't a big problem but we didn't know why it happens.
Second, my DBA tolds me that she not copied the data like described above. As far as I understood, we would only receiving the values inside the table but we will loose the links between the values. Instead of this she used a function from the SQL Management Studio.
Thanks for your comments
I've noticed this remained un-responded. I would like to just add an info for the other users that may run into the similar problem. We've added a checkbox into ipam that says "do not erase manually entered data" which should avoid the problem you had. also, if you call support, they have a SQL script that may get some data back from historical tables.