Criteria we use is - When was the last time an IMAGE Copy was needed? How much dasd/tape does it take up
How long is the application alive ( has it been in place for 5 years, 100 years) >From those questions we get an idea of what time retention is needed for the image copies. Some shops - the image copy can be delete when the next image copy occurs Other shops, the image copies live the life of the application. - Just in case a year later the apps need to recover data Lizette -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Benik, John E Sent: Wednesday, June 17, 2020 1:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DB2 Image Copies 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
