Video Screencast Help

V-79-57344-65072 - An error occurred while connecting to the Backup Exec Remote Agent on the Backup Exec server

Created: 03 Sep 2013 | 6 comments
Vince Hubbard's picture

Hello Symantec,

All backups run smoothly except for one.

Using Backup Exec 2012 SP1.
Latest Agent for Windows (14.0.1798.1244) is installed on the client. A trust has been established. Credentials are correct.

I've created a backup for a vm.

This is the error from the job log:

Snapshot Technology: Started for resource: "\\servername.domain\Microsoft Information Store\Mailbox Database 1019742211". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
V-79-57344-65072 - An error occurred while connecting to the Backup Exec Remote Agent on the Backup Exec server. Ensure that the job options are correct, and then submit the job again. The backup set was not created.

Snapshot Technology: Started for resource: "\\servername.domain\E:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot technology used by VSS for volume E: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
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.

Snapshot Technology: Started for resource: "\\servername.domain\C:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot technology used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).

Drive and media mount requested: 9/2/2013 11:05:38 PM
No appendable media could be mounted.
Switching to overwrite operation on scratch media.

Drive and media information from media mount: 9/2/2013 11:05:48 PM
Drive Name: Deduplication disk storage:1
Media Label: OST00000136-4906A1C6996CF72F
Media GUID: {5f3b02d8-d072-4867-bb36-6f32ca6f05e9}

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. Snapshot Technology: Started for resource: "\\servername.domain\System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" "\\?\VOLUME{2492C0DE-5C38-11E0-A04D-806E6F6E6963}" . The snapshot technology used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). The snapshot technology used by VSS for volume \\?\VOLUME{2492C0DE-5C38-11E0-A04D-806E6F6E6963} - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). V-79-57344-65072 - An error occurred while connecting to the Backup Exec Remote Agent on the Backup Exec server. Ensure that the job options are correct, and then submit the job again. The backup set was not created.

 

This is the error from event viewer of the vm:

First error

Exchange VSS Writer (instance b28543aa-c69d-4356-8cd1-8904f7131977:7) has completed the backup of database 'Mailbox Database 1019742211' with errors. The backup did not complete successfully, and no log files were truncated for this database.

Second error

Information Store (1812) Shadow copy instance 7 aborted.

For more information, click http://www.microsoft.com/contentredirect.asp.

I've tried re-establishing a trust, re-installed the agent. removed the server from the server list and added it again.

Can you please help me get all green checkmarks with my backups?

Thanks in advance,

 

Vince Hubbard

Operating Systems:

Comments 6 CommentsJump to latest comment

CraigV's picture

Hi,

 

SP2 is out so I'd recommend running LiveUpdate to get this installed before push-installing to any remote servers you might have.

Furthermore, on the server giving you issues, open up a command prompt and type: vssadmin list writers. Any writers not stable and running are in error and a reboot should sort this out.

Thanks!

 

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Vince Hubbard's picture

I'm sorry. My information wasn't correct. The Backup Exec server already is on SP2. SO latest BE Exec and latest Agent.

No writers are in error on the vm:

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {7a4dd8c5-322d-4f55-aa89-44ac5e1d6553}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {eeadb074-ce17-4cdc-8f43-26301ed330e7}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {426a78a5-6591-47a9-9f66-c8ef263950a4}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {e44426c0-a8b6-45ed-9e5a-f28a21c8fe75}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {0df53eff-e883-4e74-ac1c-a25f7c042cc7}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {eb060b72-4c3e-4443-af41-89fc5e70084b}
   State: [1] Stable
   Last error: No error

Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {c7f3d93e-ed20-4dbd-ae23-b6799f5c6850}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {026c0455-38a4-4543-b567-38fd11ad478c}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {7e3c3510-6f67-455d-aefa-6e57ade63162}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {d9be16be-f013-4441-aad5-85a072a4bf93}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {d8554077-d59f-4a66-80f3-cc858411658a}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {4b01bdc3-91bd-483f-944a-b4576260b487}
   State: [1] Stable
   Last error: No error

 

I haven't rebooted the server yet though. I'll let you know if that solves the problem.

Vince Hubbard's picture

I'm sorry for my very late response. The reboot didn't fix the error.
Still returns the same error message

CraigV's picture

...I'd recommend opening a support query with Symantec, and reporting back here with the solution before closing the query off.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Iesa Behbehani's picture

Hi Vince,

I will have a Symantec Tech Support Engineer join this thread to assist you.  

 

Thanks,

Iesa Behbehani 

iesa_behbehani@symantec.com 

Donald Eady's picture

Vince Hubbard

   Were you able to create a support case as suggested by CraigV? If so would you please DM me your case # so that i can take a look at the case progress and possibly lend a hand in finding a resolution. If you havent yet created the case please feel free to DM me you contact info so that i might be able to have one created and begin formally troubleshooting it with you.

I hope this posting was helpful