E8602 Failed to read from database --EC= Backup Agent Error --(69) Read/Write error in named pipes
I am running ARCServe 2000 SP4 Build 1100 on an NT Server 4.0. I am backing Exchange 5.5 w/the ARCServe 2000 Exchange Agent. While doing an exchange backup i am getting this error message "E8602 Failed to read from database --EC= Backup Agent Error --(69) Read/Write error in named pipes".
The things i have applied to solve this issue are as follows:
1. Uninstalled backup agent and reinstalled
2. ran SP4 after installation of backup agent
3. applied patch http://support.ca.com/Download/patches/asitnt/QO19251.html
http://support.ca.com/Download/patches/asitnt/QO22840.html
4. set the usetcp value under
HKLM\software\Computerasso
dbaexch to 1 and then recycle backup agent RPC server
5. HKLM\system\currentcontrol
and verify the value of "IRPSTACKSIZE" for NT you can increase it up to 11
6. Stopped NAV for Exchange Service on Exchange Server
Any suggestions will be very helpful...thanks in advance
The things i have applied to solve this issue are as follows:
1. Uninstalled backup agent and reinstalled
2. ran SP4 after installation of backup agent
3. applied patch http://support.ca.com/Download/patches/asitnt/QO19251.html
http://support.ca.com/Download/patches/asitnt/QO22840.html
4. set the usetcp value under
HKLM\software\Computerasso
dbaexch to 1 and then recycle backup agent RPC server
5. HKLM\system\currentcontrol
and verify the value of "IRPSTACKSIZE" for NT you can increase it up to 11
6. Stopped NAV for Exchange Service on Exchange Server
Any suggestions will be very helpful...thanks in advance
ASKER
This problem has been occuring for the past few days. WE ran a test backup of a few mailboxes after applying the patch QO22840 and it goes through. But if you do another test if fails, so the problem is intermittent. AT the moment we are doing a full backup(230 mailboxes), its been going on for the last 2 days, still going. Normally our full takes about 6 hours to complete, this backup is still going. I just went through the dbaxch2.log file on the exchange server. During some mailbox backups i am getting this message "PID:2881 TID:2420> ReadReference..(): WARNING! not enough space in cacheBuffer for 64K data. The rest part will be read in later". I even tried stopping the NAV, thinking it might have some effect, but i guess not. Have you come across this type of issue? What type of backup and exchange are you running??
Haven't seen this. Honestly, I think you should stop this backup, and check your databases, eseutil /g /v /x, pipe it to a txt file, and see what's there. Unfortunately, this would require taking the services offline, so you might be doing this after hours. do you have the applog and syslog? Take a look, see what kind of errors are listed. Specifically, you're looking for errors related to hardware problems, like SCSI timeouts, or ESE errors for exchange. I'd really take a hard long look at my databases.
D
PS, not that it matters, but I use NTbackup for windows 2000 to back up my exchange server at home, and I use Veritas at work. Soon, I'll use ntbackup every chance I get, they are improving functionality with W2K3
D
PS, not that it matters, but I use NTbackup for windows 2000 to back up my exchange server at home, and I use Veritas at work. Soon, I'll use ntbackup every chance I get, they are improving functionality with W2K3
ASKER
So what is the command that i have to run exactly? Where are the applog and syslog located?
How exactly do you do the NT Backup w/Exchange?
How exactly do you do the NT Backup w/Exchange?
one problem at a time, applog and syslog, in the event viewer. check them and see what you have for errors.
d
d
ASKER
No errors reported..I am going reboot my exchange server tonight and then do a Inc. backup to see if that helps. I am also run the debug on exchange to see if arcserve gives any other messages that might help..
ASKER
can large mailbox (~300mg) cause issues with the backup?
No, size won't do that.
D
D
ASKER
can large mailbox (~300mg) cause issues with the backup?
Kidego - Can I jump in for one comment?
He mentioned 'mailboxes' he might be doing brick level. You might want to verify and alter the job or create a new one and just do the I.S. for troubleshooting...
~M
He mentioned 'mailboxes' he might be doing brick level. You might want to verify and alter the job or create a new one and just do the I.S. for troubleshooting...
~M
Good point, I assumed that this job had been working, and then suddenly stopped. he could try to create a new backup job from scratch.
D
D
ASKER
The job that took 2 days completed and is fine (except that it took 40 hrs to complete. We rebooted our exchange server (we do not schedule it to reboot regularly) and the daily and full backup ran normally...maybe it just needed the reboot. we are going to monitor it for a about a week...
Is this a DELL server with a DELL DLT drive?
ASKER
cpq dl380 G2 - overland loaderxpress (tape device)
ASKER
the backup is working fine now, no issues as of yet...been a week so far. maybe it did need a reboot
It's the spirit of Veritas... telling you that you cannot avoid the inevitable, all must switch to Backup Exec :)
Glad it's resolved, for now.
~Mark (opinions of course)
Glad it's resolved, for now.
~Mark (opinions of course)
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I will leave the following recommendation for this question in the Cleanup topic area:
PAQ/ Refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
What90
EE Cleanup Volunteer
I will leave the following recommendation for this question in the Cleanup topic area:
PAQ/ Refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
What90
EE Cleanup Volunteer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://support.ca.com/products/nt/16040.html
I found these 2 articles for you, I hope the first article is not your problem. How long has it been since this started happening? Your databases could have checksum errors, and yes, they could still function, but they won't back up at all. Backup software will not backup a database with checksum errors.
HTH,
D