cancel
Showing results for 
Search instead for 
Did you mean: 

BE 12 Fails on SQL backups and System State

mike_eisenhart
Level 2
I am trying to run full backups on a few SQL 2005 servers (running on Win2K3 64bit). The volumes backup fine but when it gets to the SQL backup (yes, I have the SQL agent installed on Media Server) it reports "server not responding. Backup set cancelled." Also when it gets to the System State it tries using AOFO and fails. I have tried turning of AOFO and still seems to try and fails. Jobs are running under proper accounts, using RAWS64 remote client. Can anyone help?? Also, could this be related to available disk space? Does the cache file need a certain percentage of free space?

Network control connection is established between 192.168.42.12:3437 <--> 192.168.52.31:10000
Network data connection is established between 192.168.42.12:3341 <--> 192.168.52.31:2750
Consistency checking DB_Main
Consistency Check Physical Only.
Consistency check was completed.
V-79-57344-65072 - The database server is not responding. Backup set canceled.
V-79-57344-65072 - The database server is not responding. Backup set canceled.
V-79-57344-34110 - AOFO: Initialization failure on: "\\dbserver\System?State". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.

MikeE
3 REPLIES 3

chicojrman
Level 6
Have you ran all the latest patches?

mike_eisenhart
Level 2
I ran the Live Update through BE this morning. It shows I have the following patches installed.
Service Pack 2
Hotfix 309178
Hotfix 311546
Hotfix 313345
Hotfix 315724

BE Media server is:
Backup Exec 12. Ver 1364

Ben_L_
Level 6
Employee
First off, system state will always use AOFO since it has to use VSS to perform the backup.  You can turn off AOFO in the job and system state will always use it.

So is this error happening on all of your SQL 2005 servers or just 1?  After you ran Liveupdate did you push out the updated remote agents to the the client(s) having this problem?  Liveupdate only updates the media server and the Agent install packages, it doesn't update all the remote agents for you. Make sure the remote agents are up to date as well, also make sure all the remote agents are running as local system not a user account.  Can you tell if the remote agent on the client(s) is crashing during the backup?