Re: Recovery Log problems
1999-09-02 13:56:37
Subject: |
Re: Recovery Log problems |
From: |
"Richard C. Dempsey" <dempsey AT KODAK DOT COM> |
Date: |
Thu, 2 Sep 1999 13:56:37 -0400 |
My recovery log is big enough to hold a full day's transactions at 80% of
its space. I schedule my DB backups and do not rely on the DBTRIGGER.
I find rollforward mode to be useful for getting the server back to a time
after the last DB backup and before my problem occurred.
I agree that DB backups occurring at odd times is a recipe for random
failure.
Rich
At 12:22 PM 9/2/99 -0600, you wrote:
> I agree with Steve. When the feature came out I thought about using
> it instead of mirroring my database but I like to keep things simple.
> I didn't want database backups occuring at odd times since I only have
> two tape drives and I definitely didn't want to continuously mess
> around with the recovery log.
> Jim Sporer
> University Of Wisconsin
>
>
>
>
>______________________________ Reply Separator
_________________________________
>Subject: Re: Recovery Log problems
>Author: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at IPNET
>Date: 9/2/99 10:13 AM
>
>
>> I also had to restore my DB twice. Both times I was not able to roll
>> forward.
>> I am also wondering why I bother to set it since it has not helped me in
>> the past.
>
>I run in normal mode after trying rollforward for a while, and having it
>cause me more problems than it was worth. I had a 5GB recovery log, and
>DBbackup's triggered in the middle of the night did not complete prior to
>the log filling, since client backups were running, and ADSM did not pay
>enough attention to the more critical DBbackup. When it crashes, one must
>extend the log in standalone mode, and my server would then take over 4
>hours to come up.
>
>With mirrored logs, I dunno why one would bother with the problems
>associated with rollforward mode. In the case were both logs go bad,
>rollforward recovery will not work anyway.
>
>We live with the fact that if we have to do a restoredb, we will have to
>re-backup all of the work since the last dbbackup.
>
>...just my humble opinions...
>
>Steve (unVMix Systems Programmer/Dude) Roder
>(tkssteve AT ubvm.cc.buffalo DOT edu | tkssteve AT acsu.buffalo DOT edu |
>(716)645-3564 ,
> | http://ubvm.cc.buffalo.edu/~tkssteve)
>
>
Richard C. Dempsey email: dempsey AT kodak DOT com
Public Online Services pager: 716-975-3539
11th Floor, Bldg 83, RL phone: 716-477-3457
Eastman Kodak Company fax: 716-722-3885
Rochester, NY 14650-2203
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: Recovery Log problems, (continued)
- Re: Recovery Log problems, ADSML
- Re: Recovery Log problems, Richard C. Dempsey
- Re: Recovery Log problems, Joshua Bassi
- Re: Recovery Log problems, arhoads
- Re: Recovery Log problems, malkit
- Re: Recovery Log problems, arhoads
- Re: Recovery Log problems, malkit
- Re: Recovery Log problems, Steven P Roder
- Re: Recovery Log problems, Richard C. Dempsey
- Re: Recovery Log problems, Prather, Wanda
- Re: Recovery Log problems,
Richard C. Dempsey <=
- Re: Recovery Log problems, James SPORER
- Re: Recovery Log problems, Steven P Roder
- Re: Recovery Log problems, arhoads
- Re: Recovery Log problems, arhoads
- Re: Recovery Log problems, Steven P Roder
- Re: Recovery Log problems, Bill Colwell
- Re: Recovery Log problems, ADSM : Dist Stor Manager [mailto:ADSM-L
|
|
|