I am having an issue, one that doesn't seem to have an answer.
My office just upgraded from Windows 2003 to Windows 2008, and from Exchange 5.5 to Exchange 2010.
We have one main office in Washington DC and a satellite office in Denver Colo. Denver is our DR site, so one of the two mail servers functions as a redundant repository for the mail store DB's all of which are passive. The servers in the DC site are the DAG, CAS and MBX servers. The issue is that when I run the backup from the DC site, we hit the DAG server, in DC, first, which acts as the parent and calls child jobs for the MBX servers.
We have 3 MBX servers in DC and one in Denver. Since the backup hits the Denver server, and due to the fact that it runs across the WAN, it takes about 20 or so hours to backup, and has a through put of 100 to 300 Kbps.
Everything I am finding in reference to backing up Exchange 2010 says that it has to go through the DAG server, however this is a very big bandwidth hog when trying to backup the Denver MBX on the DC backup server. Is there some way to configure NBU 7.1.0.4 to do a local backup of the MBX server without hitting the DC DAG? I am asking this as I am thinking that if the Denver backup server contacts the DC DAG, it will have the same throughput and bandwidth issue with the WAN.
Thank you