Backup job remains in "pre-processing" state for 15 minutes or more due to lost network connection.

Article:TECH23843  |  Created: 2003-01-23  |  Updated: 2012-04-05  |  Article URL http://www.symantec.com/docs/TECH23843
Article Type
Technical Solution

Product(s)

Issue



Backup job remains in "pre-processing" state for 15 minutes or more due to lost network connection.


Solution



This can occur in very specific situations. The following conditions would need to apply for there to be a 15 minute delay before the job (or backup set) will time out of the "pre-processing" state:
 
  • The backup job (or set) is for a remote machine
  • When the job (or set) first begins, the remote machine is available via TCP/IP
  • The remote machine becomes unavailable (crash, shutdown, network failure, etc.) either just before the Symantec Backup Exec (tm) server first requests for data or just after the remote machine first replies to the request (these are both small windows typically).
·
If the remote machine becomes unavailable right after the Backup Exec server first requests data but before it gets a reply, then Backup Exec is dependent on the operating system TCP/IP socket settings for the timeout.

For Microsoft Windows Servers (Windows 2000& Windows 2003), this default setting is two hours (7,600,000 milliseconds). While this is a very unlikely scenario, it could mean the backup job would remain in "pre-processing" for up to two hours.  

To change this timeout would mean altering the TCP/IP registry timeout setting (KeepAliveTime) on the Backup Exec server, which in turn would affect all TCP/IP applications on the server. For more information on TCP/IP timeout settings, please refer to the Microsoft online Knowledge base.
 



Legacy ID



254198


Article URL http://www.symantec.com/docs/TECH23843


Terms of use for this information are found in Legal Notices