Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

when LPM can't be done...

Status
Not open for further replies.

ogniemi

Technical User
Nov 7, 2003
1,041
PL
hello,

let's say there are two P6 servers configured with LPARs with live partition mobility so an LPARs can be moved between servers.

how to proceed in case the server with LPARs crashes? what is good plan to be prepared for such case? how to quickly (manually?) get vios on second P6 server ready to serve resources for the affected LPARS if LPM can't be used?
 
If the server with the LPAR crashes I don't see where LPM will come in to it.

The L part of LPM means live and it if has crashed it won't be live, will it!
 

Yes, it is clear to me. But I would like to know, if there is any way (besides e.g. HACMP) to quickly restore crashed server's configuration (VIO configurations and LPARs) on the other server with the same/symetrical hardware configuration (normally being ready for LPM)? Are there any VIO configuration snapshots which can be done before the crash and which could be applied on second server in case of total crash of 'primary' system?
 
I don't see why you couldn't backup your profile data from one system, restore it to another similar setup, or use the system planning tool to migrate the profile information.

Flip your SAN zoning to the other system and boot it up.

If it is (was) a LPM environment all the client storage would be on the SAN already. You could already have your VIOS partitions up and running with the client partitions and virtual resources mapped and ready to go.

When the first system goes pop, boot up system 2 and off you go.
 
hmmm,,, there is said, that during live partition mobility tasks:

"The virtual target devices and virtual SCSI adapters are created on the target system. Using the lsmap command on the target VIOS, before the migration, you'll notice that there are no virtual SCSI or virtual target device mappings, as shown in the following figure. "


So how to quicly create all this configuration (eg. having source vios configuration snapshot if possible) applying a source vio required configuration to be able manually activate LPARs which were running on crashed system?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top