Download PDF - IBM Redbooks

– SMS constructs and ACS routines
– No suspension of write log activity
– Suspension of the data set creation, deletion, rename, and extend operations
► DB2 BACKUP SYSTEM utility
– Uses z/OS DFSMSdss fast replication services
– Issues the commands (DFSMShsm) to DFSMSdss and tracks the copies
– Considers complete DB2 database as an entity, which is ideal for SAP
– No downtime needed
– DB2 single point of control
► DB2 RESTORE SYSTEM utility
– Only needed to recover DB2 subsystem to arbitrary PIT
– Specifies (DBA) recovery target point
– Automatically restores last FlashCopy backup before that point
– Automatically applies log to move system to recovery target point
► BACKUP SYSTEM FULL utility
– Only needed to restore to the point-in-time (PIT) of backup
– Also used as a source system in the cloning process
– Copies the entire database subsystem
– Two SMS copy pools:
Database, which includes the user data, DB2 catalog and directory, and associated
z/OS ICF catalogs
Log, which includes the active log, BSDS, and associated z/OS ICF catalogs
► BACKUP SYSTEM DATA ONLY utility
– Copies the database copy pool only, for point-in-time recovery (PITR)
► DB2 RESTORE SYSTEM utility
– Used to recover DB2 subsystem to arbitrary PIT or to current state
– Uses the database copy pool
– Is Fastest algorithm possible
– Specifies (DBA) recovery target point
– Automatically restores the last FlashCopy backup before that point
– Automatically applies log to move system to recovery target point
– Uses Fast Log Apply to presort log records in memory, to prefetch data pages and to
process log by parallel streams
– A separate set of SMS storage groups required for each SAP or DB2 subsystem
Do not copy the archive logs; place them in a separate SMS storage group. Also place the
ICF catalog in the same SMS storage group as the data sets. For nonproduction, multiple
DB2 subsystems can reuse the same SMS backup pool.
192 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System