Setting up Syamantec 7.1 and a Dell ML 6020 for 2- separate networks

[abtexas]

 We purchased a Dell ML 6020 Tape Backup unit and a Dell R710 server (36GB 2x 6-cores) to be used as the Media and Management server to backup our Test and Dev environments. The Test and Dev environments will consist of VMware and physical servers in each. However, the dilemma is that the environment includes software and server configurations that require the use of host-names that are the same in each environment and therefore separated by VLAN segments.  Unfortunately - this is the way the older code was done some time ago - the good news is that this will go away but this is the hand-dealt today.

So, to paint the picture for what we are trying to-do - we need to have a way to backup to separate environments using the same host names in each segment using one media/manager server. This is a short-term fix but in government it takes a while to get an order processed (months).

A. The management server is in the management domain (has leg in each VLAN/domain segment)

B. the Test and the Dev environments share the same SAN fabric (EMC SAN)

C. The environments have host-names that are the same because of the software requirements - in both segments / environments

D. We have 6 - drives with direct connections to 2 - SAN switches (3-each) in the SAN fabric

How do we configure the Media/Manger server to backup both environments based on the configuration we have today?

[Dan33 · Accepted solution]

I took over an environment where they did something similar except they had 2 nic's in a server, 1 for prod and 1 for a backup vlan. They used the host file make use of the other VLAN.

You could try something similar. On the master/media server add entries in the host file, eg <IP> Server1-dev, leave the test servers as Server1 or use DNS.

When you create your policy you would have to add client Server1-dev. If you have to restore you would also have to use Server1-dev as the client.

Can't remember if the client name needed to be changed within the netbackup agent or not.

Obviously this will not work well if your servers do not have static IP's

Seems a little messy but it was working.

Ideally you would want to have different names for all servers across all domains as it will get confusing down the track, if it hasn't already. Once you have different names you could use DNS and the proper server names.

Edit: Just had a different thought. Have you tried using the FQDN as the client name for the policies?