Cannot solve this problem

[momaymm]

How to resolve this problem ?

Picture as below

[CraigV]

Hi,

Check below:

0xe000fe30 - a communications failure has occurred.

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

Also obviously make sure that if the remote server has a firewall running, that port 10000 is open. You can also make sure that the remote server is publishing back to the media server correctly on the RAWS agent icon.

Thanks!

[momaymm]

On server not open windows firewall

[pkh]

Check the following

1) on the remote server, check that the remote agent service is running.  Also check the Windows Eventlog for any remote agent service failures.

2) open the remote agent utility and make sure that it is publishing correctly to the media server

3) make sure that you can ping from the media server to the remote server and vice-versa

4) make sure that there is no firewall blocking port 10000

5) on the remote server, check that there are no other applications using port 10000.

[momaymm]

Check the following

1) on the remote server, check that the remote agent service is running.  Also check the Windows Eventlog for any remote agent service failures.

ANS> remote agent service is running is OK /check the Windows Eventlog for any remote agent service failures.  Is Show > The VSS service is shutting down due to idle timeout.

2) open the remote agent utility and make sure that it is publishing correctly to the media server

ANS> It's OK

3) make sure that you can ping from the media server to the remote server and vice-versa

ANS>  Can Ping  don'thave time out

4) make sure that there is no firewall blocking port 10000

ANS> Windows firewall not open

5) on the remote server, check that there are no other applications using port 10000.

ANS>   Assing already on windows firewall

[momaymm]

Snapshot Technology: Started for resource: "\\Server\D:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot technology used by VSS for volume D: - 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: "\\Server\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: 6/16/2014 9:18:55 AM

No appendable media could be mounted.
Switching to overwrite operation on scratch media.

Drive and media information from media mount: 6/16/2014 9:18:57 AM
Drive Name:  (Full Backup)
Media Label: B2D035908
Media GUID: {b17d4744-f741-496d-a556-e7fe44a24168}
 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.

[VJware]

Do you receive the communications failure on only one backup job (i.e. for a specific server) or for random jobs ?

If only for one server, do you receive this failure upon a particular schedule or at any random time ?

Is there any Event ID 1000 logged on the BE media server or the affected remote server ?

[momaymm]

Yes this job error only on,  On BE Server don'thave Event ID 1000

[momaymm]

I deleted traget server on BE console and then  add server to BE console again.   I create job of traget server have error pop-up

[VJware]

Is BE 2012 updated with SP4 ? If yes, can you confirm what is the size of the BEDB ?

[momaymm]

for BEDB  is 4GB     LOG is 900MB

[pkh]

See this document for a solution to your problem

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

[momaymm]

Already compact Database from 4 GB  to 200 MB .

[VJware]

Have you tried recreating the backup job after reducing the BEDB size ? If yes, do you receive the same error ?

[momaymm]

I try to re-create job and add server to BE already. and run the job same the error .

[momaymm · Accepted solution]

For slove this problem  just uncheck IPv6 in networkcard