Re: Recovery Log Problems while in Normal Mode
Hi, contrary to the other responses you got so far, I would think that 1.5 GB log size should be big enough for a 13.5 GB DB if you are doing daily DB backups. (Ours is 0.8 GB , Db size ist 38 GB.) Was EXPIRE INVENTORY running when the server crashed? Perhaps you had the same problem as we had last weekend: Our recovery log went full (but did not crash the server). The reason: Due to the Daylight Savings Time (DST) error in the Windows TSM client, many of our Windows clients did full backups after the DST switch. So, many backup copies became inactive and were expired through the EXPIRE INVENTORY run last weekend, causing an unusually big amount of change activity against the DB, which all had to be buffered in the recovery log during DB backup. Reinhard Wood, Dwight - BSC writes: > My recovery log filled up and crashed the server this morning. I have the > recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the > impression that the recovery log would not fill up and crash the system > while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full > DB backup once a day, sometimes twice. When I restarted the server the log > showed up as 0.1% utilized. Does anyone have any idea as to what might cause > the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks, > -Dwight -- Reinhard MerschWestfaelische Wilhelms-Universitaet Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583 E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
Re: Recovery Log Problems while in Normal Mode
Lots of uncommitted transactions. I've seen this before on logs around a gig in size. You wouldn't think the works would/could get that far behind, but with large transaction loads it happens. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (719) 260-5991 Email: [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wood, Dwight - BSC Sent: Wednesday, December 06, 2000 8:50 AM To: [EMAIL PROTECTED] Subject: Recovery Log Problems while in Normal Mode My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up and crash the system while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full DB backup once a day, sometimes twice. When I restarted the server the log showed up as 0.1% utilized. Does anyone have any idea as to what might cause the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks, -Dwight
Re: Recovery Log Problems while in Normal Mode
You may want to expand the size of your recovery log. That would at least reduce the chances of crashing due to a full recovery log. The logs will usually fill up if you have alot of sessions going at once. Or especially if you use the Lotus Notes 4.6 agent. Its my understanding that some data just cannot be committed to the ADSM Db until the client lets go of it. In my experience this is not a problem with regular clients but with ADSM agents this can be a problem. If you have been experiencing some growth then you will have to expand the DB and Logs eventually. Just remember the max size of the ADSM recovery log is 5.5 gigs. I wouldn't expand past 5 gigs to be safe. Jack -Original Message- From: Wood, Dwight - BSC [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 06, 2000 10:50 AM To: [EMAIL PROTECTED] Subject: Recovery Log Problems while in Normal Mode My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up and crash the system while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full DB backup once a day, sometimes twice. When I restarted the server the log showed up as 0.1% utilized. Does anyone have any idea as to what might cause the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks, -Dwight
Re: Recovery Log Problems while in Normal Mode
Well, You have 2 possibles either :- 1) Your log is not big enough for you workload. Do you monitor/trend its max utilization 2) You have a rogue session or process that caused the problem. If you still have the ADSM log from before the crash, can you see what was going on Lawrence Clark <[EMAIL PROTECTED]> on 12/06/2000 04:07:25 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Recovery Log Problems while in Normal Mode It fills until the db reaches a 'sync' point. Something like a number of clients backing up concurrently but not as yet completed can fill up the log file. >>> [EMAIL PROTECTED] 12/06/00 10:49AM >>> My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up and crash the system while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full DB backup once a day, sometimes twice. When I restarted the server the log showed up as 0.1% utilized. Does anyone have any idea as to what might cause the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks, -Dwight ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric and Southern Electric are trading names of Scottish and Southern Energy Group. **
Recovery Log Problems while in Normal Mode
My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up and crash the system while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full DB backup once a day, sometimes twice. When I restarted the server the log showed up as 0.1% utilized. Does anyone have any idea as to what might cause the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks, -Dwight
Re: Recovery Log Problems while in Normal Mode
It fills until the db reaches a 'sync' point. Something like a number of clients backing up concurrently but not as yet completed can fill up the log file. >>> [EMAIL PROTECTED] 12/06/00 10:49AM >>> My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up and crash the system while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full DB backup once a day, sometimes twice. When I restarted the server the log showed up as 0.1% utilized. Does anyone have any idea as to what might cause the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks, -Dwight
