Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup Exec 2012 SP4 not backing up Exchange 2010 SP3 DAG with new isolated Backup LAN

Created: 04 Jun 2014

My current Media server is a physical server running Symantec Backup Exec 2012 SP4 running on Windows Server 2008 R2 configured as only Media server, which has connectivity to the organization Production LAN with (configured with static IP, net mask, gateway and DNS) and also recently added a separate Private Backup LAN (configured with separate IP and net mask).

Exchange mail servers is 2010 SP3 running on Windows Server 2012 HyperV vms.
Exchange 2010 DAG seems not to work well running backup on a isolated private backup LAN w/o DNS to resolve production virtual IP and FQDN of DAG.

I have a question on how to design or implement separate dedicated backup LAN for backup so that Exchange 2010 DAG could be backup via backup LAN.

eg. Production LAN IP on Media server & Client Servers

- IP: 10.101.x.x
- Subnet Mask: 255.255.255.0
- Gateway: 10.101.x.250
- DNS: 10.101.x.2

eg. Backup LAN IP on Media server & Client Servers

- IP: 10.10.1.x
- Subnet Mask: 255.255.255.0
- Gateway: None
- DNS: None

We are running the latest version of Backup Exec 2012 SP4 and anyone could do with guidance on how others may have implemented a totally dedicated private backup network.  Also are there any issues encountered on best practices that need to be followed in using backup LAN. Anyone assistance would be helpful.

Thanks.

Operating Systems: