db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oystein.Grov...@Sun.COM (Øystein Grøvlen)
Subject Re: [jira] Commented: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.
Date Tue, 02 Aug 2005 09:30:28 GMT
>>>>> "ST" == Suresh Thalamati <suresh.thalamati@gmail.com> writes:

    ST> Suresh Thalamati wrote:
    >> I think one of the following options may be more acceptable:
    >> 1)  make backup/archive  mode process  wait until
    >> all the transaction that has the non-logged

    >> operations  are  committed.
    >> or
    >> 2) convert the non-logged operation to logging mode after
    >> flushing the containers , once the backup starts.

    >> My  preference is  option 1)  , it  might be  less  complicated than
    >> option 2).

    ST>  On my way back home ,  I  was thinking  may be better option  is :

    ST>     3) to make backup/(log archive  mode enabling) fail , if there are
    ST> uncommitted transactions with non-logged operations ?  instead of

    ST>         making backup  process wait  for the non-logged  operations to
    ST> commit.

I think your last suggestion is a good idea.  If, for example, an
import takes very long, it might be better to flag the conflict
immediately instead of executing the backup several hours later.


View raw message