DB2 z/OS Cloning - SEGUS · PDF fileDB2 z/OS Cloning – What’s new and ......
Transcript of DB2 z/OS Cloning - SEGUS · PDF fileDB2 z/OS Cloning – What’s new and ......
DB2 z/OS Cloning – What’s new and faster?
Ulf Heinrich
SEGUS Inc
Session Code: A12
Thursday, May 5th, 2011 from 2:45 PM to 3:45 PM | Platform: DB2 z/OS
Agenda/Content to be addressed
Cloning basics:
• What type of cloning is the right choice for a given requirement?
• What are the gotchas and where are the shortcuts?
• What to take care of – beyond DB2?
HSC key benefits:
• What are the benefits using ICE?
• How can I exploit instant copy technology, like Flashcopy?
• DB2 cross-version cloning
Agenda/Content to be addressed
HSC in-depth:
• XML scenario definition – the sky is the limit!
• Naming conversion – how do you want to be called today?
• The path to DB2 Data Sharing – how many members do you need?
Tips and Tricks:
• Cloning costs considerations
• Do’s and don’t’s
Real world example:
• Customer experiences
To Clone or not to Clone?
Cloning is used for different reasons:
• Duplication of subsystems
• For (DR) Test and Quality Assurance (QA)
• For Backup
• For new Subsystem creation
• For Audit, (Compliance) Reporting and Data Mining
• Demo and training
• Merge/Duplication of systems/data
• Consolidation of Systems (Mergers & Acquisitions)
• Separation of test data, applications or business units
• Refresh of an entire system or parts of it
To Clone or not to Clone?
Advantages of cloning for:
• DR tests, QA, development
No effects on the real production system/data
• New subsystem creation
New system w/o starting from scratch reduces set up efforts
• Audit, Reporting, Data Mining
Shifts workload from production to the clone
Allows what if and point in time access to the data
• Merge/Duplication of systems/data
Reduces administration overhead and increase flexibility
To Clone or not to Clone?
How to achieve those benefits?
• Duplication of subsystems
• For (DR) Test and Quality Assurance (QA)
• For Backup
• For new Subsystem creation
• For Audit, Reporting and Data Mining
• Demo and training
The various ways/flavors of Cloning
Duplication of Subsystems
SOURCE TARGET
The various ways of Cloning
Duplication of Subsystems:
• Details about Source and Target
• Scope of Cloning
• Required Steps
• Gotchas to watch out for
Duplication of Subsystems
Details about Source and Target:
• All data of an entire system is duplicated
• If both, source and target are one and the same OS and database type (e.g.
DB2 z/OS DB2 z/OS)
Homogeneous System Copy (aka. HSC)
• BTW:
• If the target is different (e.g. DB2 LUW DB2 z/OS)
Heterogeneous System Copy (not addressed today)
Duplication of Subsystems
Scope of Cloning:
• We are talking about database cloning. This usually doesn’t include the
subsystem /data sharing group setup, like
• z/OS subsystem definition
• DB2 address spaces set up
• RACF rules
• SMS storage group/class set up
• WLM definitions
• Coupling Facility structures
• …
You may want to talk to your systems/operations colleagues.
Duplication of Subsystems
Scope of Cloning
Note:
DSNZPARM, DSNHDECP, BSDS, LOGs must
be considered, but not cloned. Use them as a
basis.
Optional:
Including DB2 Load Libraries
allows cross-version cloning
* Working on the volume level requires inclusion of ICF catalogs
Application
Indexspaces
Scope of Cloning
DSNDB01
DSNDB06
DSNDB04
Application
Tablespaces
ICF*
Catalogs
Load
Libraries
Active
LOGs
Archive
LOGs BSDSs
ICF*
Catalogs
The various ways of Cloning
Duplication of Subsystems
Required Steps:
• Clone your source data
• Dump via ADRDSSU
• Split Mirror systems and break the mirror
• FLASH Copy / Disk dump and then Restore
• Any other method…
• Stop the target system
• Restore the source data
• Rename (if naming should be different and/or target isn’t isolated from source)
• Adjust LOGs, BSDSs, DSNZPARM, DSNHDECP
• Start target
• Adjust DB2, like old naming (DB2 9 introduces NEWCAT)
Duplication of Subsystems
Gotchas to watch out for:
• Don’t burn time and resources
• If you have the appropriate storage features, use them!
• Instant copies (like Flashcopy) can clone your TB-sized source system
in a fraction of time
• Instant copies (like Flashcopy) don’t burn CPU
• Backup System assures full DB2 interaction
• Data consistency without downtime (QUIESCE)
Duplication of Subsystems
Gotchas to watch out for:
• Assure a proper DFSMS definition if you want to exploit instant copy
Duplication of Subsystems
Gotchas to watch out for:
• Be careful with the RACF definitions
• If the target can access the source you can
end up with corrupted source data!
• Changing the DB2 subsystem type (non data sharing/data sharing) requires
additional steps
• Be very careful going to less members!
• Cross version cloning requires to include the DB2 load libraries and changes
the DB2 version of the target
Duplication of Subsystems
Bottom Line:
• Cloning DB2 systems isn’t rocket science, but a complex and error-prone
process.
• Familiarize yourself with these procedures and define an easy to use step by
step guide.
Tools that supervise, manage and optimize cloning lead to:
• More flexibility
• Higher degree of automation
• Exploitation of latest storage technology and DB2 features
• Highest efficiency
Duplication of Subsystems
How does a tool manage those issues?
• Instant CloningExpert for DB2 z/OS – HSC component:
• Dataset names – If on the same “system” duplicates
Super fast low level RENAME
• Subsystem parameters – In built “names” VCAT etc.
XML user exits for all parameters
• Manual Intervention – Issuing shutdown messages etc.
XML user exits for external event triggering
• Huge folder full of instructions – updates, errors etc.
Automated step-by-step customizable system
Duplication of Subsystems
What are the key benefits of the HSC component?
• Supports and exploits storage subsystem instant copies like
• Backup systems or native
• ESS Flashcopy
• Timefinder
• Snapshot
• Assures data consistency for cloned data taken from running source systems –
no source outage
• Supports rename – even changing the HLQ length
• Guides and verifies the entire process
• Takes care of special steps (e.g. V8 V9, DS NDS)
Duplication of Subsystems
What are the key benefits of the HSC component?
• Guides and takes care of the various types of cloning
• Non data sharing to non data sharing
• Data sharing to data sharing
• Non data sharing to data sharing
• Data sharing to non data sharing
• Data sharing x members to data sharing y members
One standardized, central solution for your cloning needs
Duplication of Subsystems
And now a quick walk through the
HSC component
Duplication of Subsystems
Screen Flow of the HSC component
Duplication of Subsystems
Screen Flow of the HSC component
Duplication of Subsystems
XML scenario framework of the HSC component
Duplication of Subsystems
Screen Flow of the HSC component
Duplication of Subsystems
Screen Flow of the HSC component
Duplication of Subsystems
Screen Flow of the HSC component
Duplication of Subsystems
Screen Flow of the HSC component
To Clone or not to Clone?
How to achieve those benefits (…continued)?
Merge/Duplication of systems/data
The various ways/flavors of Cloning
Merge of systems/data
DB2-B
The various ways of cloning
DB2
Duplication of systems/data
The various ways/flavors of Cloning
Refresh Cloning
The various ways of Cloning
Merge/Duplication of systems/data
Refresh of an entire system or parts of it
• Details about Source and Target
• Scope of Cloning
• Required Steps
• Gotchas to watch out for
Merge/Duplication of systems/data
Details about Source and Target:
• All or parts of data from a system is duplicated
• Including/Excluding objects
• Source and target can be different or the same
• Applying conversion allows to clone objects (e.g. DB) in one and the same DB2 subsystem
• Existing objects may only want to be refreshed
Homogeneous Object Cloning (aka. HOC)
Merge/Duplication of systems/data
Scope of Cloning:
• We are talking about database object cloning. This usually doesn’t include the
DB2 subsystem /data sharing groups
• Catalog and Directory
• Any other DB2 subsystem specific parts
Merge/Duplication of systems/data:
Required steps:
• Define scope of objects
• Determine depending objects like indexes, views, authorization, … if desired
• Extract DDL for resulting source objects
• Extract data from resulting source objects
• Apply naming conversion if desired
• Run DDL on target
• Load data on target objects
Note: Refresh only requires the data
Merge/Duplication of systems/data
Gotchas to watch out for:
• Don’t burn time and resources
• If you have the appropriate storage features, use them!
Instant copies (like Flashcopy2) can clone your TB-sized source
objects in a fraction of time
Instant copies (like Flashcopy2) don’t burn CPU
DB2 supports Flashcopy2 for ONLINE CHECK INDEX maybe for
copies one day, too ;-)
Merge/Duplication of systems/data
Gotchas to watch out for:
• Be careful with Sequences
Mange them correctly
• Be careful with XML (This is not supported by DSN1COPY)
Use the cross loader for XML
• Be careful with availability
Use DB2 Clone Tables
Merge/Duplication of systems/data:
Gotchas to watch out for:
• Be careful with user defined objects
DEFINE CLUSTER
• Be careful with Multi linear datasets in both directions
• Multi on source – single on target
• Single on source and multi on target
• or even multi on source and multi on target but different number of used datasets
Delete all non-used data sets to avoid later problems
Merge/Duplication of systems/data
Bottom Line:
Cloning DB2 objects isn’t rocket science, but there are some specialties to take care of
Familiarize yourself with these procedures and define an easy to use step by step guide.
Tools that supervise, manage and optimize cloning lead to
• More flexibility
• Higher degree of automation
• Exploitation of latest storage technology and DB2 features
• Highest efficiency
Merge/Duplication of systems/data
How does a tool manage those issues?
• Instant CloningExpert for DB2 z/OS – HOC component:
• DDL processing
High speed DSNTIAD
• Object/Dataset names – If on the same “system” duplicates
flexible renaming and wildcard support
• Complex dependencies and structures
optional dependency support
• User defined objects and multi linear datasets
Out of the box dataset level management
Merge/Duplication of systems/data
What are the key benefits of the HOC component?
• Supports and exploits storage subsystem instant copies like
• Flashcopy2
• Supports DB2 copies and DSN1COPY
• DSN1COPY jobs are generated with the appropriate OBIDXLAT option to translate the object IDs.
• It takes care of
• “normal” DDL
• Stogroups
• Sequences
Basically anything valid up to DB2 10
Merge/Duplication of systems/data
What are the key benefits of the HOC component?
It splits object and data cloning
Copies DDL and/or data only using one of the methods below
• Extract object data from source and generate DDL to run on target DB2
• Data Copy using DSN1COPY based on Copies or VSAM DB2 Cluster
Refresh via DB2 Clone Tables for High Availability
One standardized, central solution for your cloning needs
Merge/Duplication of systems/data
And now a quick walk through the HOC component
Merge/Duplication of systems/data
Screen flow of the HOC component
Merge/Duplication of systems/data
Screen flow of the HOC component
Merge/Duplication of systems/data
Screen flow of the HOC component
Merge/Duplication of systems/data
Screen Flow of the HOC component
Merge/Duplication of systems/data
Screen Flow of the HOC component
Merge/Duplication of systems/data
Screen Flow of the HOC component
Merge/Duplication of systems/data
Screen Flow of the HOC component
Merge/Duplication of systems/data
Screen Flow of the HOC component
Merge/Duplication of systems/data
Screen Flow of the HOC component
Merge/Duplication of systems/data
Screen Flow of the HOC component
Quick Summary
How to serve different needs of cloning?
• Instant CloningExpert consists of two components:
• 1st HSC component
Duplication of subsystem (Homogenous System Copy)
• 2nd HOC component
Merge/Duplication of systems/data
Refresh of an entire system or parts of it
(Homogenous Object Copy)
The real world example
The Requirements:
• Merge multiple NDS production sites with the same subsystem name (DSN)
into a new DS system
The Solution:
• Instant CloningExpert for DB2 z/OS
Merging multiple Non Data Sharing DB2s to one Data Sharing Group
• HSC component creates the DS base system from the first production NDS
system
• HOC component migrates data from additional systems
The real world example
DSN
DSN
DSN
DSN
New
DATA SHARING
Group DB2P
Base Clone using HSC
Partial Clone using HOC
Partial Clone using HOC
Partial Clone using HOC
The real world example
The steps of the procedure:
• Base clone of first NDS DB2 using HSC:
Backup system used for data consistency
Restore source volumes and fast rename (new naming
conventions applied DSN DB2P)
Start Target DB2 Access Maint and Alter/Switch VCAT
Apply source Bufferpool-Settings
The real world example
The steps of the procedure:
• Partial clone of second to last NDS DB2 using HOC:
Selection of source objects based on wildcards
Depending objects discovered and included
Full SHRLEVEL REFERENCE copies used (some objects data directly
taken from DB2 VSAM Clusters)
Objects defined on target using high speed DSNTIAD (new naming
conventions applied)
Process applied to each NDS to merge
The real world example
The steps of the procedure:
• The scenario was tested and proofed in two simulation steps before the final
going live.
• After the initial set up access path checks were executed to validate
performance. Since stress tests only allowed simulation of the workload, the
customer used
Bind ImpactExpert for DB2 z/OS
to verify all resulting access paths
• for static SQL
• for dynamic SQL
The real world example
DSN 1-4
Dyn.
EXPLAIN
SQL
OWNER
SHADOW
PLAN_
TABLE
PLAN_
TABLE
Explain
table
REBIND
Cards
Batch report
PLAN
_
TABL
E
DSN
DSC
Snapshot
SHADOW
SYSPKGE
SYSPLAN
DB2P
SYSPKGE
SYSPLAN
DSN
Dyn.
EXPLAIN
The real world example
The steps of the procedure:
• Final production availability checks before AND after going live were processed
using
Recovery AssuranceExpert
to check the new environment created. This included
• Verifying the ZPARMS for the DS environment
• Verifying the coupling facility defined for the DS environment
• Verifying the recoverability of all objects
• Verifying logging for the DS environment
Summary
• Cloning is a powerful way to duplicate data, or entire subsystems for multiple
purposes
• It’s important to understand what’s required and choose the right scenario
• Exploiting instant copy technology can speed up cloning significantly
• Setting up standard procedures increases the degree of automation and makes
the complex scenarios less error-prone
Summary
Instant CloningExpert – ICE
• Automates cloning even beyond
DB2 tasks
• Supports the different flavors
• Exploits storage technology
advantages
• Speeds up cloning
• Is flexible and easy to use
• Ensures consistency of your data
Your Cookie Cutter for DB2