RE: Global Mirror via Storwize V7000

I agree, after a hard stop of either side of the PowerHA pair, the iASP will
fully replicate. Regardless of the storage being used.

The potential exception is if the SAN is doing global mirroring exclusive of
PowerHA, ( so the SANs have Global Mirroring licensed not the POWER system)
then it might not corrupt the iASP.

I'll still bet on the complete rebuild of the crashed system.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Friday, July 24, 2015 7:27 PM
To: Midrange Systems Technical Discussion
Subject: Re: Global Mirror via Storwize V7000

I wouldn't be so sure that your V7000 wouldn't do the same thing!
Remember that POWERHA is still in charge of which is on line and which is
off line. While the actual replication can be delegated to the SAN but the
control and knowledge of it is still in the hands of POWERHA.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 7/24/2015 3:36 PM, Graap, Kenneth wrote:

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.