asked on Backup Exec, dual nic, backup network issues
Backup Exec 2010 R3 64-bit on Win2k8 R2 64
two nics, Production and Backup, backup segment uses two 8 port gigabit un-managed switches on the 192.168.1.0 subnet.
BUE server has daily differential jobs for File servers, separate Exchange 2k3 and Exchange 2010 jobs that are full backups (2010 has GRT enabled). Exchange jobs backup to iSCSI DroboPro DAS w/7TB total, 3.5TB free space. All nics are set to full 1gig, backup nics have all offloading options disabled, flow control enabled, *@wirespeed disabled, and the only items each backup nic has enabled is IPV4 and File/Printer sharing (the last one only because I cannot find docs saying to disable it). The BUE server also has a hosts file specifying each 192.168 address along with the simple and FQDN of all the servers physically attached to the backup lan. Pings from BUE to any source server all resolve the correct 192 address. Production nics on all servers have all static IP's in the 10.1.1.x range.
i.e. hosts file shows:
192.168.1.7 jak-2k8-exch
192.168.1.7 jak-2k8-exch.domain.domain
source server can ping BUE server and resolve 192 address, BUE server can ping both hostnames listed and resolve correct 192 address.
The problem lies in that for teh Exchange 2010 backup job, if I specify to use the backup nic the job fails saying
:"The media server could not connect to the remote computer. The remote computer may not exist on the selected subnet. Try an alternative network interface, or allow Backup Exec to choose any available network interface."
The server IS available on the selected interface.. if I tell this job to let BUE pick the interface it ALWAYS picks the production side. In the job logs it says the "Resource name: \\192.168.1.7\Microsoft Information Store\Mailbox DB 2" Which is the correct path but how is it talking to the Backup subnet via the Production nic?
Can anyone help shed some light on this? What am I doing wrong?
two nics, Production and Backup, backup segment uses two 8 port gigabit un-managed switches on the 192.168.1.0 subnet.
BUE server has daily differential jobs for File servers, separate Exchange 2k3 and Exchange 2010 jobs that are full backups (2010 has GRT enabled). Exchange jobs backup to iSCSI DroboPro DAS w/7TB total, 3.5TB free space. All nics are set to full 1gig, backup nics have all offloading options disabled, flow control enabled, *@wirespeed disabled, and the only items each backup nic has enabled is IPV4 and File/Printer sharing (the last one only because I cannot find docs saying to disable it). The BUE server also has a hosts file specifying each 192.168 address along with the simple and FQDN of all the servers physically attached to the backup lan. Pings from BUE to any source server all resolve the correct 192 address. Production nics on all servers have all static IP's in the 10.1.1.x range.
i.e. hosts file shows:
192.168.1.7 jak-2k8-exch
192.168.1.7 jak-2k8-exch.domain.domain
source server can ping BUE server and resolve 192 address, BUE server can ping both hostnames listed and resolve correct 192 address.
The problem lies in that for teh Exchange 2010 backup job, if I specify to use the backup nic the job fails saying
:"The media server could not connect to the remote computer. The remote computer may not exist on the selected subnet. Try an alternative network interface, or allow Backup Exec to choose any available network interface."
The server IS available on the selected interface.. if I tell this job to let BUE pick the interface it ALWAYS picks the production side. In the job logs it says the "Resource name: \\192.168.1.7\Microsoft Information Store\Mailbox DB 2" Which is the correct path but how is it talking to the Backup subnet via the Production nic?
Can anyone help shed some light on this? What am I doing wrong?
Storage SoftwareNetworkingWindows NetworkingExchangeWindows OS
Last Comment
Ben Hart
ASKER
Oh yes.. and Windows Firewall/Internet Connection Sharing is disabled via GPO.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Seems to have fixed it.. thanks!