Topic: DB2 for z/OS
Is your Disaster Recovery solution based on DASD replication functions? In most cases, all you will need to do is a normal restart of DB2 for z/OS. But this assumes the DASD copy is consistent. Otherwise, it is guaranteed data corruption which will have to be fixed up, possibly several weeks or months after the event. This presentation will tell you everything you need to know about the Copy Services for IBM System z and what is required to ensure data consistency. It will address the most common myths and misconceptions about these DASD replication solutions. It will also provide hints and tips on how to tune for fast DB2 restart and how to optimise GRECP/LPL recovery. And, as DB2 makes more and more use of FlashCopy, it will discuss all the gotchas of combining FlashCopy and Remote Copy Services.
Click Here to Download
NOTE: These are only open to members of IDUG. If you are not a member, please CLICK HERE for more information.