Backups Fail 1

[dgw69]

Here are the error messages that I am getting when the backup fails. I am running BE9.0.Final error code: a00084f9 Hex
Final error desc: A communication failure has occurred between the Backup Exec engine and the remote agent.
Final error Cat: Resource Error

I also get Exceptions: like drive not snappable and initialization failure on Drive x: There was a communication failure with one of the AOFO components.

I have the remote agents running on all of the servers.
Thanks
dgw

 

[Qdog]

Check to see if the Backup Exec Remote Agent for Windows Servers service and the Backup Exec Job Engine service is stopped on either server.

 

[dgw69]

Yes bot things are running

 

[dgw69]

both

 

[SQLBill]

Have you tried stopping and restarting the services on both servers (try the remote server first and then the one with Backup Exec)?

-SQLBill

 

[packdragon]

The only technote on Veritas with the word "snappable" in it says this:

Exact Error Message:
OFO: Initialization failure on: "\\SERVER\C:". Advanced Open File Option used: Veritas Volume Snapshot Provider (VSP). OFO: Volume specified is not snappable. Possible reasons: Not a fixed drive, or contains an active cache file or does not have a valid source or is write protected.

Solution:
Use of the Advanced Open File Option (AOFO) will cause Jobs to stay in a pre-processing state longer than Jobs that are not using this option. There is no set time limit for how long a job should or should not stay in this state. The length of time a job is in pre-processing is directly related to how much data is selected to be backed up.

If the job never changes from a "pre-processing" to a "running" state, cancel the job and check for the _BEVspCacheFile_0.TMP file on the target server's hard disk.
Check the file details of this file. If the modified date and time is different than when the last backup job started, then this file was probably present on this machine prior to the backup job. This cache file is normally deleted after the backup job finishes successfully. A possible cause for this file to not be removed from a server is that the backup job might have terminated unexpectedly due to a server shutdown or the Backup Exec services being stopped. Cancelling a backup job that is using AOFO might also cause this file to be left active on the target machine.

If it is determined that there is an active cache file on your target server, rebooting the system should remove the file and allow future AOFO backups to run normally.

From

http://seer.support.veritas.com/docs/256123.htm

 

[Burninator]

I have a similar problem. I hope this tech article is some help. Thanks Pack.

Jason

 

[8arcserve]

I'm encountering the same problem ,but I think the lack of space on the C drive is the course of my problem.
Can you configure the AOFO to write the tmp file to a different location i.e. another drive.

Thanks in advance