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

Problems with canned nightly backup job.

I’m having a problem with the canned nightly config backup. For some reason it just stopped working and after looking over the log, it’s showing the following.

ERROR: Cannot download Running config : Cannot Log into Device : bad password.

We haven’t changed the username or password and I can right click on the root group of nodes and run a backup just fine.

Also, one other question. The canned backup job keeps the backups indefinitely. We only need 6 months at the very most. We now have thousands of config files from the very beginning (2.5 years). The files are now taking up some 10gig of disk space. Is there any way to modify the settings on this?

Detailes on the system

Orion NCM v6.1

ConfigMgmtEngine8 Version 8.3.177

Find more posts tagged with

Accepted answers

FormerMember

That was it.

the account used to run the job had expired. if you open up the job and select the security tab.

All comments

fcaron

First one does not ring a bell. Does the download work manually and fails when scheduled? Let's see what others have to say. If nothing, open a case.

Second one: you can use the purge job.

Capture.PNG

FormerMember

Thanks for the purge information. That helps…

To answer your first question. Yes, when I run a manual backup by clicking on the root of the node list and then click on download configs, everything works fine.

I’ve tried rebooting the server and checking to make sure the “Request Configs Using” method are correct. Strange.

fcaron

Don't know what happens. I suggest Opening a case if you don't see someone proposing a solution here soon.

bcorgey

This is most likely not an issue with the credentails, rather an NCM interpretation of the issue at the time.

I would suggest to actually extend the telnet/SSH timeouts in the NCM settings by 15 -30 seconds and test.

If that does not resolve the issue, then definitely open a support ticket.

FormerMember

I may have found the problem but will check if it runs as scheduled tonight.

Suspect it may be the windows credentials on the scheduler.

MarieB

Hi netavs--

Would you post your findings here for the benefit of the community.

Thx,

FormerMember

Absolutely

FormerMember

That was it.

the account used to run the job had expired. if you open up the job and select the security tab.

bcorgey

Thank you Netavs.

This will be helpful to others with the same issue.