powerha systemmirror, vm recovery manager,
TRANSCRIPT
© Copyright IBM Corporation 2021
PowerHA, VM Recovery Manager, Db2 Mirror
24X365
Steven Finnes Power Systems
HA/DR product manager
&
PowerHA SystemMirror,
VM Recovery Manager,
Db2Mirror
© Copyright IBM Corporation 2021
Contents
• Power Systems HA/DR family and classification system
• Section 1: active/inactive (VM Recovery Manager, FSR, ihostingi “fsr”
• Section 2: active/passive (PowerHA SystemMirror)
• Section 3: active/active (Db2 Mirror)
• Backup section with additional information
© Copyright IBM Corporation 2021
Power Systems HA/DR solution family
3
PowerHA for AIX
Cognitive Systems HA/DR
active/passive HA/DR active/inactive VM restart
PowerHA for IBM i VM Recovery Manager HA VM Recovery Manage DR
PowerHA System Mirror
– Active/passive at the production data level
however, active/active at the OS level
– Covers planned and unplanned outages for both
software and hardware with automation
– Provides solutions for both HA & DR with a
single point of control
– Operating system based technology
– RTO application restart
– RPO sync or async mode
– N+1 licensing,
VM Recovery Manager (VMR)
– Primarily for planned and unplanned
hardware outages
– Monitors and manages
large numbers of VMs (LPARS)
– Relatively easy to implement and manage
– Operating system independent
(supports AIX, i and Linux)
– RTO via reboot (IPL)
– RPO sync or async mode
– N+0 licensing
Db2 pureScale
active/active HA
Db2 Mirror for IBM i
Db2 pureScale & Db2 Mirror & Oracle RAC
– Active/active at the application level
– Covers HA servers in near proximity. DR will be
addressed separately as an add-on.
– Covers planned and unplanned outages for both
software and hardware with automation
– Db2 Mirror active/active via synchronous
replication at the OS level
– RTO & RPO = zero
– N+N licensing (DLPAR for active/passive mode)
© Copyright IBM Corporation 2021
VM Recovery Manager - Private Cloud
• Automates LPM and VM restart in the datacenter
• Covers hardware outages, planned and unplanned
• SAN storage replication for DR operations
• Lowest cost of acquisition, lowest cost of operations
• Compliments PowerHA, supports AIX, i and Linux
PowerHA for AIX, PowerHA for IBM i
• Provides highly automated business continuity
• Covers all outage types: planned, unplanned, hardware, software
• Low cost of acquisition, low cost of operations
• SAN storage replication for private cloud deployments
• GLVM or geomirroring for public cloud deployments
4
PowerHA and VM Recovery Manager
VIOS VIOS
LPAR/VM
OS/Apps
VIOS VIOS
LPAR/VM
OS/Apps
VIOS VIOS
LPAR/VM
OS/Apps
LPAR/VM
OS
Apps
LPAR/VM
OS
Apps
LPAR/VM
OS
Apps
Storage replication
Storage replication
© Copyright IBM Corporation 2021
PowerHA i, VM Recovery Manager VMRM & Full System Replication (FSR)
PowerHA VMRM PowerHA tools: FSR
Offering Standard IBM offering Standard IBM offering Lab Service Tool
Support Standard IBM support Standard IBM support Standard + Lab Services
Orchestration PowerHA KSYS Control LPAR/PowerHA
Primary use case HA and DR mission critical
application and hardware outage
management
Hardware outage management
via reboot, data center via LPM
and VM restart
Hardware outage management via
reboot, data center via LPM and VM
restart
Outage management (planned and unplanned) Software & Hardware Hardware Hardware
Concurrent production application maintenance yes no no
Cluster Object sync (user profiles etc.) PowerHA Admin Domain
(automated in 7.4)
not applicable not applicable
VIOS not required required not required
IASP (IBM i) yes no no
Redundancy 2+hardware & 2+OS 2 hardware 1 OS 2 hardware 1 OS
RTO Application restart IPL IPL
RPO 0 via sync mode 0 via sync mode 0 via sync mode
Flash Copy Automation (IBM i) yes (Flash Systems) DR rehearsal Yes (full system flash)
Shared Storage config Switchable LUN, LPM LPM, VM restart (IPL) Lun switch/IPL
Geographic dispersion Metro Mirror, Global Mirror
Geomirroring, GLVM
IBM + third party storage Global Mirror or Metro Mirror
DS8K HyperSwap + Global Mirror link Yes (PowerHA i) no no
Cloud Geomirroring, GLVM no no
Bandwidth requirements the IASP data IBM i
the VG data AIX
Full VM stack including temp
objects
Full system stack including temp
object
© Copyright IBM Corporation 2021
Section 1: Active/Inactive
• VM Recovery Manager
• FSR, full system replication (lab services tool)
• ihosting i geomirroring
VM Recovery Manager value proposition
• CAPX
⎻ VM Recovery Manager is licensed per managed processor core, one-time charge, 1st year SWMA included
o SWMA renewal is 20% of list price,
o N+0 licensing; only the production cores incorporated into the VMR cluster are counted
o Example, 40 VMs, 10 production processor cores> 10 total VM Recovery Manager licenses running on any AIX partition
> Assume small tier, list price for VMR DR 10($1060) = $10,600
> Annual subscription = $2,120
• OPEX
⎻ VM Recovery Manager HA automatically manages LPM and restart operations
⎻ VM Recovery Manager DR supports both HA and DR operations
⎻ UI enables you to monitor (and manage) from a single pane of glass
⎻ Add VMR DR to your PowerHA AIX standard edition cluster for your DR solution
• Operational value (NPS score not available yet)
⎻ Policy driven automated HA operations
⎻ Non disruptive DR rehearsal
⎻ Eliminates human dependencies for conducting DR validation testing
7 © Copyright IBM Corporation 2020
© Copyright IBM Corporation 2021
VM Recovery Manager DR disaster recovery operations made easy & economical
Automation
• Administrator defined end to end automation
• Supports both HA and DR
• Eliminates human intervention and error
• Reliable consistent recovery time
• Non disruptive disaster recovery testing
• Adapts to configuration changes (eg: VMs or disks added)
Single point of control
• Centralized status reporting
• Intuitive UI for monitoring and managing
Validation
• Auto discovery of changes to environment
• Daily verification testing (light weight hourly)
• Email & SMS alerts sent to admin
• Scripting support
Capacity management
• Enterprise pool & ECBU for scale-up systems
• Flex capacity: increase or reduce memory/CPU on target side
Economics
• N+0 licensing
• PowerVM included as of Power9
redundant ksys9
VM Recovey Manager DR installing VM Recovery Manager
• VMR DR licenses are installed in an AIX partition on a server in the
secondary site and enables the KSYS function.
• Supported OS’s: AIX, IBM i, Linux on Power
• Supported storage:
o SVC: Firmware 7.6, or later
o XIV: Firmware 11.6.2
o EMC: Solution Enabler (SE) version 8.4.0.15
o DS8K: Firmware 8.4
o Hitachi: VSP g1000/g1500
VM Recovery Manager for DR combines the HA & DR configuration
VM Recovery Manager for DR enables the capability to manage both HA and DR from a single KSYS
VM Recovery Manager for DR 1.5 enables VMR HA at both primary and secondary site
10
Failover rehearsal: non disruptive disaster recovery testing
Site 1 (active) Site 2 (backup)
• A point in time copy (i.e., Flash Copy) is created to start VMs on the back up system for DR testing or backup operations
• Enables IT operations to validate disaster recovery compliance without disrupting production
• Network isolation needs to be established by the administrator (admin can design and use the test VLANs for test VMs)
Host 11
Disk Group 1 Mirror
Host 21
S1 S2 S2C
…
LP
AR
1_11
LP
AR
1_12
LP
AR
1_1m
VIO
S 1
_11
VIO
S 1
_12
VIO
S 2
_11
VIO
S 2
_12
…
LP
AR
1_11
LP
AR
1_12
LP
AR
1_1m
Host 1
VMR HA restart policy options
APP1 APP2 APP3 APP4
OS OS OS OS
Host 2
APP1 APP2
OS OS
Host 3
APP3 APP4
OS OS
Host 1
APP1 APP2
OS OS
Host 2
APP3 APP4
OS OS
Host 3
APP1 APP2
OS OS
Host 1
APP APP APP APP
OS OS OS OS
Host 2
APP APP APP APP
OS OS OS OS
Host 3
APP APP APP APP
OS OS OS OS
Colocation PolicyAPP1, APP2 restarted to Host 2
APP3, APP4 restarted to Host 3
Anti - colocation PolicyAPP1 & 2 restarted to Host 2APPs 1 & 2 not collocate ableWith APPs 3 & 4
Blacklist PolicyHost 3 excluded as relocation target
VMR HA planned outage (LPM) management
13 © Copyright IBM Corporation 2020
Host 1
APP1 APP2 APP3 APP4
OS OS OS OS
Host 2
APP1 APP2
OS OS
Host 3
APP3 APP4
OS OS
Host 1
APP1 APP2 APP3 APP4
OS OS OS OS
Host 2
APP1 APP2
OS OS
Host 3
APP3 APP4
OS OS
• Vacate Host: VMs in Host 1 are migrated Hosts 2 and 3 in the Host group
• Best fit capacity analysis-based moves
• Restore Host: VMs are moved back to Home Host.
• Home Host is where the VMs were moved from. An admin can modify as needed
Production
Workload
Production
Workload
Full System Replication automation(PowerHA tools for IBM i) – this is not a PowerHA cluster !
Controlling LPAR
(DR Site)Controlling LPAR
(Production Site)
Production LPAR
(Production Site)
Production LPAR
COPY (DR Site)Remote Copy
DS8K Metro Mirror or Global Mirror
OR SVC-Based Metro Mirror or
Global Mirror w/Change Volumes
Issue the switch operation
Complete startup processes
Automated with FSRC
SWCSE Command
End applications/jobs on production site
Monitor/wait for all jobs to end
Issue the shut-down command
Monitor/wait for shut-down to complete
Log in to storage as Admin
Verify/wait for disk synchronization
Log in to HMC at DR site as superadmin
IPL the DR site partition in manual mode
Modify “autostart” objects (lines, interfaces,
devices, applications) to not start
Correct comm resources, storage resources,
IP interfaces, TCP routes, etc.
Apply license keys
CONTROLLING PARTITIONS:
Either controlling partition may
control the switchover, failover or
detach, dependent on which site is
active
MANUAL STEPS AND LOG-INS
NO LONGER REQUIRED!
Lab Services offering this is not a PowerHA Cluster, PowerHA is used for the controlling partition
© Copyright IBM Corporation 202014
PowerHA IBM i hosting i VM Restart (full system replication)-not a PowerHA cluster !
15 © Copyright IBM Corporation 2020
⎻ This is the ultimate, simple, low-cost solution for disaster recovery for many IBM i customers⎻ Storage agnostic, works fine with internal disk⎻ PowerHA for i is used in conjunction with IBM i hosting i to create a native VM replication/restart DR solution⎻ The full production partition including the operating system is hosted in a network storage space within an IASP⎻ The IASP is replicated using PowerHA geomirror to a backup host partition.⎻ In the event of a failure, the target IASP and NWSD are varied on, and the production partition IPL’d on the target system.⎻ Guest and host partitions must be shut down before remote host and client can be restarted⎻ Note that everything is being replicated so network bandwidth and quality is critical.⎻ Checkout the wiki link for further reference:
Admin domain*
geomirrorclient
partitionIBM i hosted
partition
NWSSTG
i host partition
IASP
client
partition IBM i hosted
partition
NWSSTG
i host partition
IASPApplications
i hosting i DR solution
customer story - Kansas Turnpike Authority
Secton 2: Active/Passive
• PowerHA SystemMirror
© Copyright IBM Corporation 2021
PowerHA i –UI Dashboard included with no additional cost
PowerHA overview live demos
PowerHA i UI demo
© Copyright IBM Corporation 2021
PowerHA i value proposition
CAPX
• PowerHA for on prem deployments are licensed per processor core, one-time charge, 1st year SWMA included
⎻ No processing overhead required for replication services
⎻ SWMA renewal is 20% of list price
⎻ N+1 licensing; the CBU for IBM i requires only one IBM i and one PowerHA
⎻ Example, 5 production processor cores, 1 CBU core
➢ 6 total IBM i and PowerHA (N+1)
➢ Assume small tier, list price for PowerHA enterprise edition: 6($3740) = $22,440
➢ Annual subscription = $4,488
OPEX
⎻ PowerHA is highly automated, inherently self regulating
⎻ New UI enables at-a-glance health monitoring
⎻ Replaces logical replication tools which rely heavily on IT specialists
Operational value (current NPS score is 85)
⎻ PowerHA customers conduct regular role-swap operations, single command
⎻ Integrates and manages IBM storage as an integral part of the total solution
⎻ Manages FlashCopy and BRMS eliminating the backup window
• Penske Truck Leasing Kansas Turnpike Auhority HATCO Svenska Handelsbanken AD Transport
18 © Copyright IBM Corporation 2020
PowerHA solutions for HA/DR: with storage replication
19
PowerHA Standard Edition PowerHA Enterprise Edition
AIX/IBM i
apps
AIX/IBM i
apps
AIX/IBMi
apps
AIX/IBM i
apps
AIX/IBM i
apps
PowerHA SE + VM Recovery Manager DR
AIX/IBM i
apps
AIX/IBM i
apps
AIX/IBM i
apps
PowerHA EE + HyperSwap
AIX/IBM i
apps
AIX/IBM i
apps
HyperSwap DS8K demo
© Copyright IBM Corporation 2021
Two system two-site PowerHA i Enterprise Edition cluster
20
• Four nodes in this illustration, nodes 1 & 2 are production nodes, node 3 is a flash copy node
• All nodes have active IBM i enabling concurrent software updates without disrupting production
• Switched LUN configuration in the data center, applications and data go into the IASP, and local journals
• System ASP(SYSBAS) contain the monitored resource entries (MREs)
• The Administrative Domain keeps MREs in sync between the nodes 1 and 2 (note: no logical replication being used)
• Node 3 (LPAR2) in this config is used for Flash Copy & BRMS operations to eliminate your backup window
⎻ We can flash the IASP, or the IASP + Admin Domain objects, or full system flash (IASP + ASP 4)
• PowerHA for i 7.4 TR4 & 7.3 TR 10 incorporates and automates FlashCopy operations
Production
IASPProduction
IASP
Flash Copy
IASP
System ASP 1
System ASP 2
IBM i 1
Application
IBM i 2
Application
IBM i 3
BRMS
Admin Domain
FS9200 FS9200
Cloud
MEDIAMetro Mirror or Global Mirror
LPAR1 LPAR2
Production data center Disaster recovery site Included inPowerHA for i 7.4 TR4 & 7.3 TR 10
© Copyright IBM Corporation 2021
PowerHA Admin Domain – what the heck is this ?
• PowerHA Admin Domain is all that is required to synchronize , add,
delete MRE’s (monitored resource entries e.g., user profiles,
authorization lists etc).
• PowerHA i 7.4 has automated Admin Domain function, for example,
you can add resources with a single command (see the included
links and video)
• The administration domain function is executed within the OS and
slic programmatically. It does not involve the replication of objects.
• There is no need to replicate SYSBAS with logical replication tools.
• You don’t need to use full system replication to avoid SYSBAS
management. Get to 7.4 and use the automated PowerHA Admin
Domain function.
MREs MREs
SYSBAS SYSBAS
Admin Domain
objects left in sysbas
21
https://www.ibm.com/docs/en/i/7.4?topic=policies-powerha-cluster-administrative-
domain-resources
Easily manage adding, deleting, and restoring resources to nodes in the cluster administrative domain
add many resources with a single command:
© Copyright IBM Corporation 2021
PowerHA with internal disk, geomirroring and FS9200
• Customer can’t initially budget for two V9200s so phase 1 they will use geomirroring and take advantage of FlashCopy operations
• PowerHA automates and incorporates it with V7.4 TR3 and V7.3 TR10
• Managing SVC IASP FlashCopy combined with Geographic Mirroring is handled with PowerHA natively.
• PowerHA manages as part of the STRSVCSSN command for FlashCopy to ensure that all copies remain usable and tracked correctly.
• The Spectrum Virtualize storage can be deployed on production side or target side
22
geomirroring
IASP
Production site
IASP
Flash Copy
IASP
System ASP 2
IBM i 2
Application
IBM i 3
BRMS
FS9200
Cloud
MEDIA
LPAR1 LPAR2
Recovery site
IASP
System ASP 2
IBM i 1
Application
Admin Domain
© Copyright IBM Corporation 2021
Three system two-site PowerHA i Enterprise Edition cluster
23
• Four nodes in this illustration, nodes 1,2 & 3 are production nodes, node 4 is a flash copy node
• All nodes have active IBM i enabling concurrent software updates without disrupting production
• Switched LUN configuration in the data center, applications and data go into the IASP, and local journals
• System ASP(SYSBAS) contain the monitored resource entries (MREs)
• The Administrative Domain keeps MREs in sync between the nodes 1,2 and 3 (note: no logical replication being used)
• Node 4 (LPAR2) in this config is used for Flash Copy & BRMS operations to eliminate your backup window
⎻ We can flash the IASP, or the IASP + Admin Domain objects, or full system flash (IASP + ASP 4)
⎻ In this illustration, the two secondary systems are CBUs
Production
IASPProduction
IASP
Flash Copy
IASP
System ASP 1
System ASP 2
System ASP 3
IBM i 1
Application
IBM i 2
Application
IBM i 3
Application
IBM i 4
BRMS
Admin Domain
FS9200 FS9200
Cloud
MEDIAMetro Mirror or Global Mirror
LPAR1 LPAR2
Production data center Disaster recovery site
© Copyright IBM Corporation 2021
DS8000 three site PowerHA IBM i Enterprise Edition HyperSwap cluster
• Three systems, three sites, three real-time copies of the production IASP production data in a signal PowerHA EE cluster
• Metro Mirror/HyperSwap section of cluster provides continuously available storage (active/active)
• Global mirror link provides the disaster recovery section
• This capability completely integrated into PowerHA 7.3 TR6 and beyond at no extra charge
24
PowerHA i Enterprise Edition multi-target Hyper Swap cluster with DS8000
Application
Global Mirror
Site oneSite two
Site three
HyperSwap section of cluster
© Copyright IBM Corporation 2021
Topology supported natively by PowerHA for i
25
© Copyright IBM Corporation 2019
© Copyright IBM Corporation 2021
Currently, the PowerVS infrastructure only supports host-based replication (i.e., no storage-based replication)
– The PowerHA for i host-based mirroring solution is called geomirror (GLVM for PowerHA AIX)
– Under the covers, geomirror is the native IBM i mirroring replicating memory pages over IP to the primary IASPs and secondary IASP maintaining two identical copies sync mode, and near identical copies async mode.
– You can have a switchable LUN cluster with geomirror replication to the cloud
– It is disk subsystem agnostic although typically used with “internal” disk
– Requires almost zero care and feeding, easily managed by any IBM i customer
– Assuming sufficient bandwidth, there should be no limitation on the scalability from a production point of view, the scale factor relates to the time it might take to resync the data from the DR system back to the production system after a hard crash. The transfer time is determined by bandwidth. Production continues during resync.
– For typical planned outage events such as switch of production to the cloud, there are no scalability issues assuming sufficient quality bandwidth
Considerations for customers migrating from logical replication deployments to PowerHA
– Size the source and target systems properly for additional capacity if needed (memory, disk, etc)
– Do a bandwidth analysis to determine what is needed for satisfactory throughput and response time
– Work with IBM lab services if you do not have the in-house skill to do the same
– Contact me ([email protected]) if you’d like information on BPs that specialize in these types of deployments
– Get ready to save a lot of money, time, and worry
Use PowerHA i geomirror to the cloud or in the cloud
26
© Copyright IBM Corporation 2021
PowerHA for i 7.4 TR4 & 7.3 TR 10
Switchover monitoring and management
• The latest enhancements provide simplified node selection with automated recovery domain management
• Monitor detailed switchover and failover progress from a single node (7.4 only)
Short demo of switchover monitoring and managment
SVC FlashCopy Automation, phase 1
• The integration of IBM FlashSystem FlashCopy technologies is enhanced with integrated automation to simplify FlashCopy
operations that previously required externally developed tools and scripts that performed multi-node operations
Additional Enhancements
• Additional enhancements include continued simplification of PowerHA commands with
interactive prompting from work panels
⎻ Reduces the number of steps required to conduct an HA/DR operation
• For more information, see the IBM PowerHA SystemMirror for i wiki page.
Planned availability date
• June 25, 2021
27
© Copyright IBM Corporation 2021
PowerHA for i enhancement highlights from recent releases
28
December 2019: HA 4.0.1
• Automated setup of the administrative domain with a
streamlined way to easily locate and add many
resources using a single command
• Increased capacity of the administrative domain
by over 340% to support up to 200,000 monitored
resource entries
• Simplified management of the administrative domain
enabling the administrator to easily sort, and filter
monitored resources with the WRKCADMRE
command
• Integrated and streamlined recovery from a data
center outage in a HyperSwap with LUN level
switching environment enabling HyperSwap protection
to be restored with a single command.
March 2020: HA 4.1.1
• Security compliance automation that detects and
disables inactive profiles across all nodes in a
PowerHA environment.
• Enhanced visibility of real-time Recovery Point
Objective (RPO) information for SVC and CSM based
replication
• Simplified and redesigned display session screens that
take advantage of 132 column displays and provide a
simplified view of replication status
June 2020: HA 4.2.1
• PowerHA SQL services for cluster, administrative
domain, and CRG information provide the ability to
explore PowerHA objects and information in new ways
• Simplified updates and upgrades with automated
PowerHA and cluster version managementAdmin Domain Automation
© Copyright IBM Corporation 2021
IBM i SYSBAS and IASP
29IBM Systems Lab Services and Training – ibm.com/systems/services/labservices
…
System ASP
ASP 1Basic
ASPs 2-32
Primary IASP
*SYSBAS
Administrative Domain
*ASPDEV *SBSD
*AUTL *SYSVAL
*CLS *TAPDEV
*ENVVAR *TCPA
*ETHLIN *USRPRF
*JOBD
*NETA
*NWSCFG
*NWSD
*NWSHDEV
*NWSSTG
*OPTDEV
*PRTDEV
SYSBAS
• Licensed Internal Code (LIC)
• Operating System (O/S)
• Licensed Program Products (LPPs)
• Program Temporary Fixes (PTFs)
• Configuration & Security
• Static/Transient Data
• Objects not supported in IASP
IASP
• User Data
• Critical Business Data
• Application Data
Connecting users to IASP data
• User profile work management
• Job description – INLASPGRP, INLLIBL
• Initial program – SETASPGRP
• User job has visibility to libraries in SYSBAS and IAS
© Copyright IBM Corporation 2021
PowerHA i Admin Domain, logical replication, SYBAS
• PowerHA Admin Domain is all that is required to synchronize , add,
delete MRE’s (monitored resource entries e.g., user profiles,
authorization lists etc).
• PowerHA i 7.4 has automated Admin Domain function, for example,
you can add resources with a single command (see the included
links and video)
• The administration domain function is executed within the OS and
slic programmatically. It does not involve the replication of objects.
• There is no need to replicate SYSBAS with logical replication tools.
• You don’t need to use full system replication to avoid SYSBAS
management. Get to 7.4 and use the automated PowerHA Admin
Domain function.
MREs MREs
SYSBAS SYSBAS
Admin Domain
objects left in sysbas
30
https://www.ibm.com/docs/en/i/7.4?topic=policies-powerha-cluster-administrative-
domain-resources
Easily manage adding, deleting, and restoring resources to nodes in the cluster administrative domain
add many resources with a single command:
© Copyright IBM Corporation 2021
PowerHA AIX value proposition
CAPX
• PowerHA for on prem deployments is licensed per processor core, one-time charge, 1st year SWMA included
o SWMA renewal is 20% of list price
o Sub-capacity licensing, meaning you only license the cores deployed into the cluster
o N+1 licensing meaning that the secondary nodes require only one PowerHA and AIX
o Example, 5 production processor cores, 1 secondary system core
» 6 total AIX and PowerHA (N+1)
» Assume small tier, list price for PowerHA enterprise edition: 6($3740) = $22,440
» Annual subscription = $4,488
OPEX
• PowerHA is highly automated, inherently self regulating
• UI enables you to monitor (and manage) all your PowerHA AIX clusters from a single pane of glass
Operational value (the current NPS score is 79)
• Automated failover
• Non disruptive software and hardware maintenance
• PowerHA/GLVM for cloud-based DR operations
31 © Copyright IBM Corporation 2020
© Copyright IBM Corporation 2021
PowerHA AIX UI screen shot health monitoring “at a glance”
PowerHA AIX graphical interface management capabilities
— Zones
— Users
— Roles
— Administrative
Controls
— Activity Log
—33
Included with PowerHA AIX for no additional cost
PowerHA Split/Merge management & quarantine polices
• Spit-Merge Policies enable customer to manage split conditions
⎻ Manual Mode notifies operator of apparent split condition, operator chooses action to be taken
⎻ Tie-Breaker mode happens automatically, the node that reaches it first is the master
Split-Merge options Quarantine Policies
standard cluster Manual-Manual
Tie-Breaker(Disk) -Tie-Breaker(Disk)
Tie-Breaker(NFS) - Tie-Breaker(NFS
Active node halt (ANHP)
HMC node shut down
Disk fencing
SCSI3 reserve-based
stretched cluster
linked cluster
• Quarantine Policies
⎻ Deployed to prevent split conditions
PowerHA AIX two-site private cloud configurations
Two Sites Stretched
Cluster
Linked
Clusters
Inter Site Communication Unicast/Multicast Unicast
Repository Disk Shared Separate
Cluster Communication ✓ Networks
✓ SAN
✓ Disk
✓ Networks
Cross Site LVM Mirroring ✓ ✓
Storage based replication ✓ ✓
HyperSwap ✓ ✓
Multi Site Concurrent RG with /
HyperSwap (active-active)
✓ NA
PowerHA AIX Standard Enterprise
Multi Site Definition
• Site Service IP
• Site Policies
✓ ✓
Stretched Cluster ✓ ✓
Linked Clusters ✓ ✓
HADR with Storage
Replication
NA ✓
HyperSwap NA ✓
Two-site LVM mirror stretched cluster
Two-site linked cluster
Repository Disk
© Copyright IBM Corporation 2021
GLVM
– Cloud support for adding, removing, tuning, encryption, compression, and monitoring
– Resizable cache for asynchronous replication
– Dynamically add or remove volumes
UI security management
– Multifactor authentication (MFA)
Cloud backup management
– Upload or download IBM Spectrum Virtualize clones to IBM Cloud Object Storage
Cross-cluster verification
– Supports up to 8 clusters
GLVM GUI demo live on youtube
PowerHA SystemMirror 7.2.6 GUI enhancements
36
© Copyright IBM Corporation 2021
Logical Volume Manager (LVM) encryption support
DR sizing tool for GLVM
PowerHA with Ansible enables software updates and configuration management
Smart Assist currency support for Oracle, IBM Db2, and SAP NetWeaver
Power10 software and hardware qualifications
PowerHA SystemMirror 7.2.6
37
© Copyright IBM Corporation 2021
PowerHA IBM cloud DR
The IBM cloud currently requires data replication over IP
⎻ PowerHA AIX + GLVM native AIX LV mirroring over IP
⎻ PowerHA i + geomirror native IBM i mirroring over IP
⎻ GLVM guidlines
PowerHA AIX GLVM
IBM Cloud IBM CloudIBM Cloud
PowerHA igeomirror
PowerHA AIX GLVM
PowerHA igeomirror
© Copyright IBM Corporation 2021
PowerHA for AIX is the host-based mirroring is called GLVM
– Under the covers it is the traditional AIX LVM native mirroring replicated over IP to the secondary system therefore maintaining two (or three) identical copies sync mode, and near identical copies async mode
– It is disk subsystem agonistic and is implemented via Remote Physical Volumes which virtualizes the remote disk to appear local. This as opposed to LUNs which are used via SAN storage.
– Requires very little care and feeding, easily managed by the AIX customer
– You will use term licensing for public cloud deployments since it is registered to the customer not the serial number
– Reserve sufficient capacity for running your production on a DR virtual server by licensing the number of cores required. N+1 licensing doesn’t apply since expanded capacity on demand can’t be guaranteed.
Currently deployed on premise primarily in smaller environments although we have tested up to 50 Tbytes
– There is no limitation on the scalability from a production point of view, if the systems are properly configured with sufficient disk, memory and quality bandwidth. Source and target systems need to be matched for equal throughput.
– For existing customers, match the bandwidth and target configuration throughput to the current on prem deployments.
For customers currently using SAN storage looking to deploy via GLVM
– Size the source and target systems properly using the AIX performance tools for additional capacity as needed (memory, disk, etc.)
– At present, we don’t have a means to estimate required bandwidth therefore it would be prudent to do a POC prior to a full deployment.
– Work with IBM lab services if you do not have the in-house skill to do the same
– Contact me if you’d like information regarding firms that specialize in these types of deployments
PowerHA AIX GLVM to the cloud or in the cloud
39
© Copyright IBM Corporation 2021
Section 3: Active/Active
• Db2 Mirror
Db2 Mirror whitepaper
© Copyright IBM Corporation 2021
Db2 Mirror value proposition
• CAPX
⎻ Db2 Mirror deployments are licensed per processor core, one-time charge, 1st year SWMA included
o Provides RTO = 0 and RPO = 0, continuous availability
o SWMA renewal is 20% of list price
o N+N licensing meaning that the CBUs are not relevant in the production site Db2 Mirror configuration
⎻ CBUs can be used on the DR servers at the DR site N+1 with PowerHA managing DR
• OPEX
⎻ UI enables at-a-glance health monitoring and configuration management
⎻ Doesn’t require third party or dedicated monitoring
⎻ Staffing requirements less than logical replication
• Operational value
⎻ Multiple options for logical and physical topologies
⎻ FlashCopy and BRMS enable off-line backup operations
⎻ Enables rolling upgrades and software maintenance
41 © Copyright IBM Corporation 2020
© Copyright IBM Corporation 2021
42
IBM Db2 Mirror for i
IBM Db2 Mirror for i: Enables Continuous Availability
- High speed synchronous replication of Db2 for i
(Data Center Solution)
- Access Db2 objects from either LPAR
Application Availability Enablement
- Two Nodes read and write to the same DB Files
- Enables quickly moving all work to one node, for planned
maintenance or node failure
Enables Business Continuity for Disruptive System Upgrades
- Nodes can be at different OS levels
- Nodes can be on different Power Hardware Generations
- Rolling upgrades for no downtime
- Roll a node back a release with minimal impact if
Active/Active applications are enabled
– Requires POWER8 or later and IBM i 7.4
– New IBM i LPP 5770DBM
Db2 Mirror
Application
Architecture
• Remote Direct Memory Access
(RDMA)
• RDMA over Converged Ethernet
(RoCE)
• Typical distance between nodes
100m or 200m
• With new adaptors, distance can
potentially be extended to 10KM
⎻ Note: workload and bandwidth
determine viable distance.
• Lab Services recommends following the PowerHA / IASP model using IBM external storage (DS8000 or FlashSystem)
⎻ Db2 Mirror is a local HA solution, any production deployment should be coupled with a remote storage-based DR
solution. You can deploy the CBUs at the DR site to minimize licensing requirements.
⎻ These are the most resilient configuration, there are options such as a single server at the DR site and single
storage at the DR site, each partitioned into two LPARs.
• A configuration with a single server or single storage has decreased resiliency which compromises the Db2 Mirror
design objective of maximum uptime. Dedicated IBM Power Servers and IBM external storage units are recommended.
• Lab Services have not tested and do not support the following environments.
⎻ Non-IBM external storage, i.e., EMC
⎻ Full System replication environments
⎻ Software/Logical replication (for DR)
Db2 Mirror for i guidelines
Initial Clone/Re-clone
via Metro Mirror
(SYSBAS & DB IASP)
• DS8870 or higher. 4 Power Servers (4 systems)
• RoCE adapter(s) required. Must be installed in CEC.
• Db2 Mirror relationship at both sites
• IBM DS8 external storage interface allows for automated clone of
SYSBAS and DB IASP via Metro Mirror
• Object Tracking List (OTL) determines what is included in the Db2
Mirror replication environment (for SYSBAS and the DB IASP)
• Admin Domain across sites for SYSBAS user profile sync, etc.
• Global Mirror for DB IASP remote sync
• MT-PPRC (MMIR + GMIR + GCP) for IFS IASP local and remote sync
• DB IASP switched via PowerHA Container CRG
• Planned DR switch ensures Global Mirror session consistency
• Unplanned DR switch requires DB IASP re-clone
• IFS IASP exists on one node, but accessible from both nodes
• IFS IASP switched via PowerHA CRG
• IFS IASP Global Copy at DR site converted to Metro Mirror after
switch
DS8000 - 4 IBM i and 4 DS8 with IASP
Global Mirror
Metro Mirror
Global Copy
Global Mirror
Global Mirror
Db2 Mirror via RoCE
DR Server 1 (CBU) DR Server 2 (CBU)
= SYSBAS
= IASP for Database Objects
= IASP for IFS Objects
Db2 Mirror via RoCE
Prod Server 1 Prod Server 2
= SYSBAS
= IASP for Database Objects
= IASP for IFS Objects
• IBM FlashSystem cluster. 4 Power Servers (4 systems)
• Each production server has a dedicated I/O group(s)
• FS = 4 I/O Groups max, IBM i workload = 2 I/O Groups max
• RoCE adapter(s) required. Must be installed in CEC
• Db2 Mirror relationship at both sites
• IBM FlashSystem external storage interface allows for automated
clone of SYSBAS and DB IASP via Flash Copy
• Object Tracking List (OTL) determines what is included in the Db2
Mirror replication environment (for SYSBAS and the DB IASP)
• Admin Domain across sites for SYSBAS user profile sync, etc.
• Global Mirror for DB IASP remote sync
• Volume Mirroring between I/O Groups for IFS IASP local sync
• Global Mirror for IFS IASP remote sync (I/O Group 1)
• DB IASP switched via PowerHA Container CRG
• Planned DR switch ensures Global Mirror session
consistency
• Unplanned DR switch requires DB IASP re-clone
• IFS IASP exists on one node, but accessible from both nodes
• IFS IASP switched via PowerHA CRG
FlashSystem - 4 IBM i and 2 clustered FS with IASP
Db2 Mirror via RoCE
DR Server 1 (CBU) DR Server 2 (CBU)
I/O Group 1
I/O Group 2
Db2 Mirror via RoCE
Prod Server 1 Prod Server 2
Global Mirror Global Mirror
I/O Group 1
I/O Group 2
Global Mirror
Initial Clone/Re-clone
via Flash Copy
(SYSBAS & DB IASP)
IFS IASPVolume Mirroring
IFS IASPVolume Mirroring
Which objects are replicated?
Additional replicated objects:
• Environment Variables
(System Level)
• Programs / Service Programs
• Data Areas
• System Values
• Libraries
• Job Descriptions
• Journals
• Data Queues
• User Spaces
• User Indexes
• Output Queues / Spooled Files
o Replication Interval
• Definition only
o Job Queues
o Optional: Data Areas
o Optional: Database Files
Database replication eligible objects
Native:
• Database Physical & Logical File
SQL:
• Alias
• Function
• Global Variable
• Index
• Procedure
• Schema
• Sequence
Included with File support:
• Row Permission
• Column Mask
• Temporal Table
• Constraint
• Etc…
• SQL Package• Table• Trigger• User Defined Type• View• XML Schema
Repository
47
Determining Rules for Replication
Example 1:
Default Inclusion State: Exclude
Include everything in library Sales except output queues,
but include output queue Receipts
Replication Criteria List
• Rules based engine
• Hierarchical
Default Inclusion State
• Include – replicate every eligible object that exists
plus any new objects as they are created
• Exclude – replicate nothing
Then add hierarchical rules at lower levels
• Library
• Object type within library
• Specific object
Example 2:
Default Inclusion State: Include
Include everything in library Sales except output queues,
but include output queue Receipts
Library Object Type Object Incl/Excl
Sales *all *all Include
Sales *OUTQ *all Exclude
Sales *OUTQ Receipts Include
Library Object Type Object Incl/Excl
Sales *OUTQ *all Exclude
Sales *OUTQ Receipts Include
48
Db2 Mirror – Security Implementation
Security changes are always replicated:
•User Profiles
•Public & Private Authorities
•Function Usage
•Ownership
•Security Attributes
•Authorization Lists
•Security related System Values
Synchronous replication of Security Implementation
is not optional
49
RoCE
Node 1
Database
App
Node 2
Database
App
Run Production Workloads on this node Run Queries and reports on this node
Db2 Mirror – Active Passive* Applications
*Active/Passive at the app layer
The DB layer is active/active
N production cores
N= Ndb+Napp
Consider using DLPAR or
Pools 2.0 to allow shifting Napp
processor activations from
Node 1 to Node 2 upon failover
With this configuration you can take advantage of DLPAR or Pools 2.0 to minimize licensing by switching the app server workload from primary to secondary
Db2 Mirror – Web Application Topologies
RoCE
Node 1
Database
Node 2
Database
Liberty
Tomcat
WebSphere
JDBC
Liberty
Tomcat
WebSphere
JDBC
Browser Browser
LoadBalancer
Active Active Web & Database
IBM i Support - Liberty- Tomcat - WebSphere
RoCE
Node 1
Database
Node 2
Database
Liberty
Tomcat
WebSphere
JDBC
Liberty
Tomcat
WebSphere
JDBC
Browser Browser
LoadBalancer
RoCE
Node 1
Database
Node 2
Database
Rest Server
SQL
Browser Browser
LoadBalancer
Active Active Rest Connection
The Load Balancer determines the side that is active. Now the Rest connection and the data are both continually available.
RPG
Rest Server
SQLRPG
RoCE
Node 1
Database
Node 2
Database
PHP
Python
Node.JS
ODBC ODBC
Browser Browser
LoadBalancer
Active Active Web & Database
IBM i Support - PHP- Python - Node.JS- Others….
PHP
Python
Node.JS
RoCENode 1
Database
Node 2
Database
Browser Browser
Web Servers running off the Mirrored IBM i Node
ODBC does not have alternative server support, so no fail over
PHP
Python
Node.JS
PHP
Python
Node.JS
ODBC ODBC
RoCENode 1
Database
Node 2
Database
Liberty
Tomcat
WebSphere
Browser Browser
JDBC w/Alternate
Server Web Servers running off the Mirrored IBM i Node
JDBC with Alternative Server support, detects the active node and routes request
Liberty
Tomcat
WebSphere
52
Db2 Mirror over Distance – (December GA)
• New adapter will also support RoCE v2
• Encryption is required by default but can be removed.
• Supported distance up to 10km
⎻ Previous limit of 200m
o 100m cables with a switch in-between
⎻ Can use LR transceivers or switches/routers
53
Encrypted Db2 Mirror for i – (December GA)
• New Db2 Mirror Property to enforce encryption
configurations.
• The new default will be to require encryption, but this
property can be overridden.
• Existing Db2 Mirror customers will be set to ‘Not
Required’ and will have to change to ‘Required’ if
desired.
• This property does not configure encryption but only
enforces the policy of what will be allowed. You can
configure encryption even if it is not required.
© Copyright IBM Corporation 2021
54
DB2 Mirror implementation roadmap with Lab services
DB2 Mirror Readiness assessment Lab Services offering*
Learn DB2 Mirror in a lab environment
Load and test application with DB2M experts
Perform initial performance comparison batch jobs
Other options for starting are
Db2 Mirror test drive via IBM garage… access to a DB2M
cluster for up to 2 weeks but all self driven no education or
experts to assist.
Db2 Mirror setup exercise via IBM garage. Self driven with
instructions for save/restore DB2Mirror setup
Note that most customers who will use the IBM garage for
an initial look at DB2 Mirror will also use the DB2 Mirror
readiness assessment for in-depth skills transfer and
application review
START
* See DB2 Mirror Readiness assessment page for more information
Purchase hardware to setup DB2 Mirror
in house in a test environment
© Copyright IBM Corporation 2021
55
DB2 Mirror implementation roadmap with Lab services
In house applications testing
• Functional testing of applications not tested during
the readiness assessment
• Performance testing of all critical applications
• It is expected that application may need to be
updated to perform satisfactorily in a DB2
Mirror environments
• Lab Services consultants can assist with best
practice for coding for performance
• MQ. How to move forward with an MQ environment
• IFS.. Setting up PowerHA for IFS and running with
IFS in an active-active high availability
environment. Determining the impacts to
applications during a switch
RESYNC testing
• Analyze locks held during run time
that would affect resync
• Test resync at different points of run
time during day/night runs
• Create process to check for conflicts
prior to a resync
• Create processes to exclude extra
objects from resync I.e work files etc
© Copyright IBM Corporation 2021
56
DB2 Mirror implementation roadmap with Lab services
Error recovery testing
• Test recovering from objects in error
• How to identify dependent objects
• Identify triggers, referential integrity
• Test recloning via hard reclone
• Test recloning SYSBAS with soft reclone ( if using
IASP )
PowerHA for DR ( if applicable )
• Configure DR with PowerHA and IASP
• Configure cluster containers for
switching multiple CRGs
simultaneously
• Configure DB2 Mirror at DR site.
Register Data IASP(s) for Db2 Mirror at
DR
• Test switching and recovery
• Test crashing nodes and switching
© Copyright IBM Corporation 2021
57
DB2 Mirror implementation roadmap with Lab services
Management processes
• Design management processes for Db2 Mirror
• Exit programs for automation
• Prevent shutdown if primary or IFS
owner
• Start CRGs for DR
• Start SBS and app if made primary
• Create programs for management
• Use System ( SQL ) services or Lab services
tools to
• Check status
• Start/stop DB2 Mirror
• Check if objects in error
• Add/remove objects from RCL as
required
• etc
Go live
• Implement IASP in production if
necessary
• Add DB2 Mirror into production
environment
• Either
• Add to existing prod node in
PowerHA
• Create Cluster or Db2M on single
node
• Add DR solution
IBM i on Power Systems Workshops
|1
0
Future Madeibm.com/it-infrastructure/services/lab-services Contact us: [email protected]
OverviewThe Db2 Mirror for i customized consulting engagement will provide customers,
Business Partners, and ISVs the skills required to implement a Db2 Mirror solution, as
well the ability to test their applications on a Db2 Mirror environment in the lab. This
consulting assessment is available as a variable length engagement in increments of 1
week. The maximum time for an engagement will be 3 weeks. At the end of the session
the attendees will have the knowledge of Db2 Mirror to continue working and testing as
required.
Target AudienceAny customer, Business Partner, or Independent Software Vendor who wishes to learn
about Db2 Mirror in depth, and test their application.
BenefitsBy the end of the workshop, attendees will have the knowledge necessary to start
planning their Db2 Mirror environment.
Qualifying Questions• Do you need a zero time failover environment to an active high availability system?
• Do you wish to start working towards a true active/active solution?
Team ContactsOwner: Selwyn Dickey [email protected]
Eric Barsness [email protected]
Opportunity manager Mike Gordon [email protected]
--
IBM Systems Lab Services — Power Systems IBM i
Db2 Mirror for i Readiness Assessment
Key Features• The engagement is fixed price for the first week, and variable for additional weeks.
• There are many topics within Db2 Mirror available, so each engagement will be
customized based on requirements.
• During the workshop the following consulting options are available: planning,
implementation, application compatibility, performance & failure testing.
• During the first week the partitions will be loaded with the customers/BPs/ISVs test
environment and cloned to create a Db2 Mirror solution.
• During the second week we would focus on performance and failure testing.
• The third week is optional for clients who wish to further optimize their applications
running in DB2 mirror.
• The available hardware is either:
• Ten POWER8 cores per partition and up to 10TB of DS8000 disk per partition.
• Four POWER9 cores per partition and up to 10TB of SVC/Flash disk per
partition.
• The testing can be performed for IASP/PowerHA, or full system.
• No HIPAA or PHI data can be loaded on the IBM systems.
Deliverables• Any presentation used in the workshop will be available to the attendees.
• Any data (performance, object changes, etc..) will be available for the attendees to
save to tape and take home.
Duration
The workshop can be purchased in increments of 1 week. Typically 2 weeks is
sufficient to perform a reliable assessment.
Availability is limited to 2 customers simultaneously.
© Copyright IBM Corporation 2021
PowerHA, VM Recovery Manager, Db2 Mirror
Thank you
© Copyright IBM Corporation 2021
Additional reference Material
60
• PowerHA home page
• IBM PowerHA SystemMirror for i
• ibmi-BRMS
• PowerHA AIX wiki
• Linkedin PowerHA AIX
• Linkedin PowerHA IBM i
• PowerHA AIX internal wikie/FAQs
1.Choosing the right HA/DR solution2.Live Demo: Deploying PowerHA and Introduction to IASPs3.Live Demo: Managing PowerHA solutions4.What's new in PowerHA
POWERUP 2021 sessions you should attend
© Copyright IBM Corporation 2021
For More Information:
61
Links You Need Twitter #Hashtags
IBM i Home Page: https://www.ibm.com/it-infrastructure/power/os/ibm-i
(find link to Forrester Study and updated IBM i Strategy Whitepaper)
IBM Strategy Whitepaper: https://www.ibm.com/it-infrastructure/us-
en/resources/power/i-strategy-roadmap/
IBM Client Success: https://www.ibm.com/it-infrastructure/us-en/resources/power/ibm-i-customer-stories/
Support Life Cycle: https://www.ibm.com/support/lifecycle/
License Topics: https://www-01.ibm.com/support/docview.wss?uid=nas8N1022087
HelpSystems 2021 Marketplace Survey https://www.helpsystems.com/resources/guides/ibm-i-marketplace-survey-results
@IBMSystems
@COMMONug
@IBMChampions
@IBMSystemsISVs
@IBMiMag
@ITJungleNews
@SAPonIBMi
@SiDforIBMi
#PowerSystems
#IBMi
#IBMAIX
#POWER9
#LinuxonPower
#OpenPOWER
#HANAonPower
#ITinfrastructure
#OpenSource
#HybridCloud
#BigData
© Copyright IBM Corporation 2021
Cognitive Systems HADR solutions: perpetual licensing/pricing
Product ID Small Tier
System/core
Medium Tier
System/core
Comments
PowerHA SystemMirror for AIX Standard 5765-H37 $2860 $3740 N+1 model (N=Active cores, 1 for
passive node/s)
Enterprise 5765-H39 $3400 $5250
PowerHA SystemMirror for i Standard 5770-HAS $2860 $3740
Enterprise 5770-HAS $3400 $5250
VM Recovery Manager HA 5765-VRM $530 $530 N+0 model (N= Active cores, 0
needed for secondary partitions)DR
(formerly GDR)
5765-DRG $1060 $1060
Db2 Mirror HA 5770-DBM* $12,000 $20,000 N+N model, where N=the number of
production cores in the Db2 Mirror
cluster configuration
List Price (U.S.)/Core with 1st year SWMA
For a Db2 Mirror HA configuration, you may use N+1 licensing for PowerHA, use the CBU at the DR site
For VM Recovery Manager DR, a CBU is not required however, you may desire 1 permanent IBM i on the DR box to avoid 70 day
PowerHA i is in the PowerVS catalog, for PowerHA AIX you will use term licensing
PowerHA i will converge to a single PID in 7.5 for simplification. The PID will in effect be today’s Enterprise Edition.
For the Db2 Mirror active/passive mode, N on production, less than N on the target, DB is active/active, apps are active/ passive
— The table shows the U.S. list prices for term and permanent (perpetual) licensing with associated Product IDs (PIDs).
— PowerHA for AIX term options are available in 3, 6,12 or 36 month terms, and in both Standard and Enterprise Editions.
— Small tier represents IBM Power Systems in the range of S914/S814, S922/S822, S924/S824, S950/S850. The Power Systems models E870/E880/E980/etc are medium tier.
— Term offering includes license and SWMA all in the one price. At the end of the term, the license to use the software (along with support) terminates, so the client must either order another term, order a perpetual license, or stop using the product.
— Perpetual license: the client has the license permanently; license and the first year of SWMA included with the price, then SWMA renewed after the first year.
— Term license: the client has the license and support entitlement for the term purchased.
PowerHA for AIX Term Licensing Option Now Available
63
PowerHA for AIX TERM PERMANENT
Per core per
month
(approx.) 3 months 6 months 12 months 36 months
Perpetual
license
(includes one
year of SWMA)
Standard Edition 5771H7S 5772H7S 5773H7S 5774H7S 5765H39
Small Tier – $119 $119 $358 $715 $1,430 $4,290 $2,860
Med Tier - $152 $152 $456 $913 $1,825 $5,475 $3,650
Enterprise Edition 5771H7E 5772H7E 5773H7E 5774H7E 5765H37
Small Tier- $156 $156 $468 $935 $1,870 $5,610 $3,740
Med Tier - $218 $218 $656 $1,313 $2,625 $7,875 $5,250
Last updated October 4, 2019
PowerHA for AIX licensing in the cloud:
1. Client’s perpetual PowerHA licenses: cannot transfer or cannot bring their own license to the cloud
2. Clients can acquire PowerHA for AIX fixed term licenses and deploy on a system within their enterprise or in the cloud or a service provider machine
3. When deploying in cloud, consider licensing as many processors as you wish to hold in reserve
PowerHA licensing, whether fixed term or perpetual:
1. Enterprise Edition is required when replicating data within a PowerHA cluster
2. Standard Edition is deployed only with a shared-storage configuration (no data replication)
3. Sub-capacity licensing means that only the processor cores that are incorporated into the cluster need be licensed
4. N+1 licensing means that the 2nd node (system/LPAR) in the cluster requires only one PowerHA license
PowerHA for AIX Licensing Basics on premise
64
PowerHA
N +1 licensing
production/primary node secondary node
PowerHA SystemMirror Standard Edition 6 month term Enterprise Edition 6 month term
Small Tier $715/core/6 months $935/core/6 months
Single Tenant Example
— When doing a relative cost assessment of the AIX (and PowerHA for AIX) software stack in the cloud, be sure to include the cost of the database in the comparison.
• E.g., AIX + PowerHA for AIX + Oracle DB cost
— The PowerHA for AIX term entitlement, while also called “monthly”, is a fixed term, where the client who orders the license pays for it all up front. E.g., the client orders 36-month term PowerHA for AIX pays for the 36 months when the order is placed.
— Order PowerHA for AIX fixed term through the Power hardware channel (i.e. e-config)
• PowerHA for AIX term licensing PIDs are available in the software-model-only path in e-config. In this software-only path, a machine-type-model or Serial Number are not required.
— The license stays entitled under the end client’s Customer Number, and the end client can use the license on any machine, including a cloud provider
• When PowerHA for AIX license is used on the cloud provider machine, the entitlement does not transfer to the provider but stays with the end client.
— For price quotes, special bids, etc, use the same tools that are used for PowerHA for AIX perpetual licensing (e-config, ePricer, etc)
— Any questions re: running configs with PowerHA for AIX (or AIX or PowerSC) fixed term, contact Digital Techline team:
• IBM: http://w3.ibm.com/support/techline
• Eligible Partners: http://www.ibm.com/partnerworld/techline
Sales/Ordering Notes
65
The new 4th data protection practice
Business continuity
“Capability of a business to withstand outages and to operate important services normally and without interruptions in accordance with predefined service-level agreements.”
Business continuity consists offour important parts:
New threats call for new methods
The traditional methods (HA, DR, BU) of protection are no longer enough. Organizations need to be Cyber Resilient.
Cyber Resiliency, a new addition to the Business Continuity umbrella, is the ability for an organization to continue to function after a breach has occurred.
New
Client and IBM internal use66
High
Availability
Cyber
Resiliency
Disaster
Recovery
Backup
What makes a CR copy different from the other copies?
Client and IBM internal use 67
HA and DR copies are synchronous / asynchronous
and will not help against Ransomware
Backup copies are ‘point in time’ (PIT) copies but they
are unprotected
You need protected ‘point in time’ (PIT) copies
Cyber Resilient (CR) copies are PIT copies
with added layers of protection:
Immutability and/or Isolation
High Availability (HA) copies:
synchronous copies within a
site
Disaster Recovery (DR) copies:
synchronous or asynchronous
copies between sites
Backup (BU) copies:
unprotected PIT copies
Cyber Resilient (CR) copies:
protected PIT copies
CVSA goal
The Cyber Vault offering
• Is based on IBM’s Safeguarded Copy (SGC) solution
• Is a set of three services…
• And is composed of a set of core components
CVSA goal
• To ensure a smooth, tailored and expediated implementation of Cyber Vault, which includes Safeguarded Copy (SGC)
Client and IBM internal use 68
Client and IBM internal use
Safeguarded Copy prevents point in time copies of data from being modified or deleted due to user errors, malicious destruction or ransomware attacks
The Cyber Vault offering is based on the IBM Safeguarded Copy solution
Provides additional security capabilities to prevent non-privileged users from
compromising protected data
Separation of duties
Provides immutable and isolated point in time copies of the data
Protected Copies
Automatically creates point in time copies; and a simplified recovery and
restoration process
Automation
69
Access and Control
Simplified
© Copyright IBM Corporation 2021
SAN Storage replication vs logical replication
70
PowerHA Full System
replication
Logical replication
IBM product Yes Yes No
CPW overhead Minimal (admin domain) None Can be substantial
CBU licensing 1 IBM i 1 IBM i Multiple to support replication workload
Apply lag at target Not applicable Not applicable Can be substantial depending on workload
Com line bandwidth requirement Medium(writes to IASP) High (all writes) Low (journal entries only)
Source target data consistency sync
mode
100% 100% No real sync mode option, Logical Replication
relies on software audits to determine
object/data integrity
Source target data consistency
async mode
Seconds Seconds Data inflight and data not yet replayed on
target not in sync
Replication engine IBM storage IBM storage Third party host-based replication
Replication works if TCP/IP inactive yes yes Remote journal or other proprietary mirroring
methods enable recovery of stored/Queued up
transactions
Object Recovery on failover IBM i recovers data
from journals
IBM i recovers data
from journals
3rd party application performing host-based
replay process
Out of sync object recovery Not applicable Not applicable Save/restore objects restart replication
© Copyright IBM Corporation 2021
SAN Storage replication vs logical replication (page 2 of 2)
71
PowerHA Full System replication Logical replication
Save to media process IASP FlashCopy/BRMS
network
Full System FlashCopy
with BRMS data restore
to production
Custom process to halt replay tasks
followed by save while active
Backup window eliminated eliminated Varies by data and workload
© Copyright IBM Corporation 2021
IBM Cloud Storage Solutions for i
• Can enable you to:
• Send backups ‘directly’ to a cloud location
• Perform move/backup operations on or off prem
• Create a shared file portfolio in the cloud
• Utilize an IBM COS device
• Currently recommended for < 4Tbyte of data
72
© Copyright IBM Corporation 2021
IBM Cloud Storage Solutions for i
73
© Copyright IBM Corporation 2019
Place your IBM i data system in a cloud Cloud or FTP storage
• Three modes of operation
⎻ BRMS to Cloud for backup operations
⎻ GUI dashboard for storing and retrieving files in the cloud
⎻ IBM i command interface
© Copyright IBM Corporation 2021
Cloud Storage Solutions offering price/licensing
• Priced per VM (LPAR)
• Cloud storage options: IBM cloud, AWS cloud or BP cloud providers, IBM COS
• BRMS turn-key for backup/recovery automation
⎻ BRMS will auto configure and set up storage backup profile
⎻ Not required if one chooses to roll their own manually or via scripts
• Advanced function
⎻ Compression, Encryption
• https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/165642461/Welcome+to+IBM+Backup+Recovery+Me
dia+Services+BRMS+for+i
• knowledgecenter ICC
PID: 5733 ICC V1R2 Description Price
Option 1 Cloud storage API, BRMS enabled
$2400/VM
Option 2 Compression and Encryption
Option 1 + $1000/VM
U.S. list prices, prices are subject to change at any time
© Copyright IBM Corporation 2021
For More Information:
75
Links You Need Twitter #Hashtags
IBM i Home Page: https://www.ibm.com/it-infrastructure/power/os/ibm-i
(find link to Forrester Study and updated IBM i Strategy Whitepaper)
IBM Strategy Whitepaper: https://www.ibm.com/it-infrastructure/us-
en/resources/power/i-strategy-roadmap/
IBM Client Success: https://www.ibm.com/it-infrastructure/us-en/resources/power/ibm-i-customer-stories/
Support Life Cycle: https://www.ibm.com/support/lifecycle/
License Topics: https://www-01.ibm.com/support/docview.wss?uid=nas8N1022087
HelpSystems 2021 Marketplace Survey https://www.helpsystems.com/resources/guides/ibm-i-marketplace-survey-results
@IBMSystems
@COMMONug
@IBMChampions
@IBMSystemsISVs
@IBMiMag
@ITJungleNews
@SAPonIBMi
@SiDforIBMi
#PowerSystems
#IBMi
#IBMAIX
#POWER9
#LinuxonPower
#OpenPOWER
#HANAonPower
#ITinfrastructure
#OpenSource
#HybridCloud
#BigData
© Copyright IBM Corporation 2021
Special notices
76
This document was developed for IBM offerings in the United States as of the date of publication. IBM may not make these offerings available in other countries, and the
information is subject to change without notice. Consult your local IBM business contact for information on the IBM offerings available in your area.
Information in this document concerning non-IBM products was obtained from the suppliers of these products or other public sources. Questions on the capabilities of non-
IBM products should be addressed to the suppliers of those products.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these
patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-1785 USA.
All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
The information contained in this document has not been submitted to any formal IBM test and is provided "AS IS" with no warranties or guarantees either expressed or
implied.
All examples cited or described in this document are presented as illustrations of the manner in which some IBM products can be used and the results that may be
achieved. Actual environmental costs and performance characteristics will vary depending on individual client configurations and conditions.
IBM Global Financing offerings are provided through IBM Credit Corporation in the United States and other IBM subsidiaries and divisions worldwide to qualified
commercial and government clients. Rates are based on a client's credit rating, financing terms, offering type, equipment type and options, and may vary by country.
Other restrictions may apply. Rates and offerings are subject to change, extension or withdrawal without notice.
IBM is not responsible for printing errors in this document that result in pricing or information inaccuracies.
All prices shown are IBM's United States suggested list prices and are subject to change without notice; reseller prices may vary.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
Any performance data contained in this document was determined in a controlled environment. Actual results may vary significantly and are dependent on many factors
including system hardware configuration and software design and configuration. Some measurements quoted in this document may have been made on development-
level systems. There is no guarantee these measurements will be the same on generally-available systems. Some measurements quoted in this document may have
been estimated through extrapolation. Users of this document should verify the applicable data for their specific environment.
Revised September 26, 2006
© Copyright IBM Corporation 2021
Special notices (cont.)
77
IBM, the IBM logo, ibm.com AIX, AIX (logo), AIX 5L, AIX 6 (logo), AS/400, BladeCenter, Blue Gene, ClusterProven, Db2, ESCON, i5/OS, i5/OS (logo), IBM Business Partner (logo), IntelliStation, LoadLeveler, Lotus, Lotus Notes,
Notes, Operating System/400, OS/400, PartnerLink, PartnerWorld, PowerPC, pSeries, Rational, RISC System/6000, RS/6000, THINK, Tivoli, Tivoli (logo), Tivoli Management Environment, WebSphere, xSeries, z/OS, zSeries,
Active Memory, Balanced Warehouse, CacheFlow, Cool Blue, IBM Systems Director VMControl, pureScale, TurboCore, Chiphopper, Cloudscape, Db2 Universal Database, DS4000, DS6000, DS8000, EnergyScale, Enterprise
Workload Manager, General Parallel File System, , GPFS, HACMP, HACMP/6000, HASM, IBM Systems Director Active Energy Manager, iSeries, Micro-Partitioning, POWER, PowerExecutive, PowerVM, PowerVM (logo),
PowerHA, Power Architecture, Power Everywhere, Power Family, POWER Hypervisor, Power Systems, Power Systems (logo), Power Systems Software, Power Systems Software (logo), POWER2, POWER3, POWER4,
POWER4+, POWER5, POWER5+, POWER6, POWER6+, POWER7, System i, System p, System p5, System Storage, System z, TME 10, Workload Partitions Manager and X-Architecture are trademarks or registered
trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol
(® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries.
A full list of U.S. trademarks owned by IBM may be found at: http://www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
AltiVec is a trademark of Freescale Semiconductor, Inc.
AMD Opteron is a trademark of Advanced Micro Devices, Inc.
InfiniBand, InfiniBand Trade Association and the InfiniBand design marks are trademarks and/or service marks of the InfiniBand Trade Association.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the
United States and other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries or both.
Microsoft, Windows and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries or both.
NetBench is a registered trademark of Ziff Davis Media in the United States, other countries or both.
SPECint, SPECfp, SPECjbb, SPECweb, SPECjAppServer, SPEC OMP, SPECviewperf, SPECapc, SPEChpc, SPECjvm, SPECmail, SPECimap and SPECsfs are trademarks of the Standard Performance Evaluation Corp
(SPEC).
The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are trademarks and service marks licensed by Power.org.
TPC-C and TPC-H are trademarks of the Transaction Performance Processing Council (TPPC).
UNIX is a registered trademark of The Open Group in the United States, other countries or both.
Other company, product and service names may be trademarks or service marks of others.
Revised December 2, 2010