IMS Cloning Tool - IMS UG May 2012 Philadelphia

526 views
415 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
526
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IMS Cloning Tool - IMS UG May 2012 Philadelphia

  1. 1. IMS Cloning Tool IMS Regional User Group Philadelphia, PA 5/2/2012Rick EngelIMS Tools – Technical Sales Supportraengel@us.ibm.com 1 © 2012 IBM Corporation
  2. 2. Topics for Today’s Meeting• Fast Replication Storage – Host-based data copy options – What is Storage-based Fast Replication? – Why is Storage-aware Fast Replication Needed?• IMS Cloning Tool – Cloning an IMS System – Refreshing Databases 2 © 2012 IBM Corporation
  3. 3. Host-Based Data Copy Options“Traditional” data copy processes use host based CPU and I/O facilitiesMore costly and slower than storage-based fast replication Volume copy options • DFSMSdss (IBM) – FDR (Innovation Data Processing) – – TDMF (IBM) Host-based – FDRPAS (Innovation Data Processing) Copy Process Data set copy options • DFSMSdss (IBM) – FDR (Innovation Data Processing) – An “expensive” use of processing power 3 © 2012 IBM Corporation
  4. 4. Storage Processor = Storage + Processor• Storage – Non-volatile – Computer components and recording media that retain digital data• Processor Host based – Computing system that executes software programs APIs• Storage Processors – Enable data movement through host-based API – Allows CPU reduction from host-based systems 4 © 2012 IBM Corporation
  5. 5. What is Storage-based Fast Replication?• An instant copy of a volume/data set at a specific point in time• Data movement (CPU and I/O) offloaded to storage processor Storage Processor-based – Frees up resources on host processor Copy Process – No host CPU or I/O costs• For volume replication a relationship is established between a source and a target (Pair) – Geometrically similar devices• Consistency Groups – Group of volumes copied at exactly the same point in time while maintaining the order of dependent writes 5 © 2012 IBM Corporation
  6. 6. Local Storage-based Fast Replication• First product availability - late 90s – Used to streamline batch processing – Speed for backup processing• Data copied using storage processor fast- replication facilities Local Storage – Volume based Replication Interface – Data set based Storage Processor APIs• No application or database knowledge• Typically used by storage administrators• Examples Volume Based Fast – IBM FlashCopy Replication – EMC TimeFinder Data set Based Fast Replication – HDS Shadow Image 6 © 2012 IBM Corporation
  7. 7. Remote Storage-based Fast ReplicationFast Rep DASD at another level Primary Production Site Secondary Production Site Volume based remote storage replication Used for business continuity and/or high availability Remote Replication Synchronous or Interface ‘Mirroring’ asynchronous Consistency technology required No application or database knowledge Remote Replication PPRC, SRDF, HUR Typically used by storage administrators Examples  EMC SRDF  IBM PPRC, XRC  HDS HUR 7 © 2012 IBM Corporation
  8. 8. Fast Rep Data Copy Options – Many Choices Fast copy processes offloaded to the storage processor No host CPU or I/O resources = $Savings• Volume-based Fast Replication options – FlashCopy (IBM,EMC,HDS) Fast Replication – SnapShot (IBM,STK) Commands from – TimeFinder / Clone Volume Snap (EMC) z/OS – TimeFinder / Snap (EMC) – Mirror processes  PPRC (IBM,EMC,HDS)  TimeFinder / Mirror, SRDF (EMC)  ShadowImage HUR (HDS)• Dataset-based Fast Replication – Data set FlashCopy (IBM,EMC,HDS) – Data set SnapShot (IBM,STK) – TimeFinder/Clone data set Snap (EMC)Common denominator = eliminate usage of host-based resources 8 © 2012 IBM Corporation
  9. 9. Application and Database Storage Integration “Having storage-aware tools” provide for: • Organizational Integration Mainframe • New Backup Methods Application and • New Recovery Strategies Application and Database • Business Recovery Monitoring Database Management Systems • Disaster Restart Solutions Domain • Cloning Automation Storage-Aware Data Management ToolsStorage Administration Source and Data Business Continuity Backup, Domain Clone, DR 9 © 2012 IBM Corporation
  10. 10. Storage-based Fast Replication Usage - Today• Storage-based fast replication is a huge success but used ineffectively by many (most) mainframe installations – Requires application and database knowledge – Operationally complex to use – Historically used solely by storage administrator role• Storage-aware application and database products provide storage awareness and simplify operational usage 10 © 2012 IBM Corporation
  11. 11. IMS Cloning Tool Capitalizing on your Storage Subsystem11 © 2012 IBM Corporation
  12. 12. Cloning – Some Terminology• A clone is an exact replica – Clone an IMS system by volume – Clone an IMS database by data set• IMS system cloning and database refresh – The act of replicating the data, making the replica accessible, and then using the replica in lieu of the original data• IMS system cloning automation – Clones a complete IMS system including all its databases. – Creates a new, or cloned, IMS system from it without having to repeat the entire installation and system generation processes – Less than 30 minutes (average when using Fast Replication)• IMS database refresh automation – Refreshes specific databases 12 © 2012 IBM Corporation
  13. 13. IMS ‘System’ Cloning - Today Production LPAR Test LPAR IMS001 IMS001 User User Catalogs Catalogs IMS002 IMS002 IMS System IMS System Data Sets Data Sets IMS003 IMS003 Application Application Libraries Libraries IMS004 IMS004 RECON RECON Data Sets Data Sets IMS005 IMS005 Data Base Data Base Data Sets Data Sets Two reads of the data 13 © 2012 IBM Corporation
  14. 14. IMS ‘Database’ Cloning – How you do it ? z/OS Production IMS Test IMS IMS System IMS System Data Sets Data Sets Application ??? Application Libraries Libraries RECON Unload Load RECON Data Sets Data Sets Data Base Data Base Data Sets Data Sets Image Recovery Copy Index Rebuild 14 © 2012 IBM Corporation
  15. 15. Problems with Traditional “Cloning” Methods• Manual step by step methods can be error-prone, inefficient, time consuming, and complicated – Can require the data to be stopped for a long time while the copy operation is performed – Downtime impacts high availability, business waits• Expensive – Resource intensive using large amounts of host CPU and I/O• For IMS system cloning – Requires a separate LPAR to house the copy  Same volsers, same data set names – Requires Sysgen 15 © 2012 IBM Corporation
  16. 16. Create IMS Systems Using IMS Cloning Tool Automation• Performs IMS system cloning automation – Takes an existing IMS system (complete installation and system generation process completed) and creates a Production new(“cloned”) IMS system from it without having to repeat Database the entire installation and system generation processes – You benefit by:  Simplfying IMS cloning processes IMS IMS  Reducing cloning time and administration costs Clone• Performs rapid volume reconditioning and Cloning Tool dataset renaming on cloned volumes to solve Cloning Automation the data access challenges – Target volumes have different volser label than the source volume – Renames the VTOC, VTOCIX, and VVDS to match the target volume – Renames and catalogs all data sets to a new HLQ Source Clone Database Database• Adjusts target IMS to accommodate and accept Volumes Volumes the cloned data – IMS RECONs, PROCLIB, JOBS, JCL, MDA members 16 © 2012 IBM Corporation
  17. 17. Create IMS Systems Using IMS Cloning Tool Automation• Updates done in IMS cloned system – RECONs data sets  Data set names, IMS subsystem IDs, and VOLSERs are updated in the following Production RECON records: Database → header record, database data set records, online log records, and back-out records  Optionally, the following RECON records are updated if they were on volumes that were cloned: IMS → image copy records, change accumulation records IMS → system log data set (SLDS) records Clone → recovery log data set (RLDS) records – IMS PROCLIB, JOBS and user JCL libraries Cloning Tool  New values for IMSID, VOLSERS, and data set names in the JCL members Cloning within these libraries Automation – MDA (MVS Dynamic Allocation) members for databases or system data sets, are updated to reflect the new data set names. Updates include:  The RECON data sets  Online Log data sets (OLDS)  Write-ahead data sets (WADS) – If IMS data sharing is involved, each additional IMS data Source Clone sharing member is updated Database Database Volumes Volumes• Leverages fast replication facilities to clone data – Data can be cloned while online or offline 17 © 2012 IBM Corporation
  18. 18. What makes IMS Cloning Tool so “fast”? • Host-based Copy • Fast Replication Data Copy Options Options Fast Host-based Replication – Data copy processes use host – Fast copy processes offloaded to the Copy Process based CPU and I/O facilities storage processor Commands – Slower than storage-based fast from z/OS – No host CPU or I/O resources replication – Volume copy options for IMS • Data set based fast replication system cloning options for IMS database refresh  TDMF (IBM), – Data Set FlashCopy (IBM,EMC,HDS)  FDRPAS (Innovation Data • Volume based fast replication Processing)  DFSMSdss (IBM) options for IMS system cloning  FDR (Innovation Data – FlashCopy (IBM,EMC,HDS) Processing) – SnapShot (IBM,STK) – Data set copy options for IMS – TimeFinder/Clone Volume Snap or database refresh Snap (EMC)  Any traditional data set – Mirror processes copy processes  PPRC (IBM,EMC,HDS)  TimeFinder/Mirror, SRDF (EMC)  ShadowImage HUR (HDS) – Data set SnapShot (IBM,STK) – TimeFinder/Clone Data set Snap (EMC) 18 © 2012 IBM Corporation
  19. 19. IMS Cloning - Methods • IMS System Skeleton – Clones an IMS system without cloning any data by volume  Recommended for IMS new version migration activities – The replicated system is accessible and is usable in lieu of the original system without requiring a system generation • IMS Full System Clone – Copies an IMS system WITH the databases by volume – The replicated system is accessible and is usable in lieu of the original system without requiring a system generation – Less than 30 minutes average when using “Fast Replication” • IMS Data Refresh – Copies individual or groups of databases by data set 19 © 2012 IBM Corporation
  20. 20. Using IMS Cloning Tool - IMS System Skeleton• Performs IMS system “skeleton” cloning automation Production – System, no databases Database – Takes an existing IMS system and creates a new, or cloned, IMS system from it – Do not need to repeat the entire installation and system generation IMS processes IMS Clone – Simplifies IMS cloning processes IMS Cloning Tool – Reduces cloning time and administration costs Cloning• Leverages fast replication facilities to clone data Automation – Can also leverage traditional Host Based copy options• Performs rapid volume reconditioning and data set renaming on cloned system volumes to solve the data access challenges – Target volumes retain their target volume label Source Clone – Renames the VTOC, VTOCIX, and VVDS to match the target System System volume Volumes Volumes – Renames and catalogs all data sets to a new HLQ• Adjusts target IMS to accommodate and accept the cloned data – IMS RECONs, PROCLIB, JOBS, JCL, MDA members 20 © 2012 IBM Corporation
  21. 21. IMS System Skeleton - What can it deliver to you• Quickly creates a “Sandbox Environment” with an exact copy of the IMS configuration of the source system (system only, no data). – Takes up very little space• A safe place to test RECON fixes• A safe place to test the apply process – Install prerequisite software and maintenance – Install IMS new version – System Definition steps including DBRC migration process• Can you still bring your IMS up?  Are you missing any modules?  Did your RECON upgrade correctly?  Did you skip a step in the apply process?  Run the System Skeleton clone for each configuration and repeat apply testing  Repeatable – automation cleans up between cloning cycles 21 © 2012 IBM Corporation
  22. 22. Using the IMS Cloning Tool - IMS Full System Clone• Performs IMS system cloning automation – Takes an existing IMS system (complete installation and system Production generation process completed) and creates a new, or cloned, IMS Database system from it without having to repeat the entire installation and system generation processes – Simplifies IMS system copy processes IMS – Reduces cloning time and administration costs IMS Clone• Leverages fast replication facilities to clone data IMS Cloning Tool – Data can be cloned while online or offline Cloning – Can also leverage traditional Host Based copy options Automation• Performs rapid volume reconditioning and data set renaming on cloned volumes to solve the data access challenges – Target volumes retain their target volume label – Renames the VTOC, VTOCIX, and VVDS to match the target volume Source Clone Database Database – Renames and catalogs all data sets to a new HLQ Volumes Volumes• Adjusts target IMS to accommodate and accept the cloned data – IMS RECONs, PROCLIB, JOBS, JCL, MDA members 22 © 2012 IBM Corporation
  23. 23. IMS Full System Clone - What it can deliver to you  Quickly Copies an entire IMS system without having to repeat the entire installation and system generation processes  Fast with no interruption to the source system  Copies all the data and is faster than database refreshes • Offload business reporting to an IMS clone – Improve production performance • Create or refresh test, development, or quality assurance environments – Development refresh – To stage data-warehouse loads • Aid in problem determination – Troubleshoot a production problem – Test new releases of IMS – Apply maintenance and verify integrity before applying to production 23 © 2012 IBM Corporation
  24. 24. Using IMS Cloning Tool - IMS Database Refresh• Performs automated IMS database refresh operations Production – Fast refresh of IMS databases Database – IMS DB support (FF, HALDB, DEDB)• Verifies source and target database compatibility IMS IMS• IMS data copied using storage-based data set fast- Source Target replication – Target takes up the same amount of space as the source IMS Cloning Tool Database Refresh• Performs target system meta-data management Automation – Updates DBRC information for target databases• Performs HALDB cloning with integrity – Updates the target IMS RECON – Primary/Secondary indexes and ILDS can be copied to eliminate rebuild time – Manages partition number and gap sequencing IMS IMS System Clone Volumes Volumes 24 © 2012 IBM Corporation
  25. 25. IMS Database Refresh - What it can deliver to you • Quickly copies a specific database or set of databases for targeted testing. – Flexibility to select exactly what database you need thus saving space and time • Application Testing  Before a major upgrade to the application  To debug an error that only happens in production  Create consistent test environments between phases of the testing cycle  Test an application in conjunction with system parameter tweaking • Database Testing  HALDB conversions can be complex and affect database availability  Run performance and integrity utilities 25 © 2012 IBM Corporation
  26. 26. IMS Cloning Tool – Benefits and Advantages • Creates an “exact” Copy – Avoid surprises – Avoid errors – Enable the “lesser” skilled • Fast – No interruptions to your production – Less than 30 minutes average for a full system clone when using Fast Replication • Easily Repeatable – One batch job – Automation includes clean up features between cloning cycles • Flexible – Easily controlled, parameter and command driven • Disposable – If anything fails or you want to try something different, just re-clone the environment 26 © 2012 IBM Corporation
  27. 27. Using IMS Cloning Tool to Migrate to New IMS ReleasesTeleconference – Webcast on May 8, 2012 11:30 AM EST- Automating the cloning process of an entire IMS System with all its data, just an IMS environment, or just IMS- Reducing production downtime when creating exact clones for migration testing- Applying resources based on which vendor and home-grown products need upgradesSpeakers: Margaret M Wilson, IMS Tools Marketing Manager, Rosemary Shay, Quality Assurance and Product Specialist for IMS ToolsBroadcast date: May 8, 2012, 11 a.m., Eastern Daylight Timehttp://www-01.ibm.com/software/sw-events/teleconference/J210596Q30517L24.h 27 © 2012 IBM Corporation
  28. 28. Thank You! Rick Engel IBM IMS Tools Technical Sales Support raengel@us.ibm.com 28 © 2012 IBM Corporation

×