Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Migration Issue - NPM and NCM database sync error

Hello

I am in the process of migrating our NPM and NCM onto new 2008 servers (front and back ends).

I have installed NPM and restored todays copy of our live database - This works fine and can see the nodes we have in the test lab as well as the existing nodes in the database.

I then restored todays copy of NCM onto the new SQL server as a seperate database and installed NCM. It seemed to go ok and has added the relevant config section to the web console but upon clicking it there is a message which says the NPM and NCM databases need to be synced.

I clicked to sync but then it flags up the error:

"Synhronization error: No DNS entries exist for host SERVER1"

SERVER1 is the name of the current (soon to be replaced) live NPM server.

I am guessing something in the NPM/NCM database is referencing this server but I don't know what?

Everything is in a test lab until we go live and it does still show SERVER1 as a polling server although (current live nodes are still assigned to it) it's uncontactable obviously.

Any ideas?

Have also logged a call with Support

Cheers

Find more posts tagged with

Accepted answers

All comments

danielleh

Hi noneforit--

Would you please post your ticket #?

Thank you,
DH

FormerMember

I think I worked this out.

I imported the live database into our new test Environment which meant that the old primary polling engine and additional polling engine were still in the database.

When it tried to sync the NPM and NCM databases it looked for both of these servers as all our live nodes are assigned to them and because we are in a closed lab, it was unable to see them....hence the error.

I am obviously not going to be able to test the NCM and NPM database sync in the lab and will have to hope for the best when we go live tomorrow

Luckily we are leaving the old servers in situ in case we experiences issues and I can simply move the nodes back to the,