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 > Nightly Back-up Takes Unusually Long (20-plus hours) to Complete

Nightly Back-up Takes Unusually Long (20-plus hours) to Complete

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 883 Votes: 0 Revisions: 10

Issue:

Nightly Back-up Takes Unusually Long (20-plus hours) to Complete.

Solution:

There may be several reasons for this behavior.  The most common are:

  • Logging for Scheduled Jobs has been turned on for an extended amount of time. Turn off all logging if you are not troubleshooting a particular issue.
  • Session Tracing has been left on for an extended amount of time.  Session tracing should only be left on for troubleshooting purposes and immediately turned off after gathering a sample of the traces needed.
  • The job may have devices with large configuration files, like Cisco WLC or Fortinet devices.
    •  WLC devices if running the wrong command (show running-config) and should be using TFTP 
    •   ​Fortinet devices. No work around, but they should be isolated to their own job(s).

 

These are the most common instances. Additionally, network connectivity, firewalls, database running out of room, local hard drive getting low on space and / or other environmental issues such as the size of the deployment (30,000 nodes) can play a part in sluggish behavior.  

Last modified

Tags

Classifications

Public