backups

Transcription

backups

Université IBM i
IBM Power Systems - IBM i
10 et 11 mai 2016 – IBM Client Center de Bois-Colombes
S7 – Disponibilité IBM i
Mardi 10 Mai – 14H00 – 15H30
Joseph Esnault – IBM France
© IBM France 2016
Agenda
Architecture résiliente
Availability Updates
– Disponibilité du serveur Power IBM i : rappel des principales améliorations
– Architectures de disponibilité dont Cluster PowerHA for i.
© IBM France 2016
Qu’entend-on par résilience?
Résilience
La Résilience se définit comme étant la capacité pour un matériau ou un système
à répondre et à s’adapter rapidement à tout changement dynamique interne ou
externe et à revenir à un état stable.
« Business Resilience »
Pour l’entreprise la « Business Resilience » est l'aptitude à s'adapter et à
répondre rapidement, tant aux risques qu'aux nouvelles opportunités, afin de
garantir la continuité de l'activité.
Un des piliers de la « Business Resilience » est une infrastructure résiliente. En
parallèle de cette infrastructure, l’entreprise doit s’assurer de tous les moyens
humains et logistiques pour mettre en œuvre cette infrastructure.
3
© IBM France 2016
Le coût d’une interruption de service
Une interruption de service peut avoir des conséquences négatives multiples pour une entreprise:
Perte de revenu
Perte de productivité au niveau des utilisateurs
Perte de productivité au niveau du système d’information
Paiement de pénalités, d’amendes
Marchandises perdues
Perte d’image
Etc.
Et les modèles d’entreprise ont évolué:
Convergence des besoins métiers avec les services du système d’information
Nouveaux modèles intégrant le cloud et l’Analytics.
Interaction directe du client avec le système d’information de l’entreprise (Systems of Engagement)
besoin accru de flexibilité, capacité à répondre rapidement, disponibilité et
sécurité
4
© IBM France 2016
Une infrastructure résiliente et performante est primordiale
dans le CAMS
Big Data &
Analytics
Cloud
Améliorer l'économie de
l'information grâce à
l'efficacité et la fourniture
de nouveaux produits et
services plus rapidement
Gérer des volumes de
données importants, en
temps réel
Analytics
Cloud
5
Security
Mobile & Social
Révolutionner le partage
d'informations et la
collaboration dans l'entreprise
Mobil
e
Social
© IBM France 2016
Les aspects de la résilience
Continuité de Services
Haute Disponibilité
Modularité: capacité à ajuster la puissance,
disponibilité immédiate de ressources
Anticipation des besoins de ressources
Architecture permettant d’éviter les arrêts
planifiés (upgrades OS, middleware, applicatifs,
matériels)
Pas de SPOF (single point of failure)
Automatisation de la reprise et du retour
Classiquement sur un site type campus
Solution généralement orientée matériel
Toutes les applications ne sont pas
nécessairement concernées.
Plan de Secours Informatique / PSI
Possibilité de restaurer et de redémarrer une infrastructure
informatique après un sinistre majeur et conformément aux :
DMIA (Délai Maximum d’Interruption Admissible, RTO)
PDMA (Perte de Données Maximale Acceptée, RPO)
Engagements de services (Service Level Agreement, SLA)
6
© IBM France 2016
Les indicateurs de la résilience
Perte de Donnée Maximale Autorisée (PDMA) - Recovery Point Objective
(RPO)
Correspond au point de restauration des données. Combien de temps d’activité sur les
données peut-on perdre? Ou combien de données faut-il reconstruire?
Durée Maximale d’Interruption Admissible (DMIA) - Recovery Time
Objective (RTO)
Correspond au temps de restauration. Pendant combien de temps la production peut-elle être
arrêtée?
A considérer également:
– Durée Maximale pour le retour du réseau - Network Recovery Objective (NRO)
Correspond au temps de remise en service du réseau
T im e lin e
C h e c k p o in t
in T im e
RPO
O u ta g e
M in im u m
S e rv ic e
D e liv e r y
S y s te m
re p a ir
S e r v ic e
D e liv e ry
at 100%
N e w B u s in e s s
RTO
7
Y o u r R e c o v e r y O b je c t iv e s - E x a m p le
© IBM France 2016
Signification du % de disponibilité pour une application
Pourcentage de disponibilité annuelle pour une application :
8
99 %
87 heures (3 jours ½) de coupure maximum par an
99,5 %
44 heures de coupure maximum par an
2 fois moins de temps / 99%
99,9%
9 heures de coupure maximum par an
3 fois moins de temps / 99,5%
99,99%
1 heure de coupure maximum par an
99,999%
5 minutes de coupure maximum par an
© IBM France 2016
Session objectives
This session will provide an overview and recap of the range of IBM
i system availability solutions and recent enhancements
– Single-system availability technologies for addressing scheduled and
unscheduled downtime
– IBM PowerHA SystemMirror for high availability / disaster recovery through IBM
storage-based clustering
By David Painter
Senior Availability Specialist
IBM
STG Lab Services
© IBM France 2016
Availability Strategy
Balanced
Systems
Growth
Eliminate System
Outages
Reduce Frequency &
Duration of Outages
HA Clustering
Solutions
© IBM France 2016
Availability Enhancements
Scheduled downtime
Unscheduled downtime
Backups
Recovery time
High availability
solutions
PowerHA replication
technologies
Save Performance
Abnormal IPL
Online Backups
Transactions up to point of
failure
Usability/Automation
Restoring lost or corrupted data Lab Services tools
Maintenance
Enhancements by release
Single points of failure
PTFs
Processor & Memory
OS Upgrades
Power & Service Proc
Hardware / firmware
DASD
Other I/O
© IBM France 2016
Scheduled downtime: Backups
Save Performance
Performance increase with each generation of tape hardware
technologies
– Couple with multiple concurrent or parallel backups for maximum throughput
7.2 Faster IFS save times using SAV command with new
ASYNCBRING parameter
– Up to 60% faster save times in some cases (depends on directory structure,
number/size of objects, and other factors – Note: performance could degrade in some
situations)
– To enable ASYNCBRING in 6.1 or 7.1, see IBM Technote N1011242:
– http://www-01.ibm.com/support/docview.wss?uid=nas8N1011242
– See BRMS developerWorks wiki for BRMS support information:
– IBM Backup, Recovery and Media Services (BRMS) for i > Backup > Backup of
integrated file system objects > Specifying ASYNCBRING for IFS backups
– https://ibm.biz/Bd4vwD
© IBM France 2016
IBM Tape drive Roadmap
© IBM France 2016
What Happened to the PCRM?
Performance Capabilities Reference Manual – “PCRM”
Was THE reference manual for all things related to IBM i performance
considerations
– Content was carried forward but not always updated
Beginning in 2014, the PCRM only covers CPW information
– Updates for new hardware models and CPW ratings
– Older versions are still available for download
– Save/Restore Performance can still be found in the PCRM for 7.1 dated Aug 2013
Use other sources for IBM i performance information:
– The IBM i Performance FAQ  a MUST read!
(89 pages) – Updated 12 Avril 2016
http://www.ibm.com/common/ssi/cgibin/ssialias?subtype=WH&infotype=SA&appname=STGE_PO_PO_USEN&htmlfid=POW03102USEN&attachment=POW03102USEN.PDF
– Papers under the resources section on the Performance Management site
– Knowledge Center
– developerWorks
© IBM France 2016
Performance management on IBM i
http://www-03.ibm.com/systems/power/software/i/management/performance/resources.html
Save/Restore
Performance
© IBM France 2016
IBM developerWorks : IBM i
http://www.ibm.com/developerworks/ibmi/
© IBM France 2016
BRMS PRTRPTBRM *CTLGRPSTAT Command
• Excellent for:
• Monitoring / Analyzing ongoing Backup Performance
• Sizing New Tape / ProtecTIER Environments
• See BRMS developerWorks Wiki for BRMS support information
• IBM Backup, Recovery and Media Services (BRMS) for i > Backup > Save
Items > Backup control group status – PRTRPTBRM
• https://ibm.biz/BdF6rr
© IBM France 2016
Online “point in time” backups
6.1 Save-While-Active (SWA) synchronized across libraries and IFS objects
– Single checkpoint to ensure library and IFS data saved in consistent state
– STRSAVSYNC command in 6.1
Full System Copy Services Manager (FSCS) from IBM Systems Lab
Services
– Enables automated, full system backup without ending user jobs
– Supports SVC/V7000, DS8000 and XIV external storage
– See Full System Copy Services Manager section of IBM i Advanced Copy Services
developerWorks Wiki at https://ibm.biz/Bd4vwr
Save IASP mirror copy (FlashCopy or detached geographic mirror)
– For PowerHA environments
– FlashCopy (IASP Manager) from IBM Lab Services enables automatically creating “point in
time” copies of an IASP on DS8000 or SVC/V7000/V3700.
– See FlashCopy (IASP Manager) section of IBM i Advanced Copy Services developerWorks
Wiki at https://ibm.biz/Bd4vws
© IBM France 2016
FlashCopy Overview
DS8000, SVC,
V7000, V3700
Prod LPAR
IASP
*SYSBAS
FlashCopy
LPAR-2
IASP
*SYSBAS
Tape Backup
(backup)
FlashCopy is a point-in-time-copy of external storage logical volumes that can be established very quickly
and with minimal or no disruption or resource on the production LPAR
IASP based or Full System solution
FlashCopy options – full copy, no copy
Space Efficient FlashCopy volumes can reduce FlashCopy storage by 70-80%
Use with Quiesce to eliminate IASP vary off or LPAR shut down, journal for object and data integrity of
flashcopy
Automate with IASP Copy Services Manager for PowerHA on i or with Full System Copy Services
Manager" (FSCS) from IBM Systems Lab Services
Integration with BRMS
Ideal for off-line backup solutions
© IBM France 2016
IBM i Full System FlashCopy Process
1
IBM i Production
Write all memory
content to disk
3
Partition returns to
production duties
Production LPAR
Bandothèque
Managing LPAR
Sysbas
2
Flashcopy the disks
Backup LPAR
Storage Unit
IPL the target partition
4
Sysbas’
5
Backup the target
partition to tape
6
The whole process is managed by
the managing partition
Managing LPAR with IP connection to production/backup LPARs, HMC and DS8K or V7K
HMC is key to manage the full system FlashCopy process as FlashCopy cannot be
invoked from a quiesced or powered off production LPAR
© IBM France 2016
Flashcopy pour accroître la disponibilité du service.
© IBM France 2016
Backup Usability/Automation
7.1 and 7.2 BRMS enhancements
– Improved functions for managing backups, media, backup history, and recoveries
– See News section of BRMS developerWorks Wiki
http://ibmurl.hursley.ibm.com/2KIS
7.1 BRMS Enterprise Function
– Monitor backup operations for all your BRMS systems from a central site
– Provides common spot for recovery reports, dashboard for all systems, ability to get
status on a control group run... all from a central hub.
– 7.2 enhancements (not PTFed back to IBM i 7.1)
–
Auto refresh of Hub’s node status (dashboard) via new Q1ABRMENT subsystem
– PRTRPTBRM support
– Failed Control Group View to debug problems faster
– See BRMS Enterprise section of BRMS developerWorks Wiki for details
– https://ibm.biz/BdDYg5
– See BRMS Enterprise Enhancements Redpaper
– http://www.redbooks.ibm.com/redpieces/abstracts/redp4926.html
© IBM France 2016
Pour en savoir plus sur les solutions de sauvegarde…
S25 – Astech
Les différentes solutions de
sauvegarde sur IBM i.
Mercredi 11 mai – 9H00
Pascal Thenon
© IBM France 2016
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM
Backup, Recovery and Media Services (BRMS) for i
Enterprise
List of BRMS
enhancements
delivered via
quarterly PTFs!
24
IBM Navigator for i enhancements
Backup enhancements (see next page)
Recovery enhancements
Media services enhancements
BRMS network enhancements
Install enhancements
Maintenance enhancements
Miscellaneous enhancements
© IBM France 2016
Scheduled downtime:
BRMS - Backup enhancements (7.2)
Async bring (ASYNCBRING) parameter on IFS backups to improve performance
Allow setting spool file expiration dates during backups
BRMS object lists indicate whether to include or exclude objects during backups
BRMS object lists can select objects using the object attribute
Abnormal end delay time (ABNENDDLY) parm on ENDSBS to force restricted state
Queue data (QDTA) parameter to backup the contents of queue objects
Sort by (SORT) parameter to allow sorting backups by library size
Update history (UPDHST) parameter to to not update object history (for PowerHA)
Use creation date for incremental backups of spooled files
Online domino backups with new Weekly Activity types
Dynamic serial/parallel (media definition) support
ASP value * for backup operations to include all ASPs in current job’s ASP group
Allow retry of backups to Tivoli Storage Manager (TSM) when TSM failures occur
Automatically IPL if subsystems cannot be started after a restricted state backup
Allow auto-restart when Start Backup using BRM (STRBKUBRM) ends abnormally
Support media and save item expiration dates after the year 2038
Enhanced tape library selection based on resources and media
Support saving to save files located on independent storage pools (IASP)
Automatically omit system libraries QPTFOBJ1 and QPTFOBJ2 from backups
© IBM France 2016
BRMS 7.3 Enhancements
BRMS Web Client
– Improved filtering and usability
– Multi-task navigation (get where you want to go quicker)
– Improved backup list editing (sorting)
BRMS Server
– Modernization of Storage Tiering using BRMS Migration
– IFS lists supported
– SSD <
HDD support
PTF’ed back to 7.2
in Dec 2015 PTF
– IASP support
–
–
–
–
PRTRPTBRM FROMSYS support
INZBRM network checker options
CHGMEDBRM movement support of one volume
SAVBRM now supports Pattern parameter
© IBM France 2016
Storage Tiering using BRMS Migration
Previous Migration Support
ASP01
Library
Support
LIB A
USER ASP
LIB A
If LIB A isn’t used enough based
on customer choices, LIB A can
get moved down to USER ASP
or vice versa if use increases.
© IBM France 2016
Modernization of Storage Tiering using BRMS Migration
NEW Migration Support
IFS now
supported!
Library Support!
S
S
D
H
D
D
ASP01
S
S
D
H
D
D
User ASP
Can move PF/LF files within
an ASP. Between SSD (Fast)
and HDD (Slow)
S
S
D
H
D
D
IASP
NEW IASP
SUPPORT
© IBM France 2016
7.3 SAVE menu enhanced (Options 21, 22, and 23)
–
Start date prompt allows scheduling backups up to 7 days
in advance
–
Remount file systems at end of backup if chose to unmount
file systems during backup
7.2 SELECT parameter on SAVLIB/SAVOBJ
commands to refine which objects to include or omit
7.2 Spooled files can now be saved with the Save
Changed Objects (SAVCHGOBJ) command
7.2 TCP/IP configuration information automatically
saved with QUSRSYS
7.1 Removed limit that prevented saving database
files with more than 16 MB of descriptive information
– NOTE: Find all the system limit changes for any
OS version in the IBM i Knowledge Center
NOTE: Save Storage (SAVSTG) command no longer available on 7.2
© IBM France 2016
Tape Virtualization (address tape errors and tape handling issues)
– IBM i virtual tape
outstanding large file save performance
– IBM TS7600 ProtecTIER® Deduplication Family
great for remote replication
© IBM France 2016
What does ProtecTIER do?
ProtecTIER
IP Replication
IBM i
TS3500
Optional
duplication
to physical
tape
Ohio
Minimized bandwidth
since data is de-dup’d
before sending
(at local or
remote
site)
New York
IBM i
ProtecTIER
Virtual
Tapes
C
Disk
What is
DeDuplication?
B
A
B
A
C
A
B
A
C
Local Saves to
Virtual Tape with
De-dup
B
A
B
A
C
A
C
A
B
A
B
C
B
A
A
A
B
© IBM France 2016
Where does ProtecTIER fit? Generally and on IBM i
Small Servers can’t optimize a tape drive
Writing
Waiting
Waiting
Small Backups don’t fill a tape
Waiting
Virtual tape can provide
multiple virtual drives
Tapes are Hard to Manage
Virtual tape can make virtual
volumes of any size
Nice with VIOS
for IBM i
Offsite Shipments are Costly and a Bother
Virtual
tape keeps
all the
volumes
inside the
device
Virtual
tape can
transmit
them to a
remote site
Very Interesting for
IBM i Customers
© IBM France 2016
Backups: Best practices / technologies
High Speed tapes – upgrade to latest generation for maximum performance
Multiple tapes – when a single fast tape drive is not enough
– Concurrent saves and/or Parallel saves
Real time backups of active data – when users won’t give it up
– Save-While-Active (SWA)
– Saving journal receivers – complex and slow recovery, but cheap
Off-line backups from a point-in-time copy –
move it off to tape at your leisure
– Snapshots (for example, FlashCopy with DS8000, SVC, V7000, V3700)
– Logical replication read-only access of target copy
Automation – because humans cannot keep up with all of the options
– BRMS – Backup Recovery and Media Services – does it all, including FlashCopy
– IBM Systems Lab Services tools (IASP or Full System Copy Services Manager)
Tape Virtualization – address tape errors and tape handling issues
– IBM TS7600 ProtecTIER® Deduplication Family
– IBM i virtual tape
© IBM France 2016
Scheduled downtime
Backups
Recovery time
Save performance
Abnormal IPL
Online backups
Transactions up to point
of failure
Maintenance
PTFs
OS Upgrades
Hardware / firmware
Restoring lost or
corrupted data
High availability
solutions
PowerHA replication
technologies
Enhancements by
release
Lab Services tools
Single points of failure
Processor & Memory
DASD
Other I/O
© IBM France 2016
Scheduled downtime: PTFs
7.2 More immediate apply PTF opportunities
– Conditional Immediate PTFs
– Allows an immediate apply PTF which supersedes a delayed PTF to be Immediate applied if the
superseded PTF has already been applied
– Prior to 7.2, Immediate PTFs cannot supersede delayed PTFs
– Once delayed PTF created, snowball effect triggered since all future
superseding PTFs must be delayed even if the changes in the PTF could be
applied immediately
7.1/7.2 Display PTF Apply Information (DSPPTFAPYI) command
(7.1 requires PTF SI52034 included in TR8)
– Shows whether selected PTFs can be applied immediately
– PTF save files and PTF groups must exist in or be copied into *SERVICE before running command
6.1/7.1/7.2 PTF apply time improvements
– Improvements to Long Running PTF apply exit programs
– Improvements to LIC PTF apply (benefits smaller partitions/systems)
– Automatic double IPL for PTFs requiring extra IPL for installation
6.1 Networked virtual optical for OS upgrades, PTF install, or LP install
© IBM France 2016
Scheduled downtime: OS upgrades
Technology Refreshes (7.1 and beyond)
– Semi-annual technology refreshes provide new functions and I/O support
– Simpler to install on a current release and less disruptive (PTF apply vs. OS upgrade)
– Allows many years between disruptive major OS upgrades
Independent ASPs / PowerHA
– Upgrade target LPAR to new release without disruption to production
– Vary off IASP from old release, vary on IASP to new release (minimum disruption/outage)
FlashCopy
– Eliminate downtime for pre/post-upgrade backups
– Create cloned image to test upgrade process, calculate timings (repeatable over and over)
– Create cloned image for rapid back-out if upgrade process fails / takes too long
Central site distribution media (“DLO media”)
– Saves time/steps in the upgrade process
– See “Distributing software using central site distribution” topic in the Knowledge Center
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzai4/rzai4centsitedist.htm
Image catalog and network install using virtual optical storage & NFS
– Eliminates need to handle physical media during install process
– See “Preparing to upgrade or replace software with virtual optical storage using the Network File
System” topic in the Knowledge Center
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzahc/rzahcpreparingtoupgradevirtoptnfs.htm
Install time improvements with faster POWER processors
© IBM France 2016
Scheduled downtime: Hardware maintenance
Concurrent repair of fans/power supplies
Concurrent repair of PCIe adapters
Concurrent repair of disks configured for redundancy
7.1 Concurrent disk move/remove
POWER6/7 hot-add HSL-2 and 12X I/O loop adapters
POWER8 hot-pluggable optical modules for I/O drawer attachment
Concurrent system firmware updates (between releases)
7.1 TR4 Live Partition Mobility
– Migrate running workloads between systems to enable continuous availability during
planned server hardware maintenance / outages
– Combine with Power Enterprise Pools with Mobile and Elastic COD for maximum
flexibility and economic efficiency
© IBM France 2016
7.1 Concurrent disk move/remove
1
Work with Disk Configuration
Concurrent Remove of Disk Units
– Logically remove disk unit(s) without having to IPL or
take an outage (physical remove requires IPL to clean-up
Select one of the following:
hardware resources)
1. Display disk configuration
2. Add units to ASPs
3. Work with ASP threshold
- ...
- ...
10. Stop hot spare
11. Work with encryption
12. Work with removing units from configuration
2
– Does not require restricted state
– Can be paused and restarted
POWER5 and up, with 7.1
Work with Removing Units From Configuration
3
Select one of the following:
1. Display disk configuration
2. Display status of remove operation
3. Remove units from configuration
4. Pause the remove operation
5. Resume the remove operation
6. Cancel the remove operation
7. Cancel the remove operation and balance data in the ASP
4
Serial
Number
YL4RUT3ERVR7
Resource
Type Model Name
6B22 050 DD006
Capacity Status
37287 Non-configured
Size
%Used Status
195754 33.56% Unprotected
55924 40.77% Configured
37287 2.88% Removing
See section 8 in: IBM i 7.1 Technical
Overview, SG24-7858
http://www.redbooks.ibm.com/redpieces/abst
racts/sg247858.html?Open
© IBM France 2016
Live partition mobility
Move a running partition from one Power7/8
server to another with no application downtime
Reduce planned downtime by
moving workloads to another server
during system maintenance
Rebalance processing
power across servers when
and where you need it
Live Partition Mobility requires the purchase of the optional PowerVM Enterprise Edition
© IBM France 2016
Partition mobility: Active and Inactive LPARs
Active Partition Mobility
Active Partition Migration is the actual movement of a running LPAR from one
physical machine to another without disrupting the operation of the OS and
applications running in that LPAR.
Applicability
Workload consolidation (e.g. many to one)
Workload balancing (e.g. move to larger system)
Planned CEC outages for maintenance/upgrades
Impending CEC outages (e.g. hardware warning received)
Ability to move from POWER7 servers to POWER8 servers without
an outage
Inactive Partition Mobility
Inactive Partition Migration transfers a partition that is logically ‘powered off’ (not
running) from one system to another.
Suspended Partition Mobility
Suspended Partition Migration transfers a partition that is suspended from one
system to another.
© IBM France 2016
Power Enterprise Pools
Power Enterprise Pools enable you to move processor and memory
activations within a defined pool of systems, at your convenience.
New mobile activations for both processor and memory
Mobile activations can be used for systems within the same pool
• One pool type for Power E880 & POWER7+ 780 & Power 795 systems
• One pool type for Power E870 & POWER7+ 770 systems
Activations can be moved at any time by the user without contacting IBM
Movement of activations is instant, dynamic and non-disruptive
© IBM France 2016
Power Enterprise Pools
The capability to freely move core and memory activations between
servers in a pool provides a new degree of architecture and application
areas to consider:
– Rebalancing server capacity
– Mobile activations can be moved between servers to make best use of core
and memory resources. Mobile activations can also be use to temporarily
relocate resources for period end processing or full-scale performance
testing.
– Live Partition Mobility (LPM)
– When using LPM for scheduled maintenance or partition relocation, mobile
activations can be shifted from the LPM source server to the LPM target
server.
– PowerHA clusters
– Move mobile activations from the primary server to the backup server for
planned or unplanned outages
© IBM France 2016
Scheduled downtime
Backups
Recovery Time
Save Performance
Abnormal IPL
Online Backups
of failure
Maintenance
PTFs
OS Upgrades
Hardware / firmware
Restoring lost or
corrupted data
High availability
solutions
PowerHA replication
technologies
Enhancements by
release
Lab Services tools
Single Points of Failure
Processor & Memory
DASD
Other I/O
© IBM France 2016
Unscheduled Downtime: Recovery Time
IPL performance improvements
See “Current PTFs for IPL / vary on IASP steps” document for latest
fixes/enhancements for Abnormal IPL recovery time or vary on of IASPs
– http://www-01.ibm.com/support/docview.wss?uid=nas8N1020998
6.1/7.1 Spool recovery, Work Control Block Table (WCBT) cleanup, Journal
recovery, LU services start up
7.1/7.2 Access Path recovery and Journal synchronization
– Significant improvement in some environments (including IASP vary on), particularly
where large Access Paths are rebuilt unexpectedly instead of recovered from the
journal
7.2 Main Store Dump (MSD) improvements
– Storage Management Subset Directory Recovery (SRC C6004250) on systems with
very large (>4GB) permanent directories
– Smart Dump for User-Initiated MSDs and XPF-related crashes
–
–
Prior to 7.2, these were always Full Dumps requiring all main store to be dumped
Smart dumps require only a subset (around 10%) of main storage to be copied to disk which greatly reduces the time
needed for this MSD step
– New message on Copy Status screen indicates when Smart (subset) dump vs. Full
dump being copied (factor into IPL recovery time/decision making)
“Best Practices for Managing Time Needed for Main Storage Dump (MSD)” Technote
– Latest recommendations, enhancements, and PTFs to help manage and reduce time
required for MSD
http://www-01.ibm.com/support/docview.wss?uid=nas8N1020270
© IBM France 2016
Main Store Dump Smart-Dump Indicator
Prior to 7.1, when copying a Main Store Dump to disk, SRC C6xx4404 is displayed
where xx is the percent completed for copying the dump
In 7.1 (and 6.1.1 with PTF MF58168), the SRC is later changed to indicate what type of
dump is being copied (xx still displays the percent complete):
Full dump:
SRC C6xx1404: Copying a compressed full dump
SRC C6xx2404: Copying a uncompressed full dump
Subset dump ("smart dump"):  Much shorter/faster than a full dump !
SRC C6xx3404: Copying a uncompressed subset dump
SRC C6xx4404: Copying a compressed subset dump
In 7.2, a message is displayed on the MSD copy status screen while the copy is in
progress indicating the type of dump being copied and the percent complete
– To see this information, press Enter on the MSD summary screen ("Main Storage Dump
Occurred" screen), select "Work with current main storage dump (MSD)" on the MSD
Manager screen, and then press F11=Copy status
© IBM France 2016
Monitoring progress during a MSD
With IBM i 7.2 or with the PTFs applied, the IPL satus screen will be the first
screen that will be displayed after a MSD is underway :
© IBM France 2016
Unscheduled Downtime: Recovery Time
7.1 TR4 Remote Restart (sometimes called “Dead Partition Mobility”)
– Recover and reboot partition on another server after an unplanned
server failure
– Similar prerequisites as for LPM (VIOS, external storage, etc.)
– Combine with Power Enterprise Pools for maximum flexibility/efficiency
– Requires either
– IBM Systems Director VMControl
– or –
– HMC V8R8.1.0
– Includes new command to initiate a Remote Restart operation
(manually or automate using CLI/APIs)
Simplified Remote Restart  no need for reserved storage
– Requires HMC V8R8.2.0, VIOS 2.2.3.4, recent firmware
© IBM France 2016
Unscheduled downtime: Recovery time
Restore Enhancements
7.3 Restore authorization list links for objects in QSYS
– Automatically recover links during disaster recovery to reduce recovery time
7.2 Defer restore and journaling of dependent objects
– Also available as 7.1 PTF SI50939
http://www-912.ibm.com/systems/electronic/support/a_dir/as4ptf.nsf/ALLPTFS/SI50939
7.2 Option to not start journaling for restored objects
– New STRJRN parameter on restore command
7.1 New ALWOBJDIF(*COMPATIBLE) value on RSTLIB/RSTOBJ commands
– Essentially behaves like ALWOBJDIF(*ALL) in combination with
ALWOBJDIF(*FILE) for database files (i.e, a single value that does what most
people want to happen)
7.1 Fast Restore of Single Object
– 7.3 Objects can now be located much more quickly with fewer tape operations
– Also available as 7.2 PTF MF60473
6.1 Restore logical and physical files in different libraries in any order
© IBM France 2016
7.2 Defer restore and journaling of dependent objects
Previously, restoring journaled objects from multiple libraries or from a library other
than the library of the dependent journal was difficult to manage
– If journaled object was restored before library of the journal, object was not journaled
– After journal was restored, must manually start journaling for each restored object
With deferred journaling, journaling of objects during restore can be deferred when
there is a dependency on a journal in a library that does not yet exist
– Journal information is cached and used to start journaling after journal becomes available
– Eliminates manual effort restart journaling
Defer ID (DFRID) parameter on Restore Library (RSTLIB) or Restore Object (RSTOBJ)
– Provides association between deferred journaling information and the dependent journal
– When related files/journals are available, use Restore Deferred Objects (RSTDFROBJ) command
with DFRID to complete restore and start journaling for the dependent objects
– If you restore the related files with the same defer ID, the system automatically attempts to complete
the restore of the deferred files (don’t need to use RSTDFROBJ in this case)
System can automatically handle dependent objects restored in wrong sequence
– User must have save system (*SAVSYS) special authority and use RSTLIB command with
*NONSYS, *ALLUSR, or *IBM values for Saved Library (SAVLIB) parameter and *DFT for DFRID
parameter
– Automatically performs RSTDFROBJ operation after the libraries are restored
– For other restore operations, you must specify a defer ID to manage dependent objects
© IBM France 2016
7.1 Fast restore of single object
Save operations track position (physical location on tape) of each object
– New field returned for each object in Save OUTFILE or OUTPUT
– You must retain this positioning information for use during restore
Restore POSITION parameter
– RSTLIB RSTOBJ and RST commands and APIs
– POSITION(*START) is default and gives existing behavior
– POSITION (hexadecimal value) allows you to pass the position for a single
object to be restored
– Requires that sequence number SEQNBR also be specified
Also supported for parallel restores
Very significant performance improvements can result
– For example: Restoring last object from 1.1 million IFS object save went from
about 22 minutes to less than 3 minutes.
In 7.3, objects can now be located much quicker with fewer tape
operations
– Also available as 7.2 PTF MF60473
Backup Recovery Media Service (BRMS) uses this new support
© IBM France 2016
Unscheduled downtime: Recovery time
Journal management enhancements (since 6.1)
Journal libraries and automatically journal new objects in the library
– 7.1 Object name filtering for automatic journaling (select/omit objects based on
name)
User can end journaling and then start journaling a file without closing file
STRJRNxx/ENDJRNxx commands to start or end journaling all objects in
a library
DSPRCYAP/EDTRCYAP screens show which access paths are eligible
for SMAPP protection but are not currently being protected
User control over frequency of forcing changed objects to disk (journal
recovery count)
– Choose faster runtime processing vs. faster IPL/vary on recovery after abnormal
shutdown
See “Journal management > What's new” topic in the Knowledge Center
– http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaki/rzakiwhatsnew.htm
© IBM France 2016
Remote journal enhancements
7.2 Remote journal over secure sockets (SSL) support
7.1 Automatic restart of remote journaling if ended due to a recoverable
comm error
7.1 Ability from source side to view number of retransmissions occurring
for a remote journal connection
– Measurements of how far behind source system is at sending data to target
– 6.1 included measurements of how far behind target system is at receiving data from source)
7.1 Filtering and not sending journal entries that are not absolutely
needed to the target
7.1 Improved WAN performance via larger buffer size (greater of 256KB or
TCP send buffer size on source or TCP receive buffer size on target)
– Also available via PTFs v5r4m0 MF46358, v5r4m5 MF46359, v6r1m0 MF46360
6.1 Use of data port services with up to 4 comm lines for greater
resiliency
6.1 Validity checking to verify data received by target matches data sent
from source
© IBM France 2016
7.1 Journal disk arm selection
Starting in 7.1, journal receivers may be spread across all disk arms in
disk pool
– Journaling no longer directs writes to specific disk arms
Disk selection process was put in place years ago when greater
disparity between disk speeds and no IOA write cache
– Selecting specific disks allowed parallel disk ops & greater journal throughput
– Potential for disk usage to be skewed resulting in real or perceived performance
problems/calls
Tests of this change in multiple hardware environments with different
workloads showed no difference in performance
Changes in journal behavior
– 10 is no longer a magic number of disks for journal receivers; data goes wherever
Storage Management puts it
– No minimum nor maximum number of disk units for receivers
– Journal receiver size threshold no longer affects the number of disks across which
receiver is spread
NOTE: The higher the journal receiver threshold value, the more parallel I/O requests will be
allowed. Allowing more parallel I/O requests may improve performance
© IBM France 2016
Scheduled downtime
Backups
Recovery Time
Save Performance
Abnormal IPL
Online Backups
of failure
Maintenance
PTFs
OS Upgrades
Hardware / firmware
Restoring lost or
corrupted data
High availability
solutions
PowerHA replication
technologies
Enhancements by
release
Lab Services tools
Processor & Memory
DASD
Other I/O
© IBM France 2016
System Hardware RAS Strategy
First Failure Data Capture
Reliability
Availability
Serviceability
Quality
of Parts
Recover
Hot Repair
Quantity
of Parts
Spare
Light Path
Diagnostics
Design and
Testing
De-allocate
Color Coding
Thermal
Control
Contain
Errors
LPAR
Mobility
© IBM France 2016
Unscheduled downtime: Single points of failure
Processor & Memory
Instruction Retry (POWER6)
Alternate processor recovery (POWER6)
Active Memory Mirroring for Hypervisor (POWER7 795/780/770)
Dynamic Predictive DIMM deallocation and substitution with spare/COD
memory (POWER8)
See “POWER8 Systems RAS: Introduction to Power Systems Reliability,
Availability, and Serviceability” whitepaper
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=SA&subtype=WH&htmlfid=POW03133USEN
Find POWER8 Technical Overviews at IBM Power Systems Redbooks
portal
http://www.redbooks.ibm.com/portals/power
© IBM France 2016
RAS and other features
Power
Power
S812L S822L S822
Power *
S814 S824
Power
S824L
Power *
E870 E880
Redundant / Hot Swap Fans & Blowers
Std
Std
Std
Std
Std
Hot Swap Disk/SSD Bays
Std
Std
Std
Std
N/A
Hot Swap DVD Bay
Std
Std
Std
Std
Std
Hot Swap PCIe Adapters
Std #
Std
Std
N/A
Std
Concurrent Firmware Update
Std #
Std
Std
N/A
Std
Redundant / Hot Swap Power Supplies
Std
Std
Std
Std
Std
Dual disk controllers (split backplane for AIX, IBM i, Linux)
Opt
Opt
Opt
N/A
N/A
Processor Instruction Retry
Std
Std
Std
Std
Std
Alternate Processor Recovery
Std
Std
Std
N/A
Std
Storage Keys (AIX only)
N/A
Std
Std
N/A
Std
Dynamic Processor Sparing
Std
Std
Std
Std
Std
PowerVM Live Partition Mobility / Live Application Mobility
Opt
Opt
Opt
N/A
Opt
PowerVM Active Memory™ Sharing
Opt
Opt
Opt
N/A
Std
Dual VIOS
Opt #
Opt
Opt
N/A
Opt
Active Memory Expansion for AIX
N/A
Opt
Opt
N/A
Opt
Active Memory Mirroring for Hypervisor
N/A
N/A
N/A
N/A
Std
Chipkill Memory with Dynamic Bit Steering
Std
Std
Std
Std
Std
PowerVM Management ( IVM / HMC )
I/H #
I/H
I/H
N/A
H
Redundant Service Processors
N/A
N/A
N/A
N/A
Std
Dynamic Service Processor Failover
N/A
N/A
N/A
N/A
Std
Redundant System Clocks
N/A
N/A
N/A
N/A
Std
Dynamic System Clock Failover
N/A
N/A
N/A
N/A
Std
Power Systems Enterprise Pools
N/A
N/A
N/A
N/A
©
2014 International
Business Machines Corporation
Power
IFL
# -- Not available for PowerKVM™ environment
-
N/A
N/A
-
Opt
© IBM France 2016
Opt
Unscheduled downtime: Single points of failure
Storage and I/O (since 6.1)
Multipath disk units
–
7.1 Display the level of protection for multipath disk units
Redundant VIOS partitions
Hot spare for RAID
Hot spare for Mirroring
Dual SAS RAID adapter support
– 7.1 Dual SAS RAID adapter with cache and no batteries (uses
supercapacitor technology instead of batteries)
7.1 Ethernet Link Aggregation (EtherChannel)
© IBM France 2016
Scheduled downtime
Backups
Recovery Time
Save Performance
Abnormal IPL
Online Backups
of failure
Maintenance
PTFs
OS Upgrades
Hardware / firmware
Restoring lost or
corrupted data
High availability
solutions
PowerHA replication
technologies
Enhancements by
release
Lab Services tools
Processor & Memory
DASD
Other I/O
© IBM France 2016
IBM i Différentes options de replication.
Logical
Replication
Application
FULL Replication
Replication stockage
externe
Replication stockage
externe
Application
IBM i
IBM i
Application
Application
IBM i
IBM i
Asynchrone
Journal-based replication over TCP/IP
Indépendance du sous-système de stockage
Synchrone ou Asynchrone
Réplication stockage
Sous-système de stockage externe
(DS8000, SVC* , V7000)
Metro Mirror
IBM External
Storage
OS-based
replication
HABP Solutions
IBM External
Storage
Global Mirror
Application
Cluster IBM i
IBM i-based replication over TCP/IP
Indépendance du sous-système de
stockage
Application
Geographic
IBM i
Mirroring
IBM i
iASP
iASP
Application
Application
IBM i
iASP required
Cluster IBM i
Réplication stockage
Sous-système de stockage externe
(DS8000, SVC* , V7000)
IBM i
Metro Mirror
iASP
IBM External
Storage
60
Global Mirror
iASP
iASP required
IBM External
Storage
*SCV
– SAN Volume Controller ou Spectrum Virtualize
© IBM France 2016
Solutions de réplication disponibles sur IBM i.
Réplication assurée au niveau applicatif (base de données), s’appuyant essentiellement sur la
journalisation (ou logging):
– Solutions logicielles de réplication, toutes basées sur solutions éditeurs.
– Pour implémenter une solution de haute disponibilité (HA) ou DR.
Réplication ‘’Hardware’’ assurée par le système d’exploitation IBM i encore appelée ‘’Geographic
Mirroring’’:
– Solution sous contrôle de PowerHA for i s’appuyant sur la fonction Cluster IBM i.
Réplication ‘’Hardware’’ assurée par un sous-système de stockage disque IBM :
– Solution sous contrôle de PowerHA for i s’appuyant sur la fonction Cluster IBM i.
– Redondance du stockage externe avec la fonction HyperSwap (synchrone) et PowerHA for i (DS8K).
Réplication « Hardware » assurée par le sous-système de stockage disque IBM :
–
–
–
–
61
Solution sous le contrôle des fonctions de réplication (Copy Services) de la solution SAN IBM.
Pour implémenter une solution de reprise après sinistre (PRA ou DR).
Redondance du stockage externe avec la fonction HyperSwap (synchrone).
FULL réplication avec sous-système de stockage externe.
© IBM France 2016
Réplication logicielle – Solutions éditeur.
Serveur
Stockage Serveur
Stockage
Réplication Logique
Remote journal objects
S47 – ACMI
La continuité totale sur
Power i « as a Service »
Mercredi 11 mai - 15h15
Benoit Massiet Du Biest
Audit journal objects
Le basculement requiert que les données de backup soient appliquées et que les objets soient synchronisés.
1
2
LSU
1
5
2
S39 – Traders
Application/Database I/O
4
Objets journalisés:
1. Mise à jour sur DB locale.
2. Transfert sur site à distance.
3. Accusé de réception envoyé par site distant.
4. Réception en local
5. Données appliquées en asynchrone sur serveur
de secours.
3
3
SYSBAS
Objets non journalisés:
1. Modification de l’objet non-DB en local.
2. Capture de ce changement dans le journal
d’audit.
3. Envoi vers cible
4. Application asynchrone sur cible.
SYSBAS
Une production non-stop
24/24 et 7/7 sur IBM i,
c'est possible !
Thierry Roux
Veiller à faire un changement
régulier de rôle (serveur CBU).
© IBM France 2016
PowerHA SystemMirror for i
An IBM delivered, end-to-end solution for HA, DR and on-line backups
End-to-End Solution
PowerHA SystemMirror for i
Lab
Services
ACS
IBM i Clusters and Cluster Resource Services
HA Switchable Resources - XSM
DSCLI DS Command Line Interface
Switched
IASPs
Geographic
Mirroring
Geographic
Mirroring
• IOA or
Tower
IASP
switch
• Synch
transmit
copy
• Asynch
transmit
copy
(7.1)
OS Resiliency Technology
(Guideline: Less than 2 TB)
63
Metro
Mirror
Global
Mirror
• Sync
copy
• DS8000
• HyperSwap
• SVC V7000
• Async
copy
• DS8000
• SVC
V7000
V9000
Flash
Copy
• Point in time
copy
• DS8000
• SVC V7000
V9000
LUN Level
Switching
• IASP
Storage
Switch
• DS8000
• V7000
V9000
Storage Resiliency Technology
(with IBM Storage)
© IBM France 2016
IBM PowerHA SystemMirror for i
First released in 2008 (IBM i 6.1 release)
Hardware based replication solutions (disk level)
Supports both:
– IBM i replication – any storage
– External storage replication – DS8000, SVC, Storwize models
Integrated – Can manage IBM i and external storage HA from one IBM i
GUI or command line
Reliable – Using IBM replication technologies
Efficient – Deeply integrated with lower levels of the OS
Automated – Minimal IT management required
Versatile – Solutions for any storage, any distance
© IBM France 2016
PowerHA IASP replication technologies
External Storage Replication
1 site
Shared Storage
IBM i Replication
PROD
External
Storage
PROD
HA
LUN level switching
HA
PROD
Network
Synchronous Geographic Mirroring
1 site
Replication
External
Storage
HA
External
Storage
Network
Metro Mirror
PROD
PROD
HA/DR
Network
2 site
Replication
External
Storage
HA/DR
Network
External
Storage
Global Mirror
Asynchronous Geographic Mirroring
PROD
2 site
HA + DR
HA
DR
External
Storage
External
Storage
Network
LUN switch + Global Mirror
3 site
Replication
(DS8K only)
65
PROD
HA
DR
External
Storage
Network
Metro Global Mirror
© IBM France 2016
PowerHA with Geomirroring
PowerHA with geographic mirroring is popular with our smaller IT shops
– Inexpensive compared to logical replication solutions, its easy to use and requires little
day to day monitoring and maintenance.
– Typically used by shops with under 2 Tbytes and on internal disk
– After an unplanned outage the target data is replicated back to the source therefore the
larger the IASP the longer the resync time
– Doing a tape backup off of the target works great, Quiesce the IASP on the current
production copy system (see speaker notes) if you want to get a “clean transaction
boundary. If you choose to do the quiesce (recommended), do it during a quite time.
Geomirroring is IBM i mirroring of the data writes to the IASP source and target over IP
– Referred to as host based replication (as opposed to storage based replication)
– IBM i storage management sends the memory pages to both the remote and local
server either synchronously or asynchronously
– Synchronous distance is typically under 30 or 40 KM but distance is driven by
application response time requirements
– Bandwidth and quality of service are both important. When we’ve seen issues they
usually come down to network quality.
© IBM France 2016
PowerHA – Geomirroring – HA/DR clustering
Admin Domain
Sysbas
Sysbas
production partition
target partition
IASP
IASP
geomirror
DB2, IFS
DB2, IFS
PowerHA geomirror cluster (typically with internal disk and < 4 Tbytes )
Complete HA/DR coverage for all outage types (hardware, middleware, operator error)
Off line back-up followed by source side /target side tracking change resynchronization
Both bandwidth and network quality are important.
Synchronous mode up to 40 KM, production and target always identical
Asynchronous mode unlimited distance, production and target ordered and consistent
© IBM France 2016
Geomirroring – IBM i hosting (remote VM restart for DR)
i host partition
Applications
client
partition
Admin domain*
IASP
IASP
NWSSTG
IBM i
hosted
partition
i host partition
NWSSTG
geomirror
IBM i
hosted
partition
client
partition
* Admin Domain on host is optional
Non-cluster PowerHA configuration, full system replication, this is disaster recovery setup, this is not a HA solution
IBM client placed into a network storage space which is placed into an IASP
Guest and host partition must be shut down before remote host and client can be restarted
Limitation: no heart beating, can’t do concurrent OS upgrades, is more resource intensive than a PowerHA cluster
Note that everything is being replicated so network bandwidth and quality is critical
Any roll over or failover requires an abnormal IPL of target
© IBM France 2016
two site traditional cluster with Metro Mirror
Application
Metro Mirror
Traditional two-site Metro Mirror cluster configuration
Synchronous replication limits effective distance due to lag
IASP replication synchronous to application state (real-time identical copies)
Server outage management via a PowerHA cluster operation
Storage outage management via a PowerHA cluster operation
© IBM France 2016
storage based disaster recovery configuration
Application
Global Mirror
PowerHA Enterprise Edition with Global Mirror replication
Unlimited distance
Typically used for disaster recovery
© IBM France 2016
Two site PowerHA cluster with tape backup
PowerHA Metro Mirror Cluster (or Global Mirror)
TS3500
IASP
Metro Mirror
Global Mirror
IASP
BRMS
IASP
Site A
Site B
V3700, V5000,V7000, V9000, SVC, DS8000
HA/DR with Metro Mirror (or Global Mirror, or Switchable LUNs or all of them combined)
Backup window elimination save automation with FlashCopy and BRMS
© IBM France 2016
PowerHA Express Edition - Full system HyperSwap
Support for DS8000 HyperSwap in full system replication environments
HyperSwap by itself is a hardware availability solution
–
–
–
–
‘Zero’ downtime switch for storage planned and unplanned outages
Single partition solution, although can be combined with partition mobility
Not a disaster recovery solution
No protection against software planned or unplanned outages
Once configured, HyperSwap switch will occur automatically in the case of a DS8K failure,
or can be triggered manually before a planned outage
Prod
Prod
SYSBAS
Metro
Mirror
SYSBAS
LPM
SYSBAS
Metro
Mirror
SYSBAS
© IBM France 2016
IBM i Full System Copy with HyperSwap
One Node HyperSwap
– Configure a single IBM i LPAR for HyperSwap
– No need for compute node on the second site
– Full LPAR (non IASP based)
IBM i 7.2 – Power HA Express Edition
The IBM i environment can be provisioned natively or
through VIOS
Secondary DS8K
Site 2
Primary DS8K
Site 1
Provides ability to switch access from production to
remote DS8000
– Automatic or manually triggered
HA solution: planned storage outages
Legend:
Active Path
DS8000 or SVC (TR3)).
Passive Path
© IBM France 2016
Enterprise edition HyperSwap solution for high availability
Application
Metro Mirror
HyperSwap
Site one
Site two
Two-site DS8K HyperSwap PowerHA Enterprise Edition cluster configuration
Server outage management via a PowerHA cluster operation
Storage outage management via a HyperSwap switch
© IBM France 2016
Enterprise edition HyperSwap cluster “under the hood”
*SYSBAS
Metro Mirror
*SYSBAS
IASP
MetroMirror
IASP
Virtual IASP
*SYSBAS
MetroMirror
DS8000
0
*SYSBAS
DS8000
HyperSwap
HyperSwap has the effect of making the replicated pair of IASPs appear as a single virtual IASP
–
HyperSwap switches the source and target IASP and SYSBAS in the event of a storage outage
–
The source IASP is mirrored to the target IASP via Metro Mirror
–
The source and target SYSBAS data are mirrored via Metro Mirror
In the event a storage outage event, the source system switches to the mirrored IASP and the mirrored SYSBAS
In the event of a production server outage, PowerHA conducts a failover to the target production server, (the virtual IASP is
switched to target) Metro Mirror will reverse direction of replication and production resumes on the secondary power server
If VIOS is deployed, LPM can be used for firmware updates, load balancing etc
DS8800 and above (TPC-R not utilized)
© IBM France 2016
PowerHA Enterprise Edition - IASP based HyperSwap
Prod
DS-A
*SYSBAS
IASP
*SYSBAS
DS-B
Metro
Mirror
Metro
Mirror
Metro
Mirror
*SYSBAS
HA
IASP
*SYSBAS
• IASP replication plus HyperSwap
• Live partition mobility for ‘zero’ downtime planned firmware, POWER outages
• HyperSwap for ‘zero’ downtime storage planned and unplanned outages
• PowerHA vary off/on of IASP for OS planned outage, disaster recovery
Note : Available via 7.2 PowerHA PTFs with both release 7.2 and 7.3 of IBM i.
© IBM France 2016
PowerHA HyperSwap clustering technology
Applications halts while cluster switches
– Storage resumes after cluster switch
Applications continue to use the IASP
– Storage switched via SLIC
Application
Application
PowerHA Enterprise Edition
PowerHA Enterprise Edition
IASP
IASP 1
IASP 2
SLIC
Metro Mirror
Metro Mirror
Primary DS8K
Secondary DS8K
Primary DS8K
Traditional Metro Mirror Cluster
77
Secondary DS8K
HyperSwap Cluster
© IBM France 2016
Three site
MGM cluster with HyperSwap
Application
Metro Mirror
HyperSwap
Site one
Global Mirror
Site two
Site three
Metro Global Mirror (MGM) cluster with Hyper Swap
IBM PowerHA System Mirror for i Planning Insights:
IBM plans to introduce the capability to add a third system connected to the PowerHA for i HyperSwap pair
via either a Metro Mirror or Global Mirror link.
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole
discretion. Information regarding potential future products is intended to outline our general product direction and it should not be
relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment,
promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be
incorporated into any contract. The development, release, and timing of any future features or functionality described for our
products remains at our sole discretion.
© IBM France 2016
PowerHA FSR (Full System Replication)
FSR automates full system replication
It’s relatively simple to migrate to from internal disk and logical replication
Functionality
PowerHA
Integrated automation/management from IBM i
FSR
*
IBM i based recovery for Data/Commitment control etc
FlashCopy saves for scheduled outage reduction (full
system flash requires an IPL to save the data to tape)
RTO
*
minutes
hour
Minimize bandwidth requirements
Minimize performance overhead of sync replication ( not
replicating temporary I/O, savf’s etc )
Provide capability to do PTF, operating system, and
software packages concurrent to production
Active host at HA/DR ( hardware error reporting )
Outage management requires IPL processing
No IASP migration required
• Ensure that the solution meets the SLA of the customer
* Via Lab Services tools
IPL
• Due the proper sizing's for performance and bandwidth
• Use as a first step in the transition to clustering
© IBM France 2016
Comparaison Réplication IBM i Full System avec replication
IASP (PowerHA for i).
Partition Primaire
Partition Backup hors service
- Tous les volumes (LUNs) sont répliqués sur le stockage
du site de secours.
- La VM de secours n’est pas active.
- Les LUNS répliquées sont actives mais non accessibles.
- Une inversion des rôles suppose un arrêt préalable de la
VM primaire.
- Un failover suppose un IPL anormal
Partition Primaire
-
Partition Backup active
Seuls les données/objets de l’IASP sont répliqués.
La VM de Backup est active (SYSBAS).
L’IASP répliqué est actif mais non accessible.
Le switch lié à un arrêt planifié/non planifié se traduit par
une commande simple pour lancer un vary on de l’IASP.
© IBM France 2016
SVC HyperSwap versus PowerHA replication
- La VM IBM i reste active lors d’une défaillance d’un soussystème de stockage (redondance de stockage).
- Full système copie: pas d’IASP sur SVC/Storwize.
- Une défaillance du serveur suppose un IPL anormal depuis
le serveur à distance.
- RPO: excellent (synchrone)
- RTO : temps d’un IPL anormal.
- Arrêt de la VM IBM i lors d’un switch ou d’un failover.
- SYSBAS et storage actif avec PowerHA for I
- L’IASP remote est en relation synchrone mais non actif sur
le SYSBAS remote.
- Pour que l’application soit active sur le site remote, vary on
de l’IASP. Demande quelques minutes (fonction éventuelle
des applications de postes de journaux).
- RPO: excellent (Metro Mirror)
- RTO : une dizaine de minutes ou plus selon contexte.
© IBM France 2016
A PowerHA Technology for Every Storage Type
Internal
SAS/SSD
DS8000
SVC
Storwize
V840
V9000
XIV
DS5000
Other
Storage
Geographic
Mirroring
Metro Mirror
Global Mirror
Metro Global
Mirror
LUN switching
FlashCopy
HyperSwap
© IBM France 2016
A PowerHA Technology for Every Outage Type
Planned
/Unplanned
Partition
Outages
Planned
/Unplanned
Server
Outages
Planned
/Unplanned
Storage
Outages
Site
Outage
Offline
Backups
>2 copies
of realtime data
Synch Geo
Mirroring
Asynch Geo
Mirroring
Metro Mirror
Global Mirror
Metro Global
Mirror
LUN switching
Flashcopy
HyperSwap
© IBM France 2016
Pour en savoir plus sur PowerHA for i…
S23 – IBM
Principes et mise en œuvre
des IASPs. .
Bertrand Guibert
S31 – IBM
Haute disponibilité IBM i avec
la solution PowerHA for i.
Bertrand Guibert
© IBM France 2016
PowerHA Tools for IBM i
Complement and extend PowerHA and IBM Storage capabilities for
HA/DR
Helps reduce business risk and improve resiliency for critical
applications
Simplifies set up and automation of HA/DR and backup solutions
Reduces cost of maintaining and regular testing of an HA/DR
environment
Facilitates flexible deployment options for single or multi-site
protection
Assures consistent deployment using best practices and
experienced consultants
PowerHA Tools for IBM i is a service offering
from IBM Systems Lab Services
© IBM France 2016
PowerHA - A solution for everyone
Prod
IASP
Prod
HA
Geographic Mirroring
IASP
Prod
PowerHA for i
(automation & management)
Prod
Main Site
(HA)
HA
ACS
Disaster Recovery
Site
DR1
(additional management)
DS8000
DS8000
IASP
Prod
IASP
Prod
DS8000
TPC-R
Backup
or Test
IASP
Prod
Flash
Copy
Metro
Mirror
Global Mirroring
D
Copy
* TPC-R = Tivoli Productivity Center - Replication
© IBM France 2016
Session summary Cluster PowerHA for i
Highly automated solutions for high availability and disaster recovery
HA/DR solutions based on IBM storage or on internal disk solution
Provides automation for ease of use.
Implemented in IBM i, SLIC, and storage management.
FlashCopy enables off line tape backup
Designed for regular role swap operations and automated failovers.
Developed and supported by IBM.
Several ways to save money: CBU, CBU for PowerHA, Enterprise Pools
Ultra low cost modern HA/DR solutions for small customer shops
Lab Services brings expertise and added value.
Resources ..new redbooks, the wiki, join the PowerHA on i Linkedin group
© IBM France 2016
Additional resources
IBM i 6.1 and 7.1 Technical Overviews
– http://www-304.ibm.com/systems/support/i/library/techoverviews/
IBM i 7.2 wiki
– https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20
Technology%20Updates/page/IBM%20i%207.2%20-%20Base%20Enhancements
“What's new” topic in the Knowledge Center
– http://www01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahg/rzahgicoverview.htm
© IBM France 2016
PowerHA Resources
IBM PowerHA web site
– http://www-03.ibm.com/systems/power/software/availability
PowerHA Wiki
– www.ibm.com/developerworks/ibmi/ha/
Lab Services
– http://www-03.ibm.com/systems/services/labservices
Redbooks at www.redbooks.ibm.com
– Preparing for IBM PowerHA SystemMirror for IBM i- SG24-8400-00 (Feb 2016)
– IBM PowerHA SystemMirror for IBM i: Using DS8000 - SG24-8403-00 (Feb 2016)
– IBM PowerHA SystemMirror for IBM i: Using IBM Storwize - SG24-8402-00 (Feb
2016)
– IBM PowerHA SystemMirror for IBM i: Using Geographic Mirroring - SG24-8401-00
(Feb 2016)
– IBM I 6.1 Independent ASPs - SG24-7811-00
© IBM France 2016
IBM i Availability Update
Thank you to
Jenny Dervin
IBM PowerHA SystemMirror for i Architect
Bob Gintowt
IBM i Availability Technology Leader
&
IBM Systems Lab Services Consultant
For the material presented here
© IBM France 2016
Special notices
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 generallyavailable 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
© IBM France 2016
Special notices (cont.)
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
© IBM France 2016

backups

Transcription

Documents pareils

Greenford Green Business Park, Green Park Way, Greenford

Vincent Raucroix | Paperjam Guide

English CV - philippeMathieu.fr

IBM announces winners of shared university research awards

Gilles Entringer – Software Engineer

Developing COBOL with IBM Rational Developer

Support Utilisateurs Lotus Notes 8

Beyond converged networks: driving business value through