I figured out that I had to use SQL Management Studio to do the restore. Here's a copy of a conversation I am having with Solarwinds:
I have a further question: I am migrating to new hardware, but I want to maintain the old server name. I am finishing the setup of the new server (which still has it's new name, as the current server is still in production). When I run the Configuration Wizard to use the newly restored copy of the database, it informs me that it's in use by a server with the old name (which is true). Am I correct in assuming I do want to continue with this procedure? Then, when the Configuration Wizard is done, I can stop the services on the old server; rename and renumber it's IP address. Then I will rename the new server to the same name and IP address.
At that point, I should have a server with the correct name, IP address and installed NPM and SAM, with a restored copy of the database. I can then re-install the license.
Is there anything else I need to look out for?
So I am all migrated. Odd that no one replied in any way. :-) But anyway, I decided to make the new server the same name and IP as the old server, so after de-activating the licenses, and re-assigning them, it all seems to work now. So this is all done.
We are upgrading to new hardware also, can I ask, what does this mean "Can I install and import the database backup to the new server"? Are you not running your SQL server to which you write your polling data on a seperate physical machine? Do you not just stop your NPM server from writing to that database then set up NPM on the new hardware then when you get the NPM up and running on the new hardware point the new installation of NPM at your SQL server and start writing to that database and start polling again? Forgive me if this sounds silly but I am a newbie and tring to get my head around this!
Also, regarding modules we have installed in our present set up such as IPSLA MGR. Where does the configuration for these modules reside? Lets say I set up an IPSLA job. The IPSLA manager goes and writes config for that job on the router so the router knows how to run the job, when we move IPSLA module over to our new hardware, will it begin to run in the same way as it did previously or will it need to be configured again? Where does this configuration reside?