Symanec Protection Suites

 View Only

Backups fail due to Firewall and No Traffic Logs

  • 1.  Backups fail due to Firewall and No Traffic Logs

    Posted May 18, 2012 07:52 PM

    I'm currently in the process of deploying SEP 12.1 in our enterprise. I'm having problems with the Firewall on our backup server and Hyper V host. The backup server is a Windows Server 2008 Std, 64bit with Backup Exec 2010 R3, and the Hyper V host is a Windows Server 2008 Ent, 64bit.

    I have installed the SEP client on both these systems with the firewall. This caused problems with both systems due to the firewall. The backup server would fail to communicate with the Hyper V server for backups. Eventually, I was able to determine that IPv6 communication between these two Windows servers was causing the backups to fail. I created a rule in SEPM to allow IPv6 for Backup Exec, and it was working. Backups were successful for a couple of weeks. Then MS updates forced a restart on both of these systems.

    Since the updates and restart on these systems, I have two problems. One, the backups of the Hyper V host and client systems are failing again. Second, SEPM is not collecting traffic logs from the clients so I have no information to further troubleshoot the failed backups.

    At first, I thought that MS KB2688338 had caused a problem with communication between SEPM and the clients. However, even after uninstalling this update, the backups are still failing.

    I have verified communication between the SEPM server and the clients, but there is still a problem with the traffic logs and backups.  Any help would be greatly appreciated.