ArcServe 2000 vdi.log error E6802 backup agent error 127

[kpatrick13]

Object:
NT4 server sp6a
ArcServe 2000 sp4 (hate it)
Sql 7 sp4

Backing up local SQL database using sql agent generates virtual device error. E8602 (database) ec backup agent error -127 error virtual device

Suggestions I found thus far and implemented:
1- I have verified the compatiblity of the DB's are 70
2- I have specified IP instead of named pipes in registry
3- I have looked at the buffer and made it 512
4- I have rebooted the NT4 server
5- I cannot apply SQL 7 sp2 (using sp4)


The sql 7 database's are still not getting backup up and reporting this particular error.

The funny thing is the SQL DB is located on the same server, so it doesn't even have to pull over the network.

I need some help. Any different Ideas?

 

[kpatrick13]

Okay 1- I posted the incorrect error..8602...not 6802.

However, after talking to arcserve, very UN enlightening, I ran some basic boon or bust jobs to see what if....

When backing up SQL databases, if you have many, select each one indivudually when creating a single job, and the backups will runs sans error.

Do not just click the SQL database icon to select all the databases listed underneath.... As of yet I have not seen a fix for this from CA and I recommend this only as a short term fix....much like ArcServe is in general.

Tilting at windmills.
Kpatrick13

 

[nobeta]

We have the same setup and receive the exact same error. We have had this problem for a year or more, and reported it to CA when it first surfaced. I am not aware of any fix that specifically addresses it other than the one that suggest applying SQLSP2 which you and I are well beyond. As a workaround we created SQL Backups using Enterprise manager to backup to disk and then use Arcserve to backup these directories to tape. However this requires lots of free space on the server. The other day I applied Arcserve SP4 and thought I would try backing up with the agent again to see if this has been resolved. The first time I tried it worked, Great! That night I scheduled the regular backup to use the agent and it blew up with the same old errors 8602 and 127. Today I recreated the job and made sure that I typed in the password for the SA account before saving the job, and ran it again and it worked. (When I submitted the job that failed I accepted the security for the SA account that comes up automatically when you submit the job, as this should be the correct password.) I have no idea if this was the problem, but will let it run over the weekend and see what happens. I too have experimented with selecting databases individually rather than the entire SQL Server Icon and have had mixed results. This most recent backup that was successful had selected the entire SQL icon and it worked, where as before it only worked when I selected individual databases. I’ll let you know if I have any success.

 

[nobeta]

Just thought I'd follow up. I have to admit that since we applied arcserve service pack 4, deleted and recreated the backup job, select the entire SQL icon, specified the SA account and password, the backup has worked all week without the error.