06.01.2013 Views

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

BP2 (4 KB TS): VPSIZE=82000 VPSEQT=50 DWQT=30 VDWQT=5<br />

BP8K1 (8KB TS): VPSIZE=25000 VPSEQT=50 DWQT=30 VDWQT=5<br />

BP16K1 (16KB TS): VPSIZE=10000 VPSEQT=50 DWQT=30 VDWQT=5<br />

BP32K1 (32KB TS): VPSIZE=10000 VPSEQT=50 DWQT=30 VDWQT=5<br />

BP3 (4KB indexes): VPSIZE=120000 VPSEQT=40 DWQT=30 VDWQT=5<br />

BP4 (VB protocol): VPSIZE=1000 VPSEQT=10 DWQT=70 VDWQT=50<br />

BP40 (LOB TS): VPSIZE=4000 VPSEQT=50 DWQT=50 VDWQT=10<br />

Optional, for index compression or indexes with larger page size:<br />

BP8K8 (8KB indexes): VPSIZE=20000 VPSEQT=40 DWQT=30 VDWQT=5<br />

Installation considerations for backup and recovery<br />

Determine a rolling maintenance policy that allows one DB2 subsystem at a time within a data<br />

sharing group or single subsystem to be updated with the latest maintenance. For example,<br />

maintain two copies of the system libraries (n, n+ 1) (SDSNLOAD, SDSNEXIT,<br />

SDSNMACS,SDSNSPFP,...), and change system library names in the procedures (PROCs)<br />

for the DB2 subsystem being updated. If each DB2 subsystem has its own set of libraries,<br />

copy the SMP/E libraries to the system that you are updating. You can also use existing<br />

procedures in DB2.<br />

SAP database backup and restore<br />

For backing up and restoring the SAP database, keep in mind the following considerations:<br />

► Establish backup and recovery procedures for DB2 by using the following DB2 commands:<br />

– BACKUP SYSTEM<br />

– RESTORE SYSTEM<br />

► In DB2 10 image copies are no longer necessary because of the ability to recover single<br />

objects from system copy and because SYSLGRNX maintenance issues are resolved.<br />

► Image copies are still used during online reorganizations (REORGs). Starting with V10,<br />

you can use FlashCopy images for better performance.<br />

The recommended daily image copy of the DB2 Catalog/Directory is, at a minimum, to<br />

perform a volume copy by using the BACKUP SYSTEM command or FlashCopy.<br />

► The DFSMShsm BCDS must have a record length of 6544. For more information, see<br />

DFSMShsm Fast Replication Technical Guide, SG24-7069.<br />

FlashCopy support: All storage vendors for System z support a FlashCopy technology,<br />

but at different levels of integration with DB2.<br />

Preparing DB2 for backup<br />

To prepare DB2 for backups, use the following utilities:<br />

► DB2 Managed FlashCopy Solution with the BACKUP SYSTEM and RESTORE SYSTEM<br />

commands:<br />

– Takes system-level copies of data and logs<br />

– Uses SMS copy pools<br />

– Uses the SMS backup pool<br />

– Required SMS management of DB2 data and logs<br />

Appendix B. Planning, preparing, and implementing the SAP landscape 191

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!