|
1) The target system will be totally shut down during replication.2) If you 'crash' the source system (i.e. power outage, flood, etc.) the target system will experience a very Abnormal IPL. Journaling is MANDATORY in that environment. 3) If you want to use the backup system for backups for example you'll need to understand that environment and use the quiesce functions etc correctly or the backup will trip over damaged objects. 4) You will use more bandwidth than just replicating the iASP with data and programs because now EVERYTHING that guest does, including printing and any swapping etc all gets replicated.
- Larry "DrFranken" Bolhuis www.frankeni.com www.iDevCloud.com www.iInTheCloud.com On 5/7/2015 3:47 PM, Evan Harris wrote:
Hi Thanks for the replies so far Patrick: To use the same IP address I guess they would need to be in the same network - correct ? Also, I have not seen any details on how to tag the IP other than references to AIX. Do you have a reference ? Jim: By create target iASP do you mean populate it with data as opposed to creating the disk pool I think STRASPSSN is the start replication command - is that the command you are referring to ? When you say not enough CPU allocated to PowerHA - do you mean the source or tarket LPAR, or both How much CPU (in your estimation) does PowerHA typicall add (I realize this is probably an "it depends" type question) The scenario we are looking at is replicating a couple of guest LPARs from one site to another, in different networks. No VIOS, just i on i hosting. That is good feedback about the network saturation. We are wanting to run a test first to gain some understanding of the numbers involved and get a feel for how it works. Thanks again, this is most helpful.--Regards Evan Harris
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.