Articles & Content
Topic: 2008 NA
Subtopic: DB2 for z/OS
DATE: 2008-5-19 (01:30 PM - 02:30 PM)
SPEAKERS: Judy Ruby-Brown (IBM Dallas Systems Center)
DASD mirroring solutions for loss of site are overkill for most companies' business requirements and budgets. Common standards are a 24-hour RPO (data loss) and 24 hour RTO (recovery time). About 80% implement the traditional DB2 disaster recovery scenario described in DB2 Administration and use PTAM (" Pickup Truck Access Method") to deliver tapes to a vendor site. It is inexpensive (in terms of hardware), costly (in terms of people skill to develop, execute, maintain), and takes hours-days to recover critical applications. DB2 9 has exciting news in this space. You can back up an entire DB2 at one time and restore it at one time easily. You can do a normal startup versus massive recoveries. You can reduce the RTO to physical tape dump restoration, while keeping the RPO at 24 hours (or less), and without changing basic infrastructure at the recovery site. This presentation describes several scenarios that use DB2 9 as well as improvements in DB V7/V8.
EXP. LEVEL: Intermediate
Problems users encounter when using Traditional DR scenario
How FlashCopoy and other "instant copy" scenarios can back up a subsystem and allow a user to perform a tape restore followed by a normal restart
How DB2 V8 Restore System Logonly can be used for DR
How DB2 9 improves on prior non-mirroring solutions for the easiest DR scenario yet
How to evaluate each of the solutions in light of his/her own RPO/RTO - the good, the bad, any special issues
This file is being provided by IDUG. We would encourage you to join IDUG to get full access to all of our files and resources. Joining IDUG is FREE and signing up is simple. Click here to join! or login!Click to Download
NOTE: These are only open to members of IDUG. If you are not a member, please CLICK HERE for more information.