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

Nightly Config NCM Backup Issue

Hi Everyone.

We having issues with NCM Backing up configs for a number of nodes. The Nightly backup job has been set up to pull both the Start-up and Running config off regardless if anything in the config has changed. When investigating the issue, We noticed that it's getting a 'connection refused' when we test connection (SNMP and NCM Profile Connection) both come back with successful tests. When enabling Session Trace and retesting I can see the connection out to device happens, it runs the script to pull the config, however it's promptly ended with a 'disconnect'. I have increased the TELENT/SSH Timeout from default in case this was the issue. Tried redoing the script etc.

We stopped/restarted services which got working again. was able to manually pull a config of random nodes and was able to trigger the config backup job. However that night when it was naturally meant to trigger. it stopped working again. I have noted that there seems to be a DB maintenance job failure.

Can a issue with DB maintenance cause issues with SolarWinds/NCM been able to backup or is this a red herring?

We have been tempted to stop/restart services again. run the NCM jobs and DB maintenance etc again to get everything rebalanced and hopefully working again.

Version: 2024.4.0

Any Ideas?

Many Thanks.

Find more posts tagged with

Accepted answers

TehAj87

Fixed! Looks like there was an issue that was affecting one NCM Table, which was the NCM_ConfigArchive. Working with a DBA we found there were multiple blocks. Cleared them out which we were able to get DB maintenance, Purge jobs working etc. then we were able to get a few test configs pulled, split the all in one NCM job into separate jobs and spaced out the trigger times. and this morning both jobs completed as per scheduled without issue.

All comments

stuartd

Is there any commonality between the failing nodes?

e.g. are they all one make & model or the same level of OS or recently upgraded? That might be an avenue to investigate. However, the fact that a stop/start of services appears to briefly work suggests either an underlying SW issue or you need to split out your job.

We only backup once a week** on our primary platform and our 6k nodes are split over various nights and running is captured at a different time to startup, etc.

** unless vital, and a node undergoes frequent daily changes, then there is no real need for a nightly backup. Our process also includes that any change should have a pre and post change backup.

TehAj87