Baseline Synthetic Backup jobs fail with a timeout error during the collection of synthetic backup information.
V-79-57344-2307 0xe0000903 - time out occurred messaging involved collecting additional information synthetic backup.
A Synthetic baseline backup job will fail with the following error when a large volume with many files is selected for backup:
Running the Backup job in debug mode the following error is observed in the Backup Exec remote agent debug log:
LP_ENV: error 0xe0000903 processing object
Backup Exec Remote Agent Debug Log:
 04/11/08 18:23:06 End of TF_OpenSet() ret_val = 0x00000000, num buffers = 10
 04/11/08 18:23:06 Going to perform pre backup dbcc.
 04/11/08 18:23:06 Performing traversal pass for catalog driven backup
 04/11/08 20:49:11 [no resource for 3894]
 04/11/08 20:49:11 Entering SetupLocalShareInfo
 04/11/08 20:49:11 Informational: Enumerating DFS
 04/11/08 20:49:11 [no resource for 3893]
 04/11/08 20:49:11 Windows Server 2003 (or higher) detected. No S2LP mapping required.
 04/11/08 21:07:26 LP_ENV::MsgError: error 0xe0000903 processing object images\AdobeComments\6Mt5lcScNqWqVoHCoFpAXD
 04/11/08 21:07:26 TF xfer time = 9859 seconds.
 04/11/08 21:07:26 WRITE: tpreceive_fail_count = 4
 04/11/08 21:07:26 WRITE: waiting_on_buffers_count = 0
 04/11/08 21:07:26 WRITE: buffers_written_count = 12394
 04/11/08 21:07:26 TF_CloseSet()
 04/11/08 21:07:26 FreeFormatEnv( cur_fmt=0 )
 04/11/08 21:07:26 [no resource for 3894]
 04/11/08 21:07:26 TF_FreeDriveContext( 857570 )
 04/11/08 21:07:26 TF_FreeTapeBuffers: from 10 to 0 buffers
 04/11/08 21:07:26 Backup Job Stop(0) - Fri Apr 11 21:07:26 2008
Perform the following and make sure all the settings are properly configured
1. Use existing Windows or 3rd party Disk De fragmentation tools to regularly defragment volumes. Please be sure to defragment the volumes when there is no backup activity.
2. Ensure both the switch and the network cards have matching settings between the Media server and remote server. If the switch port is set to 100 full, the NIC for the servers should also be set to 100 full.
3. Reinstall or update the Network Card drivers on the media server and remote server.
A registry key has been added in Backup Exec 12.5 for Windows Servers revision 2213 Hotfix 327039. You can download the patch from here: www.symantec.com/docs/TECH71794
A registry key has been added in Backup Exec 2010 for Windows Servers revision 2896 Hotfix 344584. You can download the patch from here: www.symantec.com/docs/TECH126191
This registry key will increase the buffer timeout period during the Synthetic priming or baseline backup.
NOTE: A registry entry must be added to the remote agent server after the hotfix has been applied to the Backup Exec media server and the remote agent updated.
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup
Value Name: CDBSpecialBufferTimeout
Value Type: DWORD
Value: The value represents the number of seconds, with a minimum of 60 seconds, and a maximum of 24 hours or (86,400) seconds
After the registry key is created restart the Backup Exec remote agent service on the remote server.
It is recommended to start off with a CDBSpecialBufferTimout value of 3000 seconds and then increment the value by 1500 seconds until the issue is resolved.
NOTE: If increasing the Buffer Timeout does not resolve the error, break up the Backup Job into smaller parts (multiple jobs).
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec Corporation to be addressed in the next major revision of the product. There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see http://www.symantec.com