DB2 archives are cleaned only after 2 full db backups. It does not mean you need to run 3 full backups daily. You can run them monthly, but just I couldn't imagine how big space will be required for logs and archives. So you have to run 2 full database backups daily just to save space.
Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Evans, Bill Sent: Wednesday, September 02, 2009 5:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Log space required in 6.1 You have to do three FULL DB backups per day? Can't you just have enough log space to let this run for three days (or does that not meet the 3 DB backup requirement?) Does anyone know why there is a requirement for 3 DB backups before the logs are reset? Thanks, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER 206.667.4194 ~ bev...@fhcrc.org -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Wednesday, September 02, 2009 5:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Log space required in 6.1 Don't forget the requirement for 3-full DB backups before the translogs/archtranslogs are purged/reset. I too ran into the log overflow/blew out 300GB of archtranslog space/filesystem and had to move it to a 1TB disk to hopefully prevent this from happening again, as well as performing 3-daily FULL DB backups. From: Grigori Solonovitch <g.solonovi...@bkme.com> To: ADSM-L@VM.MARIST.EDU Date: 09/02/2009 07:29 AM Subject: [ADSM-L] Log space required in 6.1 Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Wolfgang wrote: >Now my long term averages are in: for the "interesting" (V5.5) TSM servers around here, the "Log Consumption" ranges from 5000 to 9000 MB/day. >So, does this tell me anything about future (V6) Log Space requirements? I have test database 6.1.2 and I think: 1) you need additional space for DB2 archive logs. Size is the same or bigger then logs (depends on you full backup schedule); 2) you definitely need bigger space for logs. Test TSM 6.1.2 produces logs without any activity at all (5.5 never do this). I need 2-3GB in logs and archives daily without activity at all. Most possible you should plan 4 time s more space for logs and archives: 2 x Log_Size x 2 or more for archives. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com<mailto:g.solonovi...@bkme.com> Please consider the environment before printing this Email Please consider the environment before printing this Email. ________________________________ "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME." "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
