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
available backups and
do the restore all over again. If you are using your latest backups, just tell
your users that you are now the production system.
/Tom Kern
--- Michael MacIsaac [EMAIL PROTECTED] wrote:
Has anyone addressed the issue of how to do a planned DR test? Here are
the assumptions
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?
1) Ensure the VM install has a unique MACPREFIX in SYSTEM CONFIG.
2) Ensure that each NICDEF or
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Michael MacIsaac
Sent: Friday, September 02, 2005 11:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: How to do a planned DR test?
Hello list,
Has anyone addressed the issue of how to do a planned DR
So how
do you tell:
(1) z/VM - bring up TCPIP with this alternate networking
information, and
I think also that VM TCPIP is smart enough to look at the system ID and
execute a specific profile based on the system id. So, if your normal
systemID is FOO1, if you have entries in SYSTEM NETID on
David wrote:
I think also that VM TCPIP is smart enough to look at the system ID and
execute a
specific profile based on the system id.
It is and that works well (that's how we do it). But MPROUTE is not so
clever in the current release. So you still need to work that one out
with either an
