Backupexec DFS-R issue

[marcin_stachurs]

Hello,

Our client is using DFS-R on Windows Server 2008R2.

We perform full backup's of three DFS machines in the customer's environment through Shadow Copy Component.
Customer registered thet DFS Replication stops and combines it with the backup / restore of DFS machines.

The client requires clarification.
How backupexec'a agent affects the DFS service?
Does it stop at the time the snapshot, or for the duration of the entire backup job, and maybe quite "hot".
Is it possible to stop the replication of the backup and did not get up?

Thanks for help.

Greetings

Marcin

[Ananya_Bhattach]

Which version of BE are you on?

If you are backing up through shadow copy components there is no reason why the DFS Replication Service is going to stop and start.

How to backup DFSR data can be found here : http://www.symantec.com/docs/TECH56841

Restoring DFSR Data : http://www.symantec.com/docs/TECH85354

I will wait for more expert opinion on this

[marcin_stachurs]

BE 2012 SP2

On event log on DFS server we have 1102 and 1104 events. Pointing to stop replication for approximately 11 seconds. It's time to take snapshot on backup jobs. Restore jobs are stopping replication for the duration of the entire task.

We asked customer for more logs. So far, we found that the task of data restore stopped replication and does not start again.

[marcin_stachurs]

Can someone explain an error?

Backup Exec Alert: Job Failed (Server: "fileserver") (Job: "fileserver Restore 00105") fileserver Restore 00105 -- The job failed with the following error: The Backup Exec server could not connect to the remote computer. Ensure that a Backup Exec agent is installed and running on the remote computer. If a Backup Exec agent is installed, ensure that it is the correct version.

For the future several questions...

Why communication has been interrupted?
We know that the server continued to work and he had a network connection.

Why DFS replication doesen't start after an unsuccessful restore Job?

Is it possible that the problems resulted from the VSS writer error?

We found VSS error (ID 12289) on fileserver - 3 minutes after restore job error.

[Ananya_Bhattach]

I request you to open a support case for this issue.

Also, it is best to upgrade to the latest release of the product. SP 4 for BE 2012 is out and is available at http://www.symantec.com/docs/TECH212772

I would advise you to upgrade to the same service pack and push it out to the remote servers as the first step.