Does spoofing, on DR server, need to be removed when failing over to DR?
We are revisiting our DR strategy for RTC/RRC 5.0.2 on Windows/Tomcat, and found spoofing
(with line "<DRserverIPaddress> <DNSalias4publicURI4CLMserverOnPRD"
in the C:\Windows\System32\drivers\etc\hosts file) was used to verify that DR is in working order.
We did not find any infos in the failover to DR procedures on the removing of spoofing: We believe that does not matter, the spoofing should not have any harmful effect on the running of CLM in DR.
Wonder if we overlook anything, so thinking.
Accepted answer
I don't think spoofing has ever been suggested in DR planning, and that's probably why you cannot find any information about it. IIRC the only situation that spoofing is mentioned in official documents is when setting up a staging environment using production data for evaluating upgrade process.
I don't know how you will switch over to the DR server in case the PRD is down. If you simply change the DNS entry to point the FQDN to the DR server address, it will have the same effect as the entry in the hosts file. In this case, the particular line in the hosts file is just fine. But if you re-assign the PRD server IP address to the DR server (which is rare), then you must remove the line in the hosts file.
I don't know how you will switch over to the DR server in case the PRD is down. If you simply change the DNS entry to point the FQDN to the DR server address, it will have the same effect as the entry in the hosts file. In this case, the particular line in the hosts file is just fine. But if you re-assign the PRD server IP address to the DR server (which is rare), then you must remove the line in the hosts file.
Comments
Thx Don,
If spoofing is not used, how could we verify if DR works on PRD DB's, with PRD live? The only way to verify, other than spoofing, is the real DR test, with PRD down?
I don't think you can make two applications connect to the same database at the same time. It is way too easy to cause data corruption, even when you think you're not updating any records. The application should refuse to do so anyway. That's why we use the term "cold standby" in the DR planning.