07-09-2009 07:10 AM
Solved! Go to Solution.
07-09-2009 11:12 AM
07-09-2009 07:42 AM
07-09-2009 07:45 AM
If I were trying to configure Backup Exec (or any backup product) to backup serverA to serverB over a dedicated NIC, here's how I would set it up (this assumes that Backup Exec is installed on serverB and it is remotely backing up serverA):
1. On both serverA and serverB, create four entries in each of their hosts file (remember that the hosts file on a Windows Server 2003 server is "C:\WINDOWS\System32\drivers\etc\hosts"):
serverA 10.x.x.x
serverA-bkp 192.168.0.101
serverB 10.x.x.x
serverB-bkp 192.168.0.102 # if this is the correct Class C IP addr for serverB's second NIC
2. In Backup Exec on serverB, configure it to backup serverA-bkp. Do not use "serverA" as the hostname of the client that you want Backup Exec to backup.
3. Run a backup. You should now see the backup traffic going from serverA to serverB over the dedicated 192.168.0.x network segment.
Alternatively, if Backup Exec is installed locally on serverA instead of serverB:
1. Create the hosts file entries on serverA and serverB, as listed above.
2. In Backup Exec on serverA, define your backup disk target to be \\serverB-bkp\sharename (substitute the actual name of the CIFS share in place of "sharename"). The key point in this step is to use "serverB-bkp" as the hostname in the CIFS path.
3. Run a backup. The backup data from serverA should now go to serverB's CIFS share over the dedicated 192.168.0.x network.
The key thing to keep in mind when you put multiple NICs in a server (regardless of the server's operating system) is that each IP address on the server should resolve to a unique hostname. By adding a "-bkp" suffix to the hostname of each server on the dedicated 192.168.0.x backup network, you are ensuring that you can specify the exact path for the backup data to take.
07-09-2009 08:05 AM
07-09-2009 08:43 AM
Did u try sepcifying the nic for the backup as I suggested before ??
07-09-2009 08:48 AM
07-09-2009 09:38 AM
07-09-2009 09:47 AM
07-09-2009 10:03 AM
07-09-2009 10:21 AM
07-09-2009 10:27 AM
07-09-2009 10:36 AM
07-09-2009 10:52 AM
using a Windows Explorer to connect to a share on serverB-bkp came up with an error "could not find server..."
BUT
I decided to do a little tinkering, I put my setup back to the original and decided to firewall NIC1 on serverB with an exception for "remote desktop" only. I left NIC2 un-checked in the firewall setup basically leaving it wide open on serverB. Low and behold the ^%#$% thing is working using NIC2. I did not want to change the connection order on serverA but I think that might have made a difference. The reason for leaving the connection order at NIC1 on top was to have network users with the most priority.
Basically I forced windows to use NIC2 for traffic between serverA and serverB.
07-09-2009 11:12 AM
07-09-2009 11:20 AM
07-09-2009 11:38 AM