Diego,

 I have implemented this configuration with NBU on Solaris (No LANMAN of course), however For the purposes of Global Failover with Windows, using the LANMAN agent you have the option of associating multiple IP addresses with different subnets against the same Virtual Name.  Additionally, the LANMAN agent can update CNAME records during a wide-area failover. There are multiple attributes that could provide the necessary results that you are looking for.  I would consider starting with DNSOptions using "UpdateAll" & "PurgeDuplicates".

You may also want to consider adding entries to the AdditionalDNSServers so that during normal operations all Name servers can be kept in sync.

You can also refer to the following document starting on page 55 for more details.

https://sort.symantec.com/public/documents/sfha/5.1sp2/windows/productguides/pdf/VCS_BundledAgents_51SP2.pdf

I have found many of the LANMAN attributes can be quite fickle depending on the type pf environemnt you are working in.

Hope this helps,

Joe D 

Hi Diego,

Joe is right, on Windows with GCO we set the Lanman DNSOptions attribute to include PurgeDuplicates.  When the group is failed over this will cause the Lanman resource to remove the DNS records for the virtual server name for the other site and put in the DNS records for this site.

The UpdateAll and AdditionalDNSServers are more dependant on your environment.  You might need them and you might not.  I would recommend checking out the Lanman resource attributes in the Bundled Agents guide for details on what each of the attributes does to determine if you need them set or not.

Let us know if you have any more problems or concerns.

Thanks,

Wally