Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*log\s+growing\s+too\s+quickly\s+\.\.\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*log\s+growing\s+too\s+quickly\s+\.\.\.\s*$/: 8 ]

Total 8 documents matching your query.

1. log growing too quickly ... (score: 1): Author: Steve Harrison <sharris1 AT ISMA DOT COM>; Date: Thu, 1 Apr 1999 15:47:35 -0700; Has anyone had the experience of their log growing too quickly (beyond the normal amount)? We watched our log grow this afternoon from 13% utilized to 46% in just 3 hours, with little activity. We ha; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00083.html (11,096 bytes)
2. Re: log growing too quickly ... (score: 1): Author: Trevor Foley <Trevor.Foley AT BANKERSTRUST.COM DOT AU>; Date: Tue, 6 Apr 1999 11:41:58 +1000; Hi Steve, We've got exactly this problem on one of our four ADSM servers at the moment. We are getting a triggered DB backup at least once per day and can't understand why. The server with the proble; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00133.html (11,194 bytes)
3. log growing too quickly ... (score: 1): Author: Steve Harrison [mailto:sharris1 AT ISMA DOT COM]; Date: Sun, 04 Oct 2015 17:44:48 -0500; Has anyone had the experience of their log growing too quickly (beyond the normal amount)? We watched our log grow this afternoon from 13% utilized to 46% in just 3 hours, with little activity. We ha; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00134.html (11,211 bytes)
4. Re: log growing too quickly ... (score: 1): Author: "Moir,Betsy" <betsy.moir AT ABBOTT DOT COM>; Date: Tue, 6 Apr 1999 07:25:37 -0500; Just a couple of things to think about - we've been trying to get the balance just right on this for a while now. Do you do incremental backups on a scheduled basis or just when the trigger gets set; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00153.html (12,457 bytes)
5. Re: log growing too quickly ... (score: 1): Author: Scott Fluegge <sfluegge AT VENATORGROUP DOT COM>; Date: Tue, 6 Apr 1999 08:41:04 -0400; Just a couple of questions... Why do you do incremental DB backups instead of full backups? Each of our ADSM databases are between 3 and 6 gig and we run 2 full DB backups in the morning. One goes to; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00157.html (13,552 bytes)
6. Re: log growing too quickly ... (score: 1): Author: Dirk Kastens <Dirk.Kastens AT RZ.UNI-OSNABRUECK DOT DE>; Date: Tue, 6 Apr 1999 15:05:09 +0200; It's gaining you at least 50% more free space. If a volume is full and the reclaimable space reaches 50%, it means that you waste 50% of the space on the tape. After reclamation a new tape is filled; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00161.html (11,761 bytes)
7. Re: log growing too quickly ... (score: 1): Author: Gerhard Rentschler <g.rentschler AT RUS.UNI-STUTTGART DOT DE>; Date: Tue, 6 Apr 1999 15:18:12 +0200; Hi, I observed the same problem with the log growing fast. This is especially true for expiration. In this case the log contains by order of magnitude more data than the changes in the db as indicate; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00164.html (11,438 bytes)
8. Re: log growing too quickly ... (score: 1): Author: "James, Ron" <Rjames AT ATSGROUP DOT COM>; Date: Tue, 6 Apr 1999 10:08:56 -0500; Setting reclamation to 50% only makes since if you have 2 or more tapes at or above 50%. Ron James Network Management Specialist Premiere Conferencing 50%? As I understand it, actually useful. If you; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-04/msg00185.html (12,421 bytes)

Current List: 1 - 8
Page: [1]