John, ICs are not related to availability, they're needed to recover.
So, you need IC if you need to recover to a certain point in time (IC, Quiesce etc.) in case of application failure (logic data issues) more than system failure. Usually customers take in count the Db2 log lifecycle and hold enough IC to restore data to any point in time. For instance, if your logs lifecycle is two weeks and IC are taken weekly, maybe last three ICs are enough. Like always in DB2 world ..... it depends. Best regards. Max Il giorno mer 17 giu 2020 alle ore 22:12 Benik, John E < 000001ace072c099-dmarc-requ...@listserv.ua.edu> ha scritto: > Are there any good recommendations/suggestions on retaining DB2 Image > Copies? Specifically in an environment where all data is replicated. It > is my belief that we are retaining the data for Image Copies much longer > than it needs to be in many cases, but I'm not sure if there is a best > practice recommendation available. > > Sincerely, > > John Benik > > > > This e-mail, including attachments, may include confidential and/or > proprietary information, and may be used only by the person or entity > to which it is addressed. If the reader of this e-mail is not the intended > recipient or his or her authorized agent, the reader is hereby notified > that any dissemination, distribution or copying of this e-mail is > prohibited. If you have received this e-mail in error, please notify the > sender by replying to this message and delete this e-mail immediately. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
