Hi all, We are ready to implement our new mirror code and are writing documentation on this process. The one thing I have not figured out is how to turn the mirror into production.
The server itself is pretty easy as I have a record that has IP address of production machine in a record. What I do not understand is how to update the clients. Production and Mirror are on different subnets so the built client on the machine will not be able to connect to without a change to 4Dlink file. What I was hoping was to use a DNS name and simply change the IP address it points to so if I had Server_prod which pointed at 192.168.5.5 Server_Mirros which pointed at 192.162.5.17 The IP’s are of course not the real ones in use I could simply change DNS name and voila each client would connect seamlessly. This code is for a large hospital and changing DNS names like this does not seem to be in the cards. Can anyone tell me how they are doing this Thanks and regards Chuck ------------------------------------------------------------------------------------------------ Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064 mailto:cjmiller<AT SIGN>informed-solutions.com Brookline, MA 02446 USA Registered 4D Developer Providers of 4D and Sybase connectivity http://www.informed-solutions.com ------------------------------------------------------------------------------------------------ This message and any attached documents contain information which may be confidential, subject to privilege or exempt from disclosure under applicable law. These materials are intended only for the use of the intended recipient. If you are not the intended recipient of this transmission, you are hereby notified that any distribution, disclosure, printing, copying, storage, modification or the taking of any action in reliance upon this transmission is strictly prohibited. Delivery of this message to any person other than the intended recipient shall not compromise or waive such confidentiality, privilege or exemption from disclosure as to this communication. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
