Hello list, Has anyone addressed the issue of how to do a planned DR test? Here are the assumptions: -) There is a production z/VM+Linux LPAR at the primary data center. -) There is a DR site where the production LPAR volumes, etc. are replicated. -) A planned DR test is necessary.
In a real disaster, the DR site will use the same IP/DNS as the production site which by definition is down. However, to do a planned DR test, different networking information is required so as to not conflict with the primary site. So how do you tell: (1) z/VM - bring up TCPIP with this alternate networking information, and (2) Each Linux to come up with alternate networking information. Then the DR site can be tested. The contingency of a real disaster occuring during the DR test must be addressed. At that time the DR test must be abandoned and the DR site must be brought online with the real network information (so modifying the Linux networking info in the DR site file systems is not a good option). I can see how you can address (1) - maintain a second TCPIP service machine - say TCPIP2. Bring up z/VM without AUTOLOG and manually bring up TCPIP2. But how to address (2)? Is anyone doing this? "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
