Yep, increasing the recovlog is doing the job. Thanks to all! Thanks for not just saying RTFM too. I really do plan to read it front2back when I get some time to do so. I need 3 months off just to read the 100 or so manuals I want to absorb better. A well planned setup saves time, I do know that.
Alex
On Fri, 25 Mar 2005, Mark D. Rodriguez wrote:
Alexander,
TSM won't let you delete those volumes since they are all part of the most recent DB backup set.
It appears that you are doing incremental DB backups at random times which indicates that the DB backup trigger is causing these backups. The DB backup trigger happens when the log space starts to be over committed. Therefore there are several suggestions I can make to you.
1. Increase the size of your log file, This should cut down on the number of triggered DB backups. 2. Consider changing your strategy for DB backups. I recommend that your "on site" DB backups should be full/incremental and should be done to a device type of file. Typically I do a full once a week and do incremental the rest of the week. There is no performance hit since it is to a device of type file. Also, set your DB backup trigger to use this device and set the number of incremental to the max. BTW, with a DB of 15GB using 1 full and six incremental plus keeping the full previous set (i.e. the previous weeks) you should need less than 50GB of disk space. 3. For off site DB backups use a snapshot backup to tape. Only run this on the days that you take tapes off site.
I have given you the basic concepts of what I would do. If you need more specific commands on how to implement this please feel free to ask.
-- Regards, Mark D. Rodriguez President MDR Consulting, Inc.
=============================================================================== MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===============================================================================
Alexander Lazarevich wrote:
HEre's the output:
tsm: TSM>q volh t=dbb
Date/Time: 03/21/2005 11:00:48 Volume Type: BACKUPFULL Backup Series: 112 Backup Operation: 0 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG044L2 Volume Location: Command:
Date/Time: 03/24/2005 18:16:08 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 1 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG010L2 Volume Location: Command:
Date/Time: 03/25/2005 06:01:13 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 2 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG033L2 Volume Location: Command:
My issue with that idea is the database is only 13-14GB, so how could it need 3 tapes for the DB backup? I've been backing up the DB for 2 years, and it never needed more than 1 tape for it:
tsm: TSM>q db
Available Assigned Maximum Maximum Page Total Used Pct Max. Space Capacity Extension Reduction Size Usable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util --------- -------- --------- --------- ------- --------- --------- ----- ----- 32,000 32,000 0 18,028 4,096 8,192,000 2,846,578 34.7 43.
Thanks!
On Fri, 25 Mar 2005, Mark D. Rodriguez wrote:
It would help if we could see the output of the following command:
q volh t=dbb
It might be that this is the most recent DB backup in which case it won't let you delete it.
-- Regards, Mark D. Rodriguez President MDR Consulting, Inc.
===============================================================================
MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===============================================================================
Alexander Lazarevich wrote:
TSM 5.1.9.0 on win2K server.
I'm failing to delete the volume histories on the following volumes (LTO-2 tapes):
tsm: TSM>q libv
Library Name Volume Name Status Owner Last Use Home ------------ ----------- ---------- ---------- --------- ---- LB6.0.0.3 ITG010L2 Private DbBackup 41 LB6.0.0.3 ITG033L2 Private DbBackup 64 LB6.0.0.3 ITG044L2 Private DbBackup 48
The command I run is:
tsm: TSM>del volhist type=dbbackup todate=today
Do you wish to proceed? (Yes (Y)/No (N)) yes ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted.
None of the dbbackup volumes are deleted though. Why? This has always worked in the past. Anyone have any idea? Logs don't give any error:
ANR2017I Administrator DUDE issued command: DELETE VOLHISTORY type=dbbackup todate=today ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted.
I need an answer fast as I've only got 1 scratch tape left because the dbbackups keep stealing tapes. The database is only 14MB so it should fit on one tape easy. Thanks in advance,
Alex
