Anyone come across this problem before???
On about 4 or 5 of our servers, we are getting the following message when the backup job starts....
E3034 Failed to get connection 11's information,fb
Excerpt from the log file...
Start Time:10/06/03 21:00:03 End Time:10/06/03 21:03:54
Job Type:Backup Media Name: MUS-FULL
#Nodes Requested:1
#Nodes Missed:1
#Errors:0
#Warnings:3
#Vol. Missed:1
#Succ./Incomp:1
#Failed:1
#Miscompared:0
Source:S-ETLFILE1/
Session No:0
Backup Status:Failed
Reason: Login Failed
Compare Status:
Reason:
#Estimated Files:0
#Actual Files:0
#Open Files:0
#Files Miscompared:0
#Errors:0
#Warnings:0
Running Arcserve 7.0 (fully patched) on a NW5.1 server running SP5 backing up to an Ultrium 1 drive (but we've had the problem on DLT's too)
So far I've tried...
Repackaging the job with a different user id that we've tested can login to the tree normally
Recreating the SMDR and NW backup queues
Deleting the Arcswerve and Btrieve MKDE databases
Submitting jobs directly from the server console using a variety of userid's
Rebooting the server
Rebooting the server seems to do the trick, but usually around 3-4 days later, it starts happening again AAAAAAGGGGGGHHH!
After consulting the CA website, I came to the conclusion that in future when faced with an Arcserve issue, I might as well just go and ask the water cooler!
Any help will, as always, be greatly appreciated.
On about 4 or 5 of our servers, we are getting the following message when the backup job starts....
E3034 Failed to get connection 11's information,fb
Excerpt from the log file...
Start Time:10/06/03 21:00:03 End Time:10/06/03 21:03:54
Job Type:Backup Media Name: MUS-FULL
#Nodes Requested:1
#Nodes Missed:1
#Errors:0
#Warnings:3
#Vol. Missed:1
#Succ./Incomp:1
#Failed:1
#Miscompared:0
Source:S-ETLFILE1/
Session No:0
Backup Status:Failed
Reason: Login Failed
Compare Status:
Reason:
#Estimated Files:0
#Actual Files:0
#Open Files:0
#Files Miscompared:0
#Errors:0
#Warnings:0
Running Arcserve 7.0 (fully patched) on a NW5.1 server running SP5 backing up to an Ultrium 1 drive (but we've had the problem on DLT's too)
So far I've tried...
Repackaging the job with a different user id that we've tested can login to the tree normally
Recreating the SMDR and NW backup queues
Deleting the Arcswerve and Btrieve MKDE databases
Submitting jobs directly from the server console using a variety of userid's
Rebooting the server
Rebooting the server seems to do the trick, but usually around 3-4 days later, it starts happening again AAAAAAGGGGGGHHH!
After consulting the CA website, I came to the conclusion that in future when faced with an Arcserve issue, I might as well just go and ask the water cooler!
Any help will, as always, be greatly appreciated.