E8604 Failed to start backup for SQL 2000 BACKUP AGENT

[Chris77x]

I am using Windows 2000 SP2 Terminal server with Arcserve 2000 Advanced Edition v7 build 1100, and trying to backup a SQL 2000 SP2 Server that has the Arcserve 2000 Client Agent and Backup Agent.

I'm backing up the SQL database thru the AS2000 Client Agent using IP address and not name resolution. The backup worked fine but after 2 days I started to get these 2 error messaegs in the log:

E8604 Failed to start backup. (DBNAME=XXX, EC=BACKUP AGENT ERROR - (127) "Error at Virtual Device Set. Please Check the SQL Server VDI.LOG".)

E8604 Failed to start backup. (DBNAME=XXX, EC=BACKUP AGENT ERROR - (73) "SQL Server Error. Please Check the Log File DBASQL.LOG".)

I have looked at the FAQ by databasebaba and it hasn't helped me resolve the issue yet. I recreated the backup job on SQL server and also recycled the Backup Agent RPC server service on the SQL server. I also tried to reset the login information for the backup at night and the job still failed. It only works fine when I create/run a test job to backup the databases during the day.

I would appreciate any suggestions or advice.

Thanks

 

[databasebaba]

Please check the FAQ written by me in ARCserve/Brightstore

This will help DatabaseBaba...

 

[Chris77x]

i did check the FAQ and it didn't help me resolve the problem
the 2 error messages still come up

any other ideas?

 

[SmithBW]

I am also having the same problem with my SQL database. I have checked the permissions to access and/or backup it up and all are correct. I also checked the settings as indicated above which were already set. Does anyone have any other suggestions? My errors are exactly as Chris77x had indicated.

Thanks for any help!

 

[ACiDelic]

That VDI error occurs because an error occurs authenticating the user or there is a problem with a security token. To fix the problem, you should change Backup RPC Server service (where the SQL agent is installed) to start using the same NT credentials that your SQL server starts with.

Something else to keep in mind is that even though you create your backup using the client agent, the backup still transfers data through its own channels. No SQL data goes through the client agent at all. Only file backups go through the client agent.

It is best to create the job by finding the server through the network or by adding it to preferred shares (using hostname not IP, which won't work).

 

[Antonello]

Try to start the Backup agente RPC service on SQL server with a domain admin account.
I resolve the same problem with it.
Caio