×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I'm currently running PhowerHA Geographic Mirroring between two sites. The iASP's are located on internal disk.
If I have a hard outage on the Primary Server, I've found that when I start up mirroring again, PowerHA initiates a FULL resync of the mirror to the target system.
I've never switched to running at our DR site because of the difficulty (either perceived or actual) of having to switch back.
I'm now looking into replacing the Geographic Mirroring that runs on my IBMi Power Servers with Global Mirroring of an iASP residing in a Storwize V7000 SAN.
Since I've now externalized the iASP storage and mirroring, I'm assuming I could do the following after a CRASH of my production server:
1. Switch the V7000 at our DR site to Primary and the V7000 at my production site to secondary...
2. Vary on the iASP to my DR IBMi server
3. Run my business on the DR server while I repair my production system (I realize I'd have some network interface configuration changes too...)
4. After the production system is repaired and ready to be brought back online
5. Vary off the iASP on my DR IBMi server
6. Switch the V7000 at our production site to Primary and the V7000 at my DR site to secondary...
7. Vary on the iASP to my production IBMi server
8. Resume NORMAL operations.
There would be no need for a full resync of the mirror from Production to DR or DR to Production.
I'm pretty sure this is how it would work, I'd just like conformation from someone who has actually had to do this.
Kenneth
Kenneth E. Graap
NW Natural
System Administrator for IBM Power Systems
503.226.4211 x5537
http://www.linkedin.com/in/kennethgraap
midrange.com
