Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Recovery\s+Log\s+size\s+\/\s+roll\s+forward\s+benefits\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Recovery\s+Log\s+size\s+\/\s+roll\s+forward\s+benefits\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: Recovery Log size / roll forward benefits (score: 1): Author: "Garrison, Tony" <Anthony.Garrison AT USAA DOT COM>; Date: Thu, 2 Aug 2001 13:20:37 -0500; We use Roll-forward here. This is primarily due to the fact that we can set the db trigger to backup the db if the log reaches a predefined percentage. This is extremely important due to the size of; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-08/msg00092.html (15,760 bytes)
2. Re: Recovery Log size / roll forward benefits (score: 1): Author: Lindsay Morris <lmorris AT SERVERGRAPH DOT COM>; Date: Thu, 2 Aug 2001 14:28:51 -0400; Thanks for your input, Tony. If I understand you, you're concerned that your log might fill up, so you set logmode roll-forward just because dbbackuptrigger requires it. Then dbbackuptrigger kicks of; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-08/msg00093.html (17,503 bytes)
3. Re: Recovery Log size / roll forward benefits (score: 1): Author: Paul Zarnowski <vkm AT CORNELLC.CIT.CORNELL DOT EDU>; Date: Thu, 2 Aug 2001 16:16:15 -0400; Lindsay, et al, It is very possible to lose your database but not the log (we have done it). The database can become corrupted through means other than hardware failure, though even a hardware-initia; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-08/msg00106.html (16,499 bytes)
4. Re: Recovery Log size / roll forward benefits (score: 1): Author: Lindsay Morris <lmorris AT SERVERGRAPH DOT COM>; Date: Thu, 2 Aug 2001 17:28:54 -0400; Thanks for the insight, Paul. In your long experience, you've probably seen everything bad that can happen. I was assuming that software corruption was rare. If I ask the list how rare it is, I'm sur; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-08/msg00114.html (19,485 bytes)
5. Re: Recovery Log size / roll forward benefits (score: 1): Author: Paul Zarnowski <vkm AT CORNELLC.CIT.CORNELL DOT EDU>; Date: Thu, 2 Aug 2001 19:37:19 -0400; I think it is pretty rare, Linday. I count myself as being very unlucky in that regard. But as unlikely as it can get, I'd think you would still want to protect yourself against the possibility. Perh; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-08/msg00119.html (19,050 bytes)
6. Re: Recovery Log size / roll forward benefits (score: 1): Author: Sheelagh Treweek <sheelagh.treweek AT COMPUTING-SERVICES.OXFORD.AC DOT UK>; Date: Fri, 3 Aug 2001 08:54:02 +0100; I agree with Paul, it is pretty rare - but it can happen. You can't guarantee to prevent software or hardware corruption : you just have to plan the recovery path ... The last corruption I had was on; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-08/msg00130.html (12,704 bytes)
7. Re: Recovery Log size / roll forward benefits (score: 1): Author: Lindsay Morris <lmorris AT SERVERGRAPH DOT COM>; Date: Fri, 22 Jun 2001 10:54:43 -0400; I'm with Kelly in thinking that roll-forward is unnecessary in most cases. The TSM admin guide seems to recommend roll-forward: "To get the best protection for your TSM data, you should use ... mirro; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-06/msg00807.html (15,771 bytes)

Current List: 1 - 7
Page: [1]