cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Job loses connection

rblumenthal0
Level 4

I have a backup to disk job that is backing up the C:\ and F:\ of a windows 2008 r2 VM, every 5-6 days the job fails with 'the connection to target system has been lost', we have backup exec 2010 R3 (with SP1). We have rebooted both the server and the backup server (its hard to reboot the VM during the day since it is our fileshare). Any advice on what to check next?

13 REPLIES 13

newsolutionBE
Level 6

Hi

 

Can you please post the job log when it has failed also can you post the events in event viewer in application tab at the time of failure on which server job is failing for example if you are backing up media server itself then application events of that time from media server or if you are backing particular remote server then application events if with any errors from that server

 

Thanks

rblumenthal0
Level 4

Here is the job log (names and ips changed) and an entry in the event viewer from the backup server:

 

 

Job Log for Fileshare
 
 
--------------------------------------------------------------------------------
 
 
Completed status: Failed    See error(s)  
Expand AllCollapse All  
 
 
Job Information 
Job server: backupserver
Job name: Fileshare
Job started: Monday, October 31, 2011 at 7:00:06 PM
Job type: Backup
Job Log: BEX_backupserver_00245.xml
 
 
 
Drive and media mount requested: 10/31/2011 7:00:07 PM
 
Device and Media Information 
Drive and media information from media mount: 10/31/2011 7:00:40 PM
Drive Name: Share
Media Label: B2D000240
Media GUID: {17a56725-b899-4240-ad40-39e2e8f429e5}
Overwrite Protected Until: 11/1/2011 5:00:40 AM
Appendable Until: 12/31/1899 7:00:00 PM
Targeted Media Set Name: Backup2Disk
 
All Media Used
 B2D000240
 
 
 
 
Job Operation - Backup  
Backup Options 
Media operation - Overwrite media.
Compression Type: Hardware [if available, otherwise none]
Encryption Type: None
WARNING: The option 'Verify after backup completes' was not selected.
Performing a verify operation to make sure that media can be read after the backup has completed is recommended.
 
 
 
 
 
Server - servername 
AOFO: Started for resource: "\\servername\F:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot provider used by VSS for volume F: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between 192.168.1.35:3916 <--> 192.168.1.40:10000
Network data connection is established between    192.168.1.35:3921 <--> 192.168.1.40:64134
 
Set Information - \\servername\F: 
Backup Set Information 
Family Name: "Media created 10/31/2011 7:00:07 PM"
Backup of "\\servername\F:"
Backup set #1 on storage media #1
Backup set description: "Fileshare"
Backup Method: Full - Back Up Files - Reset Archive Bit
 
 
 
 
Backup started on 10/31/2011 at 7:00:51 PM.
 
Backup Set Detail Information 
The network connection to the Backup Exec Remote Agent has been lost. Please check for network errors.
 
 
 
Backup completed on 11/1/2011 at 3:43:40 AM.
 
Backup Set Summary 
Backed up 465124 files in 32448 directories.
Processed 175547569454 bytes in  8 hours,  42 minutes, and  49 seconds.
Throughput rate: 320 MB/min
Compression Type: None
 
 
 
 
 
V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
 - AOFO: Initialization failure on: "\\servername\C:". 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.
 - AOFO: Initialization failure on: "\\servername\Shadow?Copy?Components". 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-65302 - The Shadow Copy resource is not responding. Backup set canceled.
V-79-57344-65302 - The Shadow Copy resource is not responding. Backup set canceled.
 - AOFO: Initialization failure on: "\\servername\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-65301 - The System State resource is not responding. Backup set canceled.
V-79-57344-65301 - The System State resource is not responding. Backup set canceled.
 
 
 
 
 
 
Job Completion Status 
Job ended: Tuesday, November 01, 2011 at 3:43:48 AM
Completed status: Failed
Final error: 0xe00084f8 - The network connection to the Backup Exec Remote Agent has been lost. Check for network errors.
Final error category: Resource Errors
 
For additional information regarding this error refer to link V-79-57344-34040
 
 
 
Errors 
Click an error below to locate it in the job log
BackupV-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.
V-79-57344-65302 - The Shadow Copy resource is not responding. Backup set canceled.
V-79-57344-65302 - The Shadow Copy resource is not responding. Backup set canceled.
V-79-57344-65301 - The System State resource is not responding. Backup set canceled.
V-79-57344-65301 - The System State resource is not responding. Backup set canceled.
 
 
 
Exceptions 
Click an exception below to locate it in the job log
BackupV-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
 - AOFO: Initialization failure on: "\\servername\C:". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
 - AOFO: Initialization failure on: "\\servername\Shadow?Copy?Components". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
 - AOFO: Initialization failure on: "\\servername\System?State". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
 
 
 
 
Adamm Database Event: Database Connection Lost!
Error = E_PVL_DB_LOST_CONNECTION
Server = "BackupServer"
Active Node = ""
Instance = "BkupExec"
Database = "BEDB"
Connection String = "DRIVER=SQL Server;SERVER=BackupServer\BkupExec;DATABASE=BEDB;App=BEWS PVL"

rblumenthal0
Level 4

double post

CraigV
Moderator
Moderator
Partner    VIP    Accredited

I've just gone through this again today..if you run: vssadmin list writers - from a command prompt you should find some of the VSS writers are in error.

Reregister the VSS *.dlls using the Symantec TN below and it should fix it. This can be done while the server is online with no effect on anybody.

http://www.symantec.com/docs/TECH70486   

If this still doesn't fix it, uninstall the RAWS agent and run a push-install from your media server again. Once done, make sure that your AV (if you run 1) isn't blocking access between the RAWS agent and the media server, and if so, put in an exclusion.

 

Thanks!

rblumenthal0
Level 4

i ran the vssadmin list writers on both the backup server and the VM having issues, but none of the writers said there was an error. i havent reregistered the dlls yet and being that teh VM is our fileshare, reinstalling the agent will need to be scheduled (since the possible reboot), thanks

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...nope, there is a way around that which buys you time if you cannot reboot the server immediately:

1. Backup your registry first!!!

2. Open regedit.exe --> HKEY_Local Machine

3. SOFTWARE --> Symantec...

4. Look for a registry key called PatchReboot and delete this.

 

That fools BE into thinking it was rebooted. Reboot the server as soon as you are able too...

pkh
Moderator
Moderator
   VIP    Certified

Enable AOFO in your job and try again.

rblumenthal0
Level 4

AOFO is already set to 'Automatically select open file technology'

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...OK, then on the affected server, run: vssadmin list providers and take note of what is shown. Change to that provider in AOFO in the job settings!

Tmy_70
Level 5
Partner Accredited Certified

 

Check this link about de AOFO  Troubleshooting http://www.symantec.com/business/support/index?page=content&id=TECH45996

pkh
Moderator
Moderator
   VIP    Certified

What has quiet time got to do with the problem?

rblumenthal0
Level 4

the aofo option is already set to Microsoft provider (same as the results of vssadmin list providers on the affected VM), is there anything else i should check? 

 

i see this in the event viewer of the backup server around the time of the failed job

 

 

Adamm Database Event: Database Connection Lost!
Error = E_PVL_DB_LOST_CONNECTION
Server = "BackupServer"
Active Node = ""
Instance = "BkupExec"
Database = "BEDB"
Connection String = "DRIVER=SQL Server;SERVER=BackupServer\BkupExec;DATABASE=BEDB;App=BEWS PVL"

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...the TN below may or may not be for your issue, but check it out nonetheless:

http://www.symantec.com/business/support/index?page=content&id=TECH87166