Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Some nodes are not backing up configs as scheduled

Some nodes are not backing up configs as scheduled

Created by Allain M Umalin, last modified by Bill Corgey on Jan 04, 2017

Views: 3,941 Votes: 1 Revisions: 5


Some nodes are not backing up configs as scheduled and the 'Overall Devices Backed Up vs. Not Backed Up' resource under CONFIG SUMMARY shows few nodes not being backed up.


All NCM versions


  • Nodes not added to NCM Config backup job.
  • Nodes may not be using the correct Connection Profile and Device Template.
  • Config Settings is set to high Simultanous Uploads/Downloads
  • Some devices may return the prompt before dumping the configuration to NCM


  1. Choose a node and manually download configs:
    1. Go to Node Details page of an affected node.
    2. Select the Left Config tab and click the Download button.
  2. If node was able to download configs, select NCM Jobs.
  3. Hover the mouse over CONFIGS tab > click Jobs.
  4. Edit Night Config Backup to see if all nodes are added to this job under Choose Nodes tab. If not, add them by either:
    • Select Nodes: Select affected node > click ADD.
    • Select 'All Nodes' to add all NCM nodes.
  5. Go to Settings > NCM Settings to avoid random failures.
    1. Configs > Simultaneous Downloads/Uploads from 3 to 10 sessions.
    2. Configs > Config Min Length from 1 to 11 lines.
    3. Protocol Settings > Telnet/SSH Connection Timeout from 45 to 280 seconds.
    4. Protocol Settings > Telnet/SSH Prompt Timeout from 15 to 180 seconds.
  6. For Devices returning the prompt before the Config is dumped, there is no workaround.  (Seen on Netscaler devices issuing the show ns.conf command, while one member of the pair is successful and the other is not)
Last modified