Has anyone been able to successfully recover a SLES 10 SP1 server using
FCP devices in a disaster recovery scenario? Recently, I attempted to do
so and the server failed to boot (either in normal or fail safe modes)
because the FCP devices that are normally attached to the server at my
home site were not available at my DR site. When I IPL'd the server at the
DR location, the server would find the mainframe 3390 devices that are
mirrored to the DR site via XRC , but failed to find the FCP devices since
the WWPN of the storage device at the DR site is obviously different than
the WWPN of the storage device at my home site.
To give a little background on the server, as I mentioned before it is a
SLES 10 SP1 server that runs as a guest of a z/VM 5.2 LPAR. I build the
Linux operating system (/, /usr, /var) on mainframe 3390 mod 3s that are
mirrored to the DR site via XRC. The user data (WebSphere file systems
/opt, /opt/apps, etc...) are mounted on FCP devices and the LUNs are
mirrored to the DR site via HDS TrueCopy.
In SLES 9, when I bring up the server at the DR site, it too would
obviously fail to find the WWPN of the FCP devices, but it would get to a
place where I can update the WWPN to point to my storage device at my DR
site (where the LUNs are mirrored to). I would then be able to reboot the
server with the updated WWPN and successfully access all my file systems
and bring up all my applications (i.e. WebSphere, Oracle, etc...).
This obviously does not work the same in SLES 10! As I mentioned earlier,
SLES 10 fails to boot because it can find the FCP devices since the WWPN
of my home site is not available from my DR site. It boots to a $ prompt
where it is limited to what I can do from the console session.
I spoke to IBM Development about this and they are still looking into
this.
Does anyone have any experience with this?
Ashley
*************************** IMPORTANT
NOTE***************************** The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
************************************************************************
----------------------------------------------------------------------
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
