The DDNS ( Dynamic DNS ) should take care of that, and remove the old entry after some time ( since the old IP is not responding anymore to DNS updates - the VDM is unloaded ).
If you are not using DDNS, then it must be done manually.
In my case when the VDM gets up on the destination site the DNS record isn't updated. The VDM creates a new DNS record with the same name leading to the backup ip address so clients using UNC sometimes get the old ip address.
This is why i'm looking for the exact steps performed by the switchover mechanism.
From what I can tell, if you wait long enough the DNS record gets replicated eventually by Active Directory but that is hogwash to me. During testing I have always had to manually update the DNS entries (due to my impatience...) and even then Windows machines cache DNS information so a cutover to our remote Celerra takes up to 15 minutes. The actual time for the remote side to come "up" on the Celerra is just a minute or two but name resolution always takes longer to get right.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
272
0
Posted April 19th, 2011 10:00
take a look at document "Using Celerra Replicator v2" ..there is a section "Appendix: Setting up the CIFS replication environment"