nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

Config Backup Stopped working after upgrade to 3.5

jedi755

Anyone else having this issue? We cannot perform mass backups, it seems to lockup and never finish the job.

Find more posts tagged with

Accepted answers

All comments

jonchill

I noticed this today some backups work and some don't but it's not the same switches every night it seems random.

I've logged a call with support to see what they say, I'll let you know when I hear anything.

Jon

IT Infrastructure Manager
Pilgrim Hospital
UK

danrog

I noticed after the upgrade, the Global protocol variable names changed. I had to update all my hosts to the new vairable names before I could get automated/manual config backups to work. Hope this helps.

BryanBecker

This may be your issue. I have a nightly device failure report sent to me an usually it's pretty small. After the upgrade I had alot of failures.

After the upgrade the new communication option "Request Configs Using" was added. I think it's default is telnet. And after the upgrade all the devices where updated with this new option and it was left blank...therefore defaulting to telnet. Since my devices only use SSH I had to edit multiple devices and change that to SSH auto.

Once I did this it worked.

HTH

BB

jedi755

I had the same issue with the "global default protocol", I fixed it and still getting the problem. One thing I noticed is that it is only happening to my nodes where the groups are larger than 1000 nodes. Still working on a solution.