Storwize V7000 With IBM I - Implementation

Storwize V7000 and IBM i pre-sales enablement
IBM Storwize V7000 with IBM i

Implementation
Jana Jamsek
Advanced technical skills, Europe
© 2014 IBM Corporation

Agenda
 External storage options for IBM i
 IBM i storage management
 Connecting V7000 to IBM i
 Defining the LUNs for IBM i
 Boot from SAN
 Solid State Drives in V7000 for IBM i
 Zoning teh switches
 Multipath
 Implementation steps
 IBM i architecture important for Copy services
 V7000 Copy services
 Solutions for IBM i with V7000 Copy services
 PowerHA SystemMirror for i with V7000 Copy services
Implementing V7000 with IBM i
3 9/18/2018 © 2014 IBM Corporation

IBM i and Storage systems IA
DS8000 V7000, V5000, V3700
Archive
IBM i
SVC
VIOS V840
Tape
Libraries
& Drives
DS4000 DS5000
XIV
DS6000 ProtecTIER

Note: The shown connections with VIOS refer to either VSCSI, NPIV or both
 SVC and Storwize V7000 offer five 9s (99.999%) availability

– Average annual downtime less than 5 minutes
 Storwize family is ideal for any organization’s disaster

recovery plan
– Data mirrored between production and disaster recovery sites
in almost real time
 Over 55.000 systems purchased

• Over 130.000 total enclosures deployed
• Over 1.6 Exabyte's of capacity
Numbers as of March 31, 2014

Storwize Family
Packages
IBM SAN Volume Controller
(Virtualization System; No Storage)
IBM Storwize V3700 (Entry)
IBM Storwize V7000 (Midrange)
IBM Storwize V5000 (Midrange) System Functions
Thin provisioning
Easy Tier
IBM Real-time Compression
IBM Storwize V7000 Unified (File)
IBM SmartCloud Storage Access
(Cloud)
Remote replication
Integrated Options (synchronous and asynchronous)
 IBM Flex System Storage Virtualization (IBM and non-
 V840 IBM)
 SVC-DH8

IBM Storwize V7000 at a Glance
Modular Hardware Building Blocks
2U
Enterprise-level Software Capabilities

Virtualization and Availability Efficiency
RAID 0, 1, 5, 6, 10 Thin Provisioning
Storage Virtualization Easy Tier
Non-disruptive Data Migration
Local Mirror Replication
FlashCopy
Manageability Global & Metro Mirror
New User Interface Application Integration
Integrated SAN-wide Management Disaster Recovery Automation
Integrated IBM Server and Storage Management IP or Fibre Channel © 2014 IBM Corporation
IBM i Single-level Storage
IBM i Partition
I5/OS Partition Single-Level Storage
Main Memory
IBM i sees all disk space and the main memory as one storage area.
It uses the same set of 64-bit virtual addresses to cover both main memory and disk space.
IBM i Oobject orientated architecture
IBM i takes responsibility for managing the information in auxiliary storage pools.
The system places the file in the best location that ensures the best performance.
It normally spreads the data in the file across multiple disk units. © 2014 IBM Corporation
Translation from 520 byte blocks to 512 byte

blocks
 IBM i disks have a block size of 520 bytes.

 Most fixed block (FB) storage devices are formatted with a block size of
512 bytes so a translation or mapping is required to attach these to IBM i.
 Translation of blocks: For every page (8 * 520 byte sectors) it uses
additional 9th sector; it stores the 8-byte headers of the 520 byte sectors
in the 9th sector, and therefore changes the previous 8* 520-byte blocks
to 9* 512-byte blocks.
 The needed disk capacity on V7000 is 9/8 of the IBM i usable capacity.
 The usable capacity in IBM i is 8/9 of the allocated capacity in V7000.

Native connection of V7000 to IBM i
POWER7 or later
 Requirements:
Hardware: IBM i
– POWER7, POWER8
Minimal software and microcode levels FC adapters

– IBM i V7.1 TR6 and PTFs MF56600,
MF56753, MF56854
– or IBM i V7.1 TR6 Resave 710-H
– V7000 code 6.4.1.4 SAN
Fabric attach
– FC EN0A/EN0B – 16Gb adapter
– FC 5735/5273 - 8Gb adapters
Direct attach V7000


Native connection - pros and cons
 Doesn’t require VIOS

 No need for resources in VIOS
 Requires relatively many FC adapters
–Each LPAR needs at least one adapter
–If PowerHA is used, sysbas and IASP require separate FC
adapters
 Can be implemented without SAN switches
–With 4Gb adapters
 Can not be used in Blade or PureFlex

Native connection - facts
 Maximum 64 LUNs per port

 SCSI Command tag queuing queue-depth is 16
 4Gb adapters feature number #5774 or #5276
– Point to point connection without a switch is supported
– Connection with SAN switches is supported
 8Gb adapters feature number #5735 or #5273
 16Gb adapters feature number #EN0A or #EN0B
Queue depth: the maximal number of I/O operations to one LUN at the
same time

VIOS_NPIV connection of V7000 to IBM i
Requirements for VIOS_NPIV

connection
 Following are the requirements for NPIV connection
of V7000 to IBM i:
 Hardware:
 POWER6 or higher
 8-Gb or 16-Gb adapters in VIOS
 NPIV enabled switches
 Minimal software and microcode levels
 IBM i V7.1 TR6
 VIOS 2.2.2.1
 V7000 6.4.1.4
 PowerHA group PTF SF99706 level 3
 Note: PowerHA group PTF SF99706 level 4 is
required for managing PowerHA with V7000 in GUI,
and for LUN level switching with V7000.

VIOS_NPIV connection - pros and cons
 Requires VIOS and the resources for VIOS

 Relatively straight-forward implementation
 Requires 8Gb or 16Gb adapters in VIOS and NPIV enabled switches
 With many IBM i LPARs, can drastically reduce the needed number of
adapters
 Big IBM i LPARs still need more physical adapters in VIOS
 Multipath functioning is very similar to native connection
 Nagligible performance overhead comparing to native connection

VIOS_NPIV connection - facts
 Maximum 64 LUNs per virtual FC adapter

 Client virtual FC adapters in IBM i
 Corresponding Server virtual FC adapters in VIOS
 In VIOS: Mapping the server virtual FC adapter to a port in the adapter
Example vfcmap -vadapter vfchost1 -fcp fcs0
 Maximum 1 client virtual FC adapter from one IBM i LPAR mapped to a
port. Up to 64 virtual FC adapters each from different IBM i LPAR can be
mapped to a port
 Zoning of SAN switches and Hosts in V7000 are done for the WWPN of
Client virtual FC adapter

VIOS VSCSI connection of V7000 to IBM i
Requirements for VIOS VSCSI

connection
 Hardware:
 POWER6 or higher
 Minimal software and microcode levels
 IBM i level V6.1.1
 IBM i v 7.1 is required for Power HA support
 VIOS level 2.2.
 V7000 level 6.1.x

VIOS VSCSI connection – pros and cons
 Requires VIOS and the resources for VIOS

 Additional complexity in VIOS
 Multipath from VIOS to V7000 is managed by VIOS Multipath
driver
 Very high max number of vscsi adapters, on the other hand
only 16 LUns per vscsi adapter
 With big workloads can be a little faster than NPIV
 Negligible performance overhead comparing to native
connection

VIOS VSCSI connection – facts
 Maximum 16 LUNs per virtual SCSI adapter

 Client virtual SCSI adapters in IBM i
 Corresponding Server virtual SCSI adapters in VIOS
 V7000 LUN reports in VIOS as disk device hdisk(x)
 In VIOS: Mapping hdisks to client virtual SCSI adapters
 Example mkvdev -vdev hdisk4 -vadapter vhost2 –dev Prod_sysbas_2

Defining the LUNs for IBM i

 A V7000 storage pool is a collection of managed disks (mdisks)
–When implementing V7000 internal storage a managed disk is a RAID
array of internal disk drives
–The mdisks in a pool should have similar performance characteristics
(same RAID level, same drive type, about the same number of drives
per array, etc)
 Volumes are created from a storage pool, they are presented to the IBM i
system as LUNs.
 Volumes for IBM i are created the same way as for other open systems
 Real-time compression is supported by IBM i
 Both Generic and Thin-provisioned volumes are supported by IBM i

LUN sizes for IBM i

 Minimal supported LUN size is 160 MB ( in IBM i)
 IBM i supports LUN size up to 2 TB ( in IBM i)
 Minimal size for LoadSource in IBM i V7.1 is 17 GB
 To support future product enhancements it is recommended that load source
devices be created at least 80GB
 For any IBM i ASP define all the LUNs to be the same size
 40 GB is the recommended minimum LUN size.
 There should be sufficient LUNs in the IBM i configuration
– The more LUNs are defined, the more Storage management server tasks are
used, consequently better IO performance
 A minimum of 6 LUNs for each ASP or LPAR is recommended.
 Maximal recommneded size is up to 300 GB
 A smaller number of larger LUNs will reduce the number of IO ports required on
both the IBM i and the Storwize V7000
LUN versus disk arm
 The V7000 LUN connected to IBM i reports

in IBM i as a disk unit
 IBM i storage management employs the
management and performance functions
as if the LUN was a disk arm.
 In fact the LUN is typically spread across
multiple physical disk arms in the V7000
disk pool
 All disk arms the disk pools are shared
among all the LUNs that are defined in that
disk pool *
* providing that a volume is defined in striped

mode

Boot from SAN
 LoadSource resides on a V7000 LUN

which is connected the same way as
the other LUNs
 There aren't any special requirements
for LoadSource connection.
 The LUN for LoadSource is selected IBM i
at IBM i installation
VIOS
 Whne migrating from other storage
systems or Internal disk drives, the
LoadSource is copied to a V7000 LUN
Load
Source
V7000
Solid State Drives with IBM i
 Solid-state storage technology can have the following benefits

 Significantly improved performance for hard-to-tune, I/O bound
applications. No code changes required.
 Reduced floor space. Can be filled near 100% without performance
degradation
 Greater IOPS
 Faster access times
 Reduced energy use
 Exploitation of SSDs with the Storwize V7000 is through Easy Tier.
 Even if you don’t plan to install SSDs you can still use Easy Tier to
evaluate your workload for the benefit of SSD

Solid State Drives with IBM i - cont

Typical IBM i Skew level and
Storage Tier Advisor Tool (STAT)
 Options to implement SSD in
V7000 for IBM i:
– Hybrid disk pool and Easy
Tier
– An IBM i ASP with
application data resides
on SSD
 The IBM i skew level is
typically flat due to IBM i
object orientated architecture
 Therefore IBM i might need
some more SSD in the hybrid
pool than other workloads
 The IBM i methods for data
relocation do not apply with
V7000

Mapping the LUNs to adapters in IBM i or VIOS

 In V7000 we create a Host that has
WWPNs of the ports to which the LUN
will be mapped
 In native or NPIV connection the Host
contains WWPNs of ports in different
physical or virtual adapters
 In VIOS VSCSI connection the Host
contains WWPNs of physical ports in
VIOS

IBM i – disk unit type model and resource name

Native and NPIV connection
Last 6 characters from volume UID in V7000
VIOS VSCSI connection
Some steps are needed to identify the LUN in VSCSI connection© 2014 IBM Corporation
Zoning SAN switches for native or VIOS_NPIV

connection
 Zone
– One WWPN of one IBM i port
– Two ports of V7000, each port
from one node canister
 Resiliency for the IO to / from the
LUN mapped to the WWPN
 The path through preferred node is
active
 The path through non preferred node
is passive

Zoning SAN switches for VIOS VSCSI connection
 Zone
– One physical port in VIOS
– As many V7000 ports as possible
to allow load balancing, keeping in
mind that there are maximum 8
paths available from VIOS to
V7000.
– V7000 ports should be evenly
spread between node canisters

Multipath
 Provides greater resiliency for SAN attached storage

 IBM i supports up to 8 paths to each LUN
 Provides performance improvement
 Multipath is achieved as soon as a LUN connects with more than one
path to IBM i
 Multipath is built in IBM i, there is no need to install a special driver
 With native connection, the ports for Multipath must be in different
physical adapters in IBM i
 With VIOS_NPIV the virtual Fibre channel adapters for Multipath must be
assigned to different VIOS.
 With VIOS vscsi connection the virtual SCSI adapters for Multipath must
be assigned to different VIOS.

Multipath and preferred node
 Every LUN in Storwize V7000 uses one V7000 node as preferred node
–The preferred node for a LUN is automatically assigend when the LUN
is created, but can be changed
–The IO traffic to / from the particular LUN normally goes through the
preferred node
–If that node fails the IO is transferred to the remaining node
 With IBM i Multipath, all the paths to a LUN through the preferred node
are active, load balancing is used on active paths
 The paths through the non-preferred node are passive.

Multipath with native and VIOS_NPIV connection

Multipath with VIOS VSCSI connection

Native connection - basic implementation steps
 Create an IBM i partition (LPAR)

 Connect the FC adapters in IBM i LPAR via SAN switches, or directly (if
4Gb adapters are used) to V7000
 Zone the SAN switches (if applicable)
 In V7000 create the Hosts for IBM i
–each host having one or more WWPNs of ports in adapters in IBM i
LPAR
 In V7000 define the LUNs for IBM i and map them to the Hosts for IBM i
 Install IBM i

VIOS_NPIV connection - basic implementation steps
 Create VIOS LPAR and install VIOS

 Create IBM i LPAR
 In IBM i LPAR create Cient virtual FC adapters
 In VIOS LPAR create Server virtual FC adapters
 In VIOS map the server virtual FC adapters to ports in physical adapters
 Zone the switches
 In V7000 create the Hosts for IBM i
–each host having one or more WWPNs of Virtual FC adapters in IBM i
LPAR
 In V7000 define the LUNs for IBM i and map them to the Hosts for IBM i
 Install IBM i

VIOS VSCSI connection - basic implementation steps
 Create VIOS LPAR and install VIOS

 Create IBM i LPAR
 In IBM i LPAR create Cient virtual FC adapters
 In VIOS LPAR create Server virtual FC adapters
 Zone the switches for physical adapters in VIOS and V7000 ports
 In V7000 create the Hosts for phyiscal ports in VIOS
 In V7000 define the LUNs for IBM i and map them to the Hosts of VIOS
 In VIOS map the hidsks to Client virtual SCSI adapters of IBM i LPAR
 Install IBM i

Example: Setup LPARs for IBM i and VIOS in POWER

server
VIOS profile
IBM i profile

Example: Install VIOS
Example
 Activate partition
 Start System Management Services
(SMS) window
 Choose CD_ROM as Install /Boot
device
 After VIOs reboots, insert userid and
password
 Accept licenses
 Start disk mirroring of Rootvg volume
group
 Setup network connectivity
 Update VIOS with the latest ficpack

Example: Mapping in VIOS for NPIV conneciton, zoning the switches

for NPIV connection
Mapping in VIOS for NPIV
Zoning the switches

Example: Create hosts in V7000
Note:
The IBM i wwpns will
Show in switches and
V7000 after IBM i IPL is
started
Before IBM i started you need
to manually insert WWPNs

Exaple: create LUNs for IBM i and map them
Create LUNs for IBM i

Map LUNs

Example: Install IBM i for ISO images in VIOS repository

 Load the first installation ISO image in VIOS
repository
 Start partition with IPL source D
 Open console window
 Install licensed internal code
 In Dedicated Service Tools (DST) add disk units
(V7000 LUNs)
 Whe needed unload the ISO image from virtual
optical device and load the next one
 Install licnesed products and accept licenses
 Install the latest group PTFs
 Setup IP connection

Migrations
 Migration between different types of connection

 The same LUNs can be disconnection from one type of connection and re-
connected in another type of connection
 From VIOS VSCSI to VIOS NPIV
 From VIOS NPIV to VIOS VSCSI
 From VIOS NPIV to native
 From native to VIOS NPIV
 From VIOS VSCSI to native
 From native to VIOS VSCSI
 Migration from IBM i internal disks or another Storage system to V7000

 Save / restore
 Connect V7000 LUNs to current IBM i partition, use ASP balancing to migrate data, copy LoadSource

IBM i solutions with V7000 Copy services
44 9/18/2018 © 2014 IBM Corporation

Disk pools Auxiliary Storage Pools

in IBM i (Disk Pools)
System ASP User ASPs

(Disk pool 1) (Disk Pools 2-255)
Traditional User ASPs

(Basic Pools 2-32)
Sysbas Independent ASPs - IASPs

( Independent Pools 33-255)

IBM i Cluster
2-node cluster
Node 1 Node 2
CRG CRG
Cluster resources
Recovery domain
Device domain

IBM i Journaling
Your
Program
New
Row
Put
File A Journal
The DB is the
last to know
File A: PT
New
Row
2
1
New Journal
Row Receiver's PT: PT
New Row New Row
content
File A
Jrn Rcvr

Quiesce data in an IASP or Sysbas
Memory
IASP,sysbas
 To quiesce data in an IASP to disk use command CHGASPACT with the following
parameters:
– ASP Device (ASPDEV)
specify the name of the IASP being quiesced, or *SYSBAS.
– Option (OPTION)
specify option *SUSPEND to quiesce the data in the IASP.
– Suspend timeout (SSPTIMO)
specify duration of the timeout during which the system is quescing the data to
disk.
– Suspend timeout action (SSPTIMOACN)
specify the desired action at the end of timeout if the system was not able to
quesce all data during the timeout.
 Requires IBM i V6R1 or later

V7000 FlashCopy –business solutions
 Rapidly creates Point-in-time copy of production data

 For off-line save of production data
 To create backups on disk through periodic execution of
FlashCopy
 For application developing and testing
 For auditing and data mining

FlashCopy Overview
 FC Mappings: FlashCopy occurs between a source volume and a target volume
that must be of the same size
 FlashCopy options: Multiple target, Cascaded, Incremental, Reverse FlashCopy
 Data copied between source and target are copied in units known as grains, each
grain is by default 256K
 Background copy
– The background copy rate is defined as a value of 0 - 100.
– No-copy option is achieved by a value of 0 of background copy. This disables
the background copying and provides pointer-based images for limited lifetime
uses.
– Afer the background copying is finished the FlashCopy relation disappears
– Background copy rates can be different for each mapping
 Consistency groups
– Consistency groups preserve point-in-time data consistency across multiple
volumes
– They ensure that dependent writes are executed in the application’s intended
sequence.
– The volumes within the consistency group are managed at the same time


FlashCopy options
 Multiple target  Reversed
 Incremental

Remote Copy Services  Single point for copy services

IBM i, Unix  Asynchronous remote copy / Global mirror
 Synchronous remote copy / Metro mirror
 Disaster recovery distance up to 8000 km
Business continuitly distance for IBM i 50 – 100 km
Wintel
Max 80ms roundtrip latency
SWV7K 5 ms delay for 1000 m
IP WAN
DS5K Others SWV7K

DS8K
 Cisco FCIP with IVR

 Brocade Routers
 DWDM/CWDM Others
DS3/4/5K
 NO Native IP Replication over Ethernet today XIV

Metro Mirror
 Creates a synchronous copy of data from a master volume to an auxiliary volume.

Global Mirror
Production host
(1) Write Host I/O (2) Ack.
Global Mirror relationship

Primary Secondary
volume volume
(3) Mirror write
 Dependent writes to primary sent with sequence number to secondary site to ensure they
are applied in the same order
 80ms roundtrip latency maximum
 Bandwidth sized for peak change rates
 RPO seconds and non-configurable

V7000 V6.3 and later - Global Mirror with Change Volumes

Production host
Host I/O
Global Mirror relationship

Primary Secondary
volume volume
Change Change
volume volume
FlashCopy FlashCopy
Mapping mapping
 Initially copy all data from primary volume to secondary volume at point-in-time of when GM relationship started
 Change volumes hold point-in-time copy of pieces of data called grains, 256K, that change during cycling mode
(default 300 seconds)
 80ms roundtrip latency maximum
 Bandwidth sized based on RPO desired
 RPO minutes to hours

Scenarios with FlashCopy

IASP
Full System
Can be Managed by FlashCopy Toolkit Managed by PowerHA SystemMirror for i
Production
Production
partition IASP
partition
BfS IASP
•Cluster
Backup
Backup partition FlashCopy
BfS
partition
FlashCopy
BfS = Boot from SAN

FlashCopy - Benefits to the Customer
 The production application downtime is only is as long as it takes to vary

off the IASP, perform a FlashCopy of the volumes in the IASP, and vary
on IASP. Or, Power-down system, perform a FlashCopy and IPL
 The performance impact on the production application during the save to

tape operation is minimal since it is only influenced by the FlashCopy
activity which is mostly confined within the Storage system.
 On IBM i V6R1 and later we can quiesce data to disk without power-
down production system i
 This solution can be implemented together with Backup, Recovery and

Media Services for (BRMS)

IBM i Scenarios with Remote Copy Remote site

Local site
Full
Disaster
Production recovery
System BfS
partition BfS partition
MM/GM
Managed by PowerHA SystemMirror for i
Cluster
Production Disaster
partition recovery
IASP
IASP IASP partition
MM/GM

Metro Mirror – Benefits to the Customer

 Provides synchronous copy of the production data on DR site
 This solution has only impact on write operations performances. It doesn’t use any
of the IBM i CPU resources.
 Once this solution is established it requires very little maintenance and
administration. Therefore some customers may prefer it to other high availability
solutions available in IBM i.
When using IASP:
 Basically, recovery takes as long as is needed to vary on an IASP, Therefore
recovery time is significantly shorter than with solutions which use Boot from SAN,
or external LoadSource, where IPL is needed for recovery.
 With this solution we can run a non production workload, like test or development
tasks in the remote partition. This is again different from the implementation using
Boot from SAN where the recovery partition has to be in stand-by, typically without
any workload.
 The PowerHA for i which is used for this solution provides full automation of steps
performed at planned or unplanned outages. All the needed steps for failover and
failback are initiated by one command in a partition of IBM i.

Global Mirror - Benefits to the Customer
 Very small impact to production performances

 Suitable solution for long distances
 Customer has the possibility to balance between RPO and bandwidth (using GM
with Change volumes)
 Once this solution is established it requires very little maintenance and
administration
 The PowerHA for i which is used for this solution provides full automation of steps
performed at planned or unplanned outages. All the needed steps for failover and
failback are initiated by one command in a partition of IBM i.

Copy service over IP links for IBM i solutions
 Metro Mirror over IP for IBM i full system – tested in Mainz

 Metro Mirror over IP for IASP with PowerHA for i – tested in Mainz
 Global Mirror with change volumes over IP for IBM i full system – tested in
Mainz
 Global Mirror with change volumes over IP for IASP with PowerHA for i –
possible, not yet tested in Mainz
Note: the test in Mainz were done for functionality, performance were not
tracked

PowerHA SystemMirror for i (PowerHA for i)

 PowerHA for i a licensed program in IBM i.
 Works with clusters, IASPs and the function Switchable Hardware resources
 Offers a complete end-to-end integrated clustering solution for high availability and
disaster recovery.
 Can be deployed with Copy Services of external storage or Geographical mirroring
- IBM i replication over IP connection.
 PowerHA for i solutions are automated. Data resiliency is completely managed
within the IBM i storage management architecture, there is no operator
involvement or minimal involvement.
 PowerHA for i Supports naitvely connected, NPIV connected and VIOS VSCSI
connected V7000
 PowerHA for i Supports natively connected, NPIV connected and VIOS VSCSI
connected DS8000
 Advanced Copy Services for PowerHA (ACS) is a Lab services offering that
enhances PowerHA for i. ACS provides high level of automation of the solutions
with DS8000 Copy Services, and comprehensive tools for checking and
troubleshooting. ACS provides high level automation of the FlashCopy solution
with V7000.

IBM i 7.1 PowerHA SystemMirror for i

An IBM delivered, end-to-end solution for HA, DR and on-line backups
LUN level switching requires PowerHA group ptf level 4 or higher

How PowerHA for i works

 Setup
– IASP, cluster, device domain, CRG
– PowerHA Copy descriptions - describe the external storage being
used
 Start ASP session
– Starts PowerHA session, which allows PowerHA to manage and
monitor Geographic mirroring, Remote Mirroring or FlashCopy
activity.
 PowerHA Metro Mirror session
– Once PowerHA session for Metro Mirror is started PowerHa is ready
to switch over the environemnt to DR site. Switch over is performed
on user request, or automatically on detected failures in production
system.
 PowerHA FlashCopy session
– Starting FlashCopy session starts the FlashCopy relation in V7000
– Ending FlashCopy session ends the FlashCopy relation in V7000

Setup for Metro Mirror /GlobalCluster

Mirror on V7000
Secondary site
Primary site
Device domain
Create cluster
Create device domain crg 1 2 crg

crg Recovery domain crg
Create IASP
MM ASP Session
Copy desc Copy desc
Generate SSH keys
and start Metro Mirror
Create CRG and

recovery domain
Create PowerHA copy descr IASP
Start PowerHA Metro Mirror session
Start CRG © 2014 IBM Corporation

Scenario for Unplanned outages

Secondary site
Primary site Cluster, Device domain, recovery domain
Automatically 12 21
Executed Actions: MM ASP Session
crg
crg
Send message to
msgqueue on DR site
Message
Vary-off production IASP

Metro Mirror
Switch Metro Mirror
Change node priority

in recovery domain
Vary-on IASP on DR site

FlashCopy for daily backups
Cluster
Quiesce data in IASP Device domain
Produciton
Production
Start FlashCopy session
Copy desc
Resume transactions in IASP

Copy desc
Vary-on FlashCopy IASP to

Backup LPAR Backup
Save to tape from Backup LPAR

End FlashCopy session
IASP

Further references
 Hints and Tips: V7000 in an IBM i Environment

– http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102305
 Introducing the Storwise STORWIZE V7000
– http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4391
 IBM i Virtualization and Open Storage
– http://www-03.ibm.com/systems/resources/systems_i_Virtualization_Open_Storage.pdf
 Example of IBM i Partition Migration from Virtual SCSI to NPIV attached IBM System
Storage SAN Volume Controller / IBM Storwize Family Systems
– http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD106089
 Redbook SAN Volume Controller V4.3.0 Advanced Copy Services, SG24-7574-01

 Redbook PowerHA SystemMirror for IBM i Cookbook, SG24-7994-00

Storwize V7000 With IBM I - Implementation

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Storwize V7000 With IBM I - Implementation

Diunggah oleh

Hak Cipta:

Format Tersedia

Storwize V7000 and IBM i pre-sales enablement

IBM Storwize V7000 with IBM i

© 2014 IBM Corporation

Implementing V7000 with IBM i

3 9/18/2018 © 2014 IBM Corporation

IBM i and Storage systems IA

DS8000 V7000, V5000, V3700

© 2014 IBM Corporation

 SVC and Storwize V7000 offer five 9s (99.999%) availability

 Storwize family is ideal for any organization’s disaster

 Over 55.000 systems purchased

Numbers as of March 31, 2014

© 2014 IBM Corporation

IBM Storwize V7000 at a Glance

Modular Hardware Building Blocks

Enterprise-level Software Capabilities

IBM i Single-level Storage

IBM i Oobject orientated architecture

Translation from 520 byte blocks to 512 byte

 IBM i disks have a block size of 520 bytes.

© 2014 IBM Corporation

Native connection of V7000 to IBM i

Minimal software and microcode levels FC adapters

Direct attach V7000

© 2014 IBM Corporation

Native connection - pros and cons

 Doesn’t require VIOS

© 2014 IBM Corporation

Native connection - facts

 Maximum 64 LUNs per port

© 2014 IBM Corporation

VIOS_NPIV connection of V7000 to IBM i

Requirements for VIOS_NPIV

© 2014 IBM Corporation

VIOS_NPIV connection - pros and cons

 Requires VIOS and the resources for VIOS

© 2014 IBM Corporation

VIOS_NPIV connection - facts

 Maximum 64 LUNs per virtual FC adapter

© 2014 IBM Corporation

VIOS VSCSI connection of V7000 to IBM i

Requirements for VIOS VSCSI

© 2014 IBM Corporation

VIOS VSCSI connection – pros and cons

 Requires VIOS and the resources for VIOS

© 2014 IBM Corporation

VIOS VSCSI connection – facts

 Maximum 16 LUNs per virtual SCSI adapter

© 2014 IBM Corporation

Defining the LUNs for IBM i

© 2014 IBM Corporation

LUN sizes for IBM i

LUN versus disk arm

 The V7000 LUN connected to IBM i reports

* providing that a volume is defined in striped

© 2014 IBM Corporation

Boot from SAN

 LoadSource resides on a V7000 LUN

Solid State Drives with IBM i

 Solid-state storage technology can have the following benefits

© 2014 IBM Corporation

Solid State Drives with IBM i - cont

© 2014 IBM Corporation