ArcServe Backups Fail on SBS2008
I have a client running SBS2008 SP1. Their backups (Arcserve 12.5) are failing with:
E3392 Backup Server TCP reconnection timeout. (AGENT=SERVERNAME @ IP ADDRESS, Network Error 10054)
This is at the BEGINNING of the backup job, after the job says "waiting" for a couple minutes (what I'm assuming is the designated TCP timeout period for the Windows Server Agent. Any hints / tips? They got ONE good backup 5 days ago, immediately after installing Arcserve. That backup went flawlessly, and they've been nothing but trouble since.
Any help would be appreciated...
E3392 Backup Server TCP reconnection timeout. (AGENT=SERVERNAME @ IP ADDRESS, Network Error 10054)
This is at the BEGINNING of the backup job, after the job says "waiting" for a couple minutes (what I'm assuming is the designated TCP timeout period for the Windows Server Agent. Any hints / tips? They got ONE good backup 5 days ago, immediately after installing Arcserve. That backup went flawlessly, and they've been nothing but trouble since.
Any help would be appreciated...
Cris Hanna
What are you trying to backup to? Portable harddrive? Tape? Another Server?
ASKER
Backing up to an External 800GB/1.6TB HP Ultrium SAS tape drive. I'm going to try a backup to another server tonight, but over a 10/100, it's gonna' take awhile, even if it works...
I think that makes sense, see if the issue is the software or the source
TCP timeout is a very generic error when doing a client agent backup.
All it tells us is the flow of data from the agent running on the remote target system stopped. It could be something on the system or network related.
Consider:
does this happen with all clients, just this one, or some
If it happens with all systems then investigate things from the backup server NIC to cable to port on the switch.
If it is just the one or some systems check things on their side. But also consider the possibility that something at the application level is causing it.
Open the Client Agent GUI and configure it for low priority.
Check to see what other applications are running on the client system.
All it tells us is the flow of data from the agent running on the remote target system stopped. It could be something on the system or network related.
Consider:
does this happen with all clients, just this one, or some
If it happens with all systems then investigate things from the backup server NIC to cable to port on the switch.
If it is just the one or some systems check things on their side. But also consider the possibility that something at the application level is causing it.
Open the Client Agent GUI and configure it for low priority.
Check to see what other applications are running on the client system.
Did you check below Article from CA support online.
Troubleshooting E8522 and E3392 (Failed to receive data from the client agent) errors
Document ID: TEC266855
Run a test backup of the remote server to an FSD on backup server.This proves if the problem is with
Troubleshooting E8522 and E3392 (Failed to receive data from the client agent) errors
Document ID: TEC266855
Run a test backup of the remote server to an FSD on backup server.This proves if the problem is with
Did you check below Article from CA support online.
Troubleshooting E8522 and E3392 (Failed to receive data from the client agent) errors
Document ID: TEC266855
Run a test backup of the remote server in question to an FSD on backup server.This proves if the problem is with device.
You can try steps mentioned in above document.
Increase ReceiveTimeOut and SendTimeOut value from default. Make sure both timeout values are same on backup server and remote server.
You can also decrease packet size on the remote server. Default packet size is 2048, make it 512 or 48 as mentioned in the document.
I hope this document will help you resolve the issue.
Troubleshooting E8522 and E3392 (Failed to receive data from the client agent) errors
Document ID: TEC266855
Run a test backup of the remote server in question to an FSD on backup server.This proves if the problem is with device.
You can try steps mentioned in above document.
Increase ReceiveTimeOut and SendTimeOut value from default. Make sure both timeout values are same on backup server and remote server.
You can also decrease packet size on the remote server. Default packet size is 2048, make it 512 or 48 as mentioned in the document.
I hope this document will help you resolve the issue.
ASKER
Thanks for the repsonses... I'm trying the information in that article. Doesn't look like the Backup Agent is working properly. The agent is listening (proof is telnet localhost 6050), and I can see the servers connection to the client agent in the Backup Agent Admin, but it just says "preprocessing."
Going to try a complete uninstall/reinstall of the application.
btw, this is a single server backup scenario. The Application and Tape Drive are installed on the server I'm trying to backup.
Going to try a complete uninstall/reinstall of the application.
btw, this is a single server backup scenario. The Application and Tape Drive are installed on the server I'm trying to backup.
ASKER
Well, backups still failing after checking the aforementioned CA Article, and Reinstalling. Opening a case with ArcServe on Monday Morning.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Could you please provide me with any article/document online which says, it's known issue. I will add it to my knowledge base.
Do they have any update for this issue ?
Do they have any update for this issue ?
ASKER
I was informed that it's a known issue by the CA Tech over the phone. I don't know of any KB articles referencing the issue. Sorry...