IBM offers several solutions for coordinating IMS and DB2 backup and recovery. Approach 1 uses a single system level backup (SLB) containing both IMS and DB2 volumes, while Approach 2 uses separate SLBs for IMS and DB2 with point-in-time recovery log application. Both approaches minimize downtime and data loss during disaster recovery. FlashCopy is used to quickly create SLBs with minimal host impact. Recovery time objectives (RTOs) and recovery point objectives (RPOs) are improved through frequent SLB creation and transmission to remote sites.

1. IBM IMS and DB2 Backup and Recovery Workshop
Coordinated IMS and DB2 Recovery
Glenn Galler
gallerg@us.ibm.com
IBM Advanced Technical Skills (ATS)
© 2013 IBM Corporation
IBM Software

2. IBM Disaster Recovery Solutions
 IBM Recovery Solutions
► Databases are recovered using image copies and/or logs
 IBM Restart Solutions
► All production data is mirrored to remote site
● IMS and DB2 Recovery Expert products: System Level Backup
● GDPS and Storage Mirroring
 IBM Restart & Recovery Solution
► All production data is mirrored to remote site
► Additional transmitted data allows for forward recovery
 Coordinated IMS and DB2 Restart & Recovery Solution
► Approach 1: SLB contains both IMS and DB2 volumes
► Approach 2: Separate SLBs for IMS and DB2 and PITR log recovery
2 IBM Software

3. IBM Local Application Recovery Solutions
 IMS Recovery Solutions
► Databases are recovered using SLB, image copies and/or logs
► Indexes can be rebuilt with index rebuild utility
 DB2 Recovery Solutions
► Tablespaces are recovered using SLB, image copies and/or logs
► Indexes can be rebuilt with index rebuild utility
► Undo/Redo SQL
► Dropped object recovery
 Coordinated IMS and DB2 Recovery Solutions
► IMS Recovery Expert, IMS Recovery Solution Pack, DB2 Recovery
Expert
● IMS and DB2 databases are recovered using SLB, image copies and logs
● Recovery to a consistent timestamp between IMS and DB2
● Application profiles for IMS and DB2 determine recovery relationships
3 IBM Software

4. RTO vs. RPO
 Recovery Time Objective (RTO)
► Time allowed to recover an application
► Critical operations are up and running again
► Considerations include:
● For DR, recovery of databases and network
 Recovery Point Objective (RPO)
► Amount of data lost for an application or in a disaster
► Last point-in-time when all data was consistent
► Considerations include:
● Frequency of creating recovery points
● Frequency of transfer of data to remote site for DR
4 IBM Software

5. FlashCopy Overview
 IBM and Vendor Options
 Establish/Thaw vs. Background Copy
 FlashCopy for a Consistency Group
5 IBM Software

6. FlashCopy Overview
 FlashCopy (FC)
► Optional licensed feature of IBM Enterprise storage subsystems
► Creates instant copy of a volume or dataset at specific point-in-time
► Often referred to as:
● Point-in-Time copy, instantaneous copy or time zero (t0) copy
 Advantages
► Can copy huge volumes of data very quickly (seconds to a few minutes)
► Minimal disruption for the running applications
► Copy process is offloaded to the storage subsystem
● Leads to lower host CPU and I/O costs
 Usage Examples
► Create a System Level Backup (SLB) of IMS and DB2 production volumes
● Replaces creation of 1000’s of image copy data sets
► Create a single image copy
6 IBM Software

7. IBM and Vendor Options
Volume Level Fast Replication
Provider Method Consistency
IBM FlashCopy FlashCopy Consistency Groups
IBM Space Efficient FlashCopy FlashCopy Consistency Groups
EMC TimeFinder Full Volume Clone Enginuity Consistency Assist (ECA)
EMC Timefinder/Snap Virtual Devices Enginuity Consistency Assist (ECA)
EMC TimeFinder Compatible Flash FlashCopy Consistency Groups
(With EMC FlashCopy Emulation License)
Hitachi Shadow Image DB2 Recovery Expert Log Suspend
or DB2 Log Suspend
IMS Recovery Expert Log Suspend
Hitachi FlashCopy FlashCopy Consistency Groups
(With HDS FlashCopy Emulation License)
7 IBM Software

8. Traditional Copy vs. FlashCopy
 Traditional Copy (DB2 Share Level Reference, IMS Clean)
1) Source dataset (DB2 and IMS) is unavailable for update during copy
Source Processing
Source Processing Traditional Copy
Target Processing
Application Update Outage
 FlashCopy is a Two-Phase Backup
1) Establish/Thaw: Creates source->target relationship
2) Background Copy: Tracks are physically copied in the background
Source Processing
Source Processing Establish/Thaw FC Background Copy
Target Processing
Appl Delay
8 IBM Software

9. Source and Target Volumes
 FlashCopy command issued
1) Source and Target volume relationship established
2) Track bit map created
3) Source volumes available immediately for updates
Source Target
Track Bit Map
Establish/Thaw FC
4) In background copy, tracks are copied from Source to Target
5) Track bit map is updated
Source Target
Track Bit Map
Background Copy
9 IBM Software

10. Source I/O’s during Background Copy
 Reads
1) “Read from Source” comes directly from Source
Source Target
Track Bit Map
Background Copy
Read I/O
 Writes
1) “Write to Source” writes directly to Source (if already copied)
a. If not already copied, force copy to Target, then write to Source
Source Target
Track Bit Map
Write I/O Background Copy
10 IBM Software

11. FlashCopy for a Consistency Group
 DBMS Consistency through Dependent Writes
► Update and Commit log records are consistently ordered in logs
 Storage Processors
► Ensures consistency across a set of volumes
 FlashCopy for a Consistency Group
► DBMS and Storage Processors working together
► Key to storage-based fast replication software solutions
11 IBM Software

12. FlashCopy for Consistency Group
Backup Elapsed Time (Worst Case) = I/O Resume – I/O Suspend
Source Source Source Source Source
Backup Time
I/O Resume Time
I/O Suspend Time
S1 S2 S3 S4 S5
(Loadlibs) (DB2 Log) (DB2 DB) (IMS Log) (IMS DB)
Target Target Target Target Target
T1 T2 T3 T4 T5
(Loadlibs) (DB2 Log) (DB2 DB) (IMS Log) (IMS DB)
12 IBM Software

13. Establish/Thaw Benchmark
Source Target
Track Bit Map
Establish/Thaw FC
IMS Recovery Expert for z/OS
Backup Summary Report
Utility Executed:......... Backup
Profile Name:............. ROCKET1.BKUP1
IMS Subsystem:............ IMSP
IMS Version:.............. 12.1
Backup Type:.............. Flash Copy
Backup Contains:.......... Database, Log Data (Mixed)
Specifications Partial Backup:........... No
1) 13 TB of data Nbr of Volumes:........... 0461
2) 461 volumes Backup Date:.............. 02/01/2012
3) DS8300 Backup Time:.............. 2012-02-01-17.03.20.671934
Consistency Method:....... Flash Consistency Group
4) 2817-M80 z196 Supports Database Restore: No
5) 4,075.28 trans/second I/O Suspend Time:......... 2012-02-01-17.03.20.671932
I/O Resume Time:.......... 2012-02-01-17.03.21.042397
6) Backup Elapsed = 0.37 secs Backup Elapsed:........... 00.37 Seconds
13 IBM Software

14. IMS and DB2 Recovery Expert: SLB
 Environment discovery and configuration management
► IMS System Level Backup includes:
● Active and archive logs
● RECONs
● All IMS database data sets
● IMS system data sets (ex. ACBLIBs, DBDLIBs, PGMLIBs, etc.)
● All associated ICF User catalogs
► DB2 System Level Backup includes:
● Active and archive logs
● Bootstrap Data Set
● All DB2 database data sets
● DB2 system data sets (ex. Loadlib)
● All associated ICF User catalogs
14 IBM Software

15. SLB vs. Image Copy: What are the Advantages?
SLBs + Reorg Image Copies Image Copies Only
FlashCopy SLBs Reorg Image Copies Weekly Image Copies
IMS SLB DB2 SLB
• One Backup job vs. 10K image copy jobs
Storage Processor • Less Host CPU on job allocations
• FlashCopy offloads work to storage processor
• Pre-built recovery jobs
• Verification of recovery resources when system is healthy
15 IBM Software

16. SLB Image Copies are Registered to DBRC
 NOTIFY.IC is done when SLB is created
► Image Copy GENMAX
► PRILOG compression/deletion
► Reset Change Accumulation starting point
 “Pseudo” data set name used for IC DSN
► Additional disk space not used for IC data set
► Data set allocation at SLB time
● Determines Concurrent IC vs. Batch IC
► User can configure either IC or UIC
 “Real” image copy can be created from SLB
► Replaces “Pseudo” image copy in DBRC
16 IBM Software

17. Coordinated IMS and DB2: Approach 1
 Coordinated IMS and DB2 Restart Solution
► Combined SLB created from IMS and DB2 volumes
● Separate analysis is performed on IMS and DB2
– Volumes combined under one Recovery Expert product
● At Primary site
– One SLB is created
– One Flashcopy for all volumes (IMS & DB2)
● At Remote site
– SLB is restored
– IMS and DB2 are restarted individually
– Restart with Dynamic Backout and Undo/Redo processing occur
17 IBM Software

18. Approach 1: IMS Recovery Expert
Production Site IMS System Analysis
RDS SLDS
WADS
RLDS
Logger
OLDS
IMS Volume 1 Change Accum
IMS Volume 2
IMS Volume 3
IMS Control
IMS Volume nn
Region
Image Copy
DBRC
RECON
IMS RE
Repository
IMS Databases
DLI/SAS
18 IBM Software

19. Approach 1: DB2 Recovery Expert
Production Site DB2 System Analysis
Logs
Logger Logs
DB2 Master Image Copy
DB2 Volume 1
DB2 Volume 2
DB2 Volume nn
DDF
DB2 RE
Repository
DB2 Tablespaces
19 IBM Software

20. Approach 1: Coordinated DR - DB2 RE or IMS RE
DB2 Volume 1
DB2 Volume 2 Create IMS and DB2 SLB
DB2 Volume nn
Logger
IMS and DB2
Combined SLB
DB2 Master
IMS Volume 1
DDF IMS Volume 2
IMS Volume 3
IMS Volume nn
20 IBM Software

21. Approach 1: IMS and DB2 Restart
Remote Site
Restart IMS/DB2 Restore SLB for IMS/DB2 Transmitted
WADS SLDS
IMS and DB2
OLDS RLDS Combined SLB
Logger
RDS Change Accum
IMS Control Region
RECON
Image Copy
DBRC IMS Databases
IMS RE Repository
DLI/SAS
Logs Logs
Logger
Image Copy
DB2 Master
DB2 RE
DDF Repository
TABLESPACES
21 IBM Software

22. Coordinated IMS and DB2 Restart
 Restore the System Level Backup (SLB)
► Dynamically backout IMS and DB2 uncommitted updates
► RPO = Changes past the last Combined SLB
SLB
Lost IMS/DB2 Data
IMS and DB2 SLB
DB2 LOG 1 DB2 LOG 2
DB2 Tran 1 DB2 Tran 1
UPD UPD CMT UPD UPD UPD UPD UPD UPD CMT UPD UPD CMT
DB2 Tran 2 DB2 Tran 2
UPD UPD UPD UPD UPD CMT UPD UPD UPD UPD CMT UPD UPD UPD CMT
IMS LOG 1 IMS LOG 2
IMS Tran 1 IMS Tran 1
UPD UPD CMT UPD UPD UPD UPD UPD UPD CMT UPD UPD CMT
IMS Tran 2 IMS Tran 2
UPD UPD UPD UPD UPD CMT UPD UPD UPD UPD CMT UPD UPD UPD CMT
22 IBM Software

23. Defining RPO (SLBs Created Once/Day)
Midnight Noon
SLB Creation 2 Hrs
Other Backups 2 Hrs
Send Offsite 1 Hr
SLB Day 1 SLB Day 2
0 1 2 3 12 16 18 22 0 1 2 3 12 16 18 22
DR Event
Best Case Worst Case
DR Event RPO Best Case RPO Worst Case
DR Event SLB Day 1 = SLB + 3 Hrs SLB Day 2 = SLB + 27 Hrs
23 IBM Software

24. Defining RPO (SLBs Created Twice/Day)
Midnight Noon
SLB Creation 2 Hrs SLB Creation 2 Hrs
Other Backups 2 Hrs Other Backups 2 Hrs
Send Offsite 1 Hr Send Offsite 1 Hr
SLB Day 1a SLB Day 1b SLB Day 2a SLB Day 2b
0 1 2 3 12 13 14 15 0 1 2 3 12 13 14 15
DR Event
Best Case Worst Case
DR Event RPO Best Case RPO Worst Case
DR Event SLB 1a = SLB + 3 Hrs SLB 1b = SLB + 15 Hrs
24 IBM Software

25. Defining RTO
Restore z/OS Environment 3 Hrs
Restore SLB 2 Hrs
Restart IMS and DB2 1 Hr
0 3 5 6
Recovery at Remote Site RTO Time
DR Event 6 Hours
25 IBM Software

26. Coordinated IMS and DB2: Approach 2
 Coordinated IMS and DB2 Recovery & Restart Solution
► Separate SLBs created for IMS and DB2 volumes
● Separate analysis is performed on IMS and DB2
● At Primary site:
– Separate SLB is created for IMS and for DB2
♦ One FlashCopy for each set of volumes (IMS & DB2)
– Archived logs are transmitted to remote site
♦ Log Timestamps are recorded in DR PDS
● At Remote site:
– IMS and DB2 SLBs are restored
– Point In Time Recovery using timestamp in IMS and DB2 DR PDS
♦ Earlier of two timestamps in IMS and DB2 DR PDS
– Start IMS and DB2 (No Backouts/Undos needed during restart)
26 IBM Software

27. Approach 2: IMS Recovery Expert
Production Site Remote Site
RDS
SLDS/RLDS
Transmitted
WADS
RECON
Logger OLDS
System Level Backup
Chang Accum
IMS Control
Region
Image Copy
DBRC
IMS RE
Repository
IMS Databases
DLI/SAS
27 IBM Software

28. Approach 2: DB2 Recovery Expert
Production Site Remote Site
Transmitted
LOGS
Logger BSDS
DB2 Master
System Level Backup Image Copy
DDF
DB2 RE
Repository
DB2 Tablespaces
28 IBM Software

29. Approach 2: IMS Recovery Expert
Remote Site
Start IMS Recover DB Find Coord RP Transmitted
IMS RE
Repository
System Level Backup
SLDS
Logger
RLDS
Restore SLB
Chang Accum
WADS SLDS/RLDS
IMS Control Region
Conditioned Recon RECON SLDS/RLDS
OLDS
Image Copy RECON
Chang Accum
DBRC RDS
Chang Accum
Image Copy
IMS Databases
Image Copy
IMS Databases
DLI/SAS IMS RE
Repository
IMS RE Repository
29 IBM Software

30. Approach 2: DB2 Recovery Expert
Remote Site
Start DB2 Recover DB Find Coord RP Transmitted
DB2 RE
Repository
LOGS System Level Backup
Logger
BSDS
DB2 Master
Restore SLB
Image Copy LOGS
BSDS
LOGS
BSDS
Image Copy
DDF DB2 RE
Repository
Image Copy
DB2 RE
Repository
DB2 RE
Repository
DB2 Tablespaces
30 IBM Software

31. Coordinated IMS and DB2 Recovery & Restart
 Restore the System Level Backup (SLB)
► Point-In-Time-Recovery for IMS and DB2
► RPO = Changes past the coordinated timestamp
SLB + Logs
Lost DB2 Data
DB2 SLB
DB2 LOG 1 DB2 LOG 2
DB2 Tran 1 DB2 Tran 1
UPD UPD CMT UPD UPD UPD UPD UPD UPD CMT UPD UPD
DB2 Tran 2 DB2 Tran 2
UPD UPD UPD UPD UPD CMT UPD UPD UPD UPD CMT UPD
Lost IMS Data
IMS SLB
IMS LOG 1 IMS LOG 2
IMS Tran 1 IMS Tran 1
UPD UPD CMT UPD UPD UPD UPD UPD UPD CMT UPD UPD CMT
IMS Tran 2 IMS Tran 2
UPD UPD UPD UPD UPD CMT UPD UPD UPD UPD CMT UPD UPD UPD CMT
31 IBM Software

32. Local and Coordinated Application Profiles
IMS Application
Coordinated Local Application Profile
Local Application Profile Local Application Profile
IMS Databases DB2 Tablespaces
IMS and DB2 Application
Single IMS UOR
IMS Databases DB2 Tablespaces
Single IMS and DB2 UOR
DB2 Application
 Coordinated Local Application Recovery Profiles
Single DB2 UOR
► Combination of one or more IMS and DB2 profiles
● Each profile can be in only one Coordinated Profile
► Allows IMS and DB2 applications to be recovered to a consistent point
32 IBM Software

33. Recovery Points
 Recovery Points (RPs) used with Timestamp Recoveries
► Traditional RPs are discovered in the RECON (IMS), SYSCOPY(DB2)
● IMS - DEALLOC shows when database is not allocated for update
● UPDATE DB STOP(ACCESS) or /DBR DB
● UPDATE DB STOP(UPDATES) or /DBD DB
● UPDATE DB START(QUIESCE)
● DB2 – QUIESCE TABLESPACE dbname.tsname
 Point-In-Time Recovery (PITR) to any timestamp
► IMS - Requires IMS Recovery Solution Pack
► DB2 - Requires DB2 Utility Suite
► Traditional RPs are not needed
● Uncommitted updates are not applied
33 IBM Software

34. Coordinated IMS & DB2 Local Application Recovery
 Recovery Expert “Quiet Time Log Analysis”
► Finds Recovery Points in the Log records
● Analyzes actual transaction Unit of Recovery (UOR) activity
– Discovers commit points for IMS and DB2 databases/objects
► Coordinated Quiet Times saved in Repository
DB2 Quiet Time IMS Quiet Time Coordinated Quiet Time
IMS UOR1 IMS UOR1 IMS UOR 1 IMS UOR1
DB2 UOR 1 DB2 UOR 1 DB2 UOR 1 DB2 UOR 1
IMS UOR 2
DB2 UOR 2 DB2 UOR 2
IMS UOR 3 IMS UOR 3
DB2 UOR 3 DB2 UOR 3
34 IBM Software

35. Coordinated IMS & DB2 Local Application Recovery
• Selecting the Consistent Timestamp for recovery
1) Select the “Current Timestamp” (Okay)
● All DBs/objects in Coordinated Profile are stopped for IMS and DB2
● IMS and DB2 logs are switched and archived
● Recovery is to the end of the current set of IMS and DB2 logs
● DBs/objects are restarted
2) Select any “User Timestamp” (Better)
● IMS Recovery Solution Pack (IMS DRF) and DB2 Recovery Utility
– Point In Time Recovery (PITR) applies only the committed updates
3) Select a “Quiet Time Recovery Point Timestamp” (Best)
● IMS and DB2 Recovery Expert identifies RPs from the logs
● IMS Recovery Solution Pack (IMS DRF) and DB2 Recovery Utility
– Point In Time Recovery (PITR) applies only the committed updates
● May provide better linkage to Business Cycle
35 IBM Software

36. Recovering a Coordinated Application
Select Coordinated Application Profile
Select or Specify Recover to Timestamp
Analysis Performed by Recovery Expert to
Determine the Recovery Steps
Submit the JCL
Stop IMS Databases Stop DB2 Tablespaces
Recover IMS Databases Recover DB2 Tablespaces
 Restore from SLB  Restore from SLB
 Restore Image Copies  Restore Image Copies
 Apply Logs  Apply Logs
► To specified timestamp ►To specified timestamp
 Rebuild Indexes  Rebuild Indexes
Start IMS Databases Start DB2 Tablespaces
36 IBM Software

37. Summary of Coordinated IMS and DB2 Recovery
 Coordinated IMS and DB2 Disaster Recovery
► Coordinated IMS and DB2 Restart & Recovery Solution
● Approach 1: SLB contains both IMS and DB2 volumes
● Approach 2: Separate SLBs for IMS and DB2 volumes
 Coordinated IMS and DB2 Local Application Recovery
► Coordinated IMS and DB2 Recovery Solutions
● IMS Recovery Expert, DB2 Recovery Expert, IMS Recovery Solution Pack
– IMS and DB2 databases are recovered using SLB, image copies and logs
– Recovery to a consistent timestamp between IMS and DB2
– Coordinated application profiles connect IMS and DB2
37 IBM Software

38. IMS and DB2 Disaster Recovery Tutorials
► IBM developerWorks
● www.ibm.com/developerworks
– External IBM website with articles, tutorials and demonstrations
► IMS Disaster Recovery Tutorials
● Four parts:
– Part 1: Overview of all solutions
– Part 2: IMS Base and IMS Tool solutions
– Part 3: IMS Recovery Expert Disaster and Local Recovery
– Part 4: Coordinated IMS and DB2 Disaster Recovery
● Downloadable demonstration file
– Demos are installed on hard disk
– Viewed with internet browser
38 IBM Software

39. IMS and DB2 Disaster Recovery Tutorials
►developerWorks URL for Tutorials
● Search on “Exploring IMS Disaster Recovery”
39 IBM Software

40. timestamps
rpo and rto consistency
recovery
FlashCopy
40 IBM Software