A full Recovery Log is definitely one of the emergencies that every ADSM/TSM system janitor will face, and should learn how to both prevent and resolve. The two times it has happened to me, were due to running out of scratch tapes, so that it could not back up the database, and after I enlarged the Log and the trigger level did not provide enough time for a Triggered Full Database Backup to complete. My approach now is to do everything I can to avoid a triggered Full Backup, including running an incremental just a couple of hours before the scheduled full backup. The alternative is to set the trigger level so low that I'm wasting quite a bit of disk space, and having more frequent triggered incremental backups as well.
In V3 of the server, the recovery Log is definitely limited to 5.5GB. I still run V3, and I have carefully not made it any bigger than 5.0GB, so I can extend it if it fills. These calculations concerning DSMSERV EXTEND LOG sizes are all explained in the ADSM/TSM System Administrator's Guide. One incentive for you to update to a V4 server is that the maximum size of the Log has been raised to 13GB. If a backup failed to empty the Recovery Log, the backup could have been unsuccessful. Check carefully. There is also a known bug in some V3 ADSM server versions where BACKUP DB failed to reset the Recovery Log to empty. A server restart followed by another backup (incremental OK) was, as I recall, the circumvention. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] ====You will take a long journey. Remember to export your variables.==== On Mon, 17 Dec 2001, Talafous, John G. wrote: >Dwight, > Right you are! The DSMSERV EXTEND LOG command requires the size parameter >to be 1 less than the DSMFMT command previously issued. Go figure. > > Any how, I now find that the TSM 3.7.2 log file max might just be 5.5GB >and the 'extend log' command requires the 1mb reduction. > >Thanks to all, >John G. Talafous IS Technical Principal >The Timken Company Global Software Support >P.O. Box 6927 Data Management >1835 Dueber Ave. S.W. Phone: (330)-471-3390 >Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 >[EMAIL PROTECTED] http://www.timken.com > > >-----Original Message----- >From: Cook, Dwight E (SAIC) [mailto:[EMAIL PROTECTED]] >Sent: Monday, December 17, 2001 12:05 PM >To: Talafous, John G. >Subject: RE: Recover log at 5120MB and full - Cannot start TSM >Importance: High > > >I'd try your dsmserv extend log newlogfilename <something_like_8> or would >it be 9 based on their rules ? ? ? > >I think because you specified 13, it actually might have tried to take it up >to something like 17... >OK, remember that an "extend" says I want x bytes... sure your dsmfmt put >down a 13 MB file (12 for use and 1 for overhead) >but your extend 13 says I want to use 13 and you only have 12 > > > > >-----Original Message----- >From: Talafous, John G. [mailto:[EMAIL PROTECTED]] >Sent: Monday, December 17, 2001 9:22 AM >To: [EMAIL PROTECTED] >Subject: Recover log at 5120MB and full - Cannot start TSM > > >I'm down! TSM 3.7.2 (out of support) on AIX 4.3.2 and the recovery log is >full. I've performed the following: > >dsmfmt -m -log newlogfilename 13 > >dsmserv extend log newlogfilename 13 > >The extend fails with ANR2447E EXTEND LOG: Insufficient space to extend >recovery log by requested >amount. > >I then did a dsmserv dumpdb dev=3590 which executed successfully. However, >this did not reset the recovery log. The server still will not come up. > >Now what do I do? Format and reload? > >Please advise ASAP. > > >John G. Talafous IS Technical Principal >The Timken Company Global Software Support >P.O. Box 6927 Data Management >1835 Dueber Ave. S.W. Phone: (330)-471-3390 >Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 >[EMAIL PROTECTED] http://www.timken.com > > >********************************************************************** >This message and any attachments are intended for the >individual or entity named above. If you are not the intended >recipient, please do not read, copy, use or disclose this >communication to others; also please notify the sender by >replying to this message, and then delete it from your system. > >The Timken Company >********************************************************************** >
