...
PowerHA can be used in conjunction with an IBM i hosting I environment to provide disaster recovery for a production partition. This This is not a standard PowerHA cluster/IASP environment, but rather a full system replication solution used by some customers as a DR solution. In In this environment, the full production partition including the operating system is hosted in a network storage space within an IASP on the host partition. That That IASP is then replicated using PowerHA to a backup host partition. In In the event of a failure of the production partition, the target IASP and NWSD can be varied on, and the production partition can be IPLed on the second system.
In this environment, the production partition does not utilize an IASP, only the host partition has the IASP. HoweverHowever, there are several disadvantages of this technology compared to a traditional PowerHA environment where the production data only is within the IASP.
- There is no automatic failure detection of the production partition. A A failure of the host partition would be detected, but no monitoring capability exists on the production partition.
- Since the entire production partition is being replicated, there is no ability to reduce OS upgrade time using this technology.
- For a planned switchover or a save from the target system, to be ensured a consistent copy, the production partition must be shut down before the target host and client can be varied on and IPLed.
- Before doing a system save from the target partition, the production system should again be shut down before detaching the IASP. A A quiesce (going to restricted state or CHGASPACT) of the production system will help to reduce IPL time and also reduce the risk of damaged objects, but powering down the production system is the only way to guarantee that no partial objects are left in memory. Journaled Journaled objects should be recovered during the abnormal IPL of the target partition. NonNon-journaled objects may be marked damaged and would need to be recovered manually, just as in the case of a single system failure/recovery scenario.
- An unplanned failure of the production partition requires an abnormal IPL of the target, and may require some manual recovery of non-journaled objects.
...
If the above steps are not followed, or in the case of an unplanned failure of the production system or of the host system, pages in memory may not have been written to disk on either the production or host system. When When varying on the target IASP, non-journaled objects may be marked as damaged, and those objects would need to be recovered from a system save.
...
Here is a link to a document on how to set up an IBM i hosting IBM i environment. This This document discusses many forms of virtualization available on IBM i. Chapter Chapter 2 is dedicated to IBM i hosting IBM i.
...
Here is a link explaining how to set up a PowerHA replication environment for a production server which is being hosted by IBM i. This This document is an iSCSI solution guide, but the directions also pertain to an IBM i hosting IBM i environment. The The relevant section of this guide for PowerHA implementations is section 7.4 - Implementing IBM i clustering for integrated servers.
...