db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: Derby Transaction Log Shipping
Date Fri, 08 Feb 2008 08:05:09 GMT
Duncan Groenewald <dagroenewald@optusnet.com.au> writes:

> Thanks - the specification looks like its close to what I would like.
> The model I work from is one used by Sybase (and possibly  others)
> where you can specify a database dump and a separate  transaction log
> dump at defined intervals using a script or some  other programmatic
> method.  From what I can tell its not possible to  do this with Derby,
> since you can only dump the database and not the  logs.  Its also
> unclear how you would load a log file on its own.
>
> What I would like to see is two additional commands added to dump
> transaction logs to specified directory or file name and another
> command to load a transaction log file from a specified location/
> file.  Ideally a transaction log file load should function much the
> same way a normal user does to allow concurrent user access while
> loading a transaction log file.

Not exactly what you want (it won't allow concurrent user access while
loading the transaction log), but you may achieve something similar with
log archiving and roll-forward recovery, combined with some creative
scripts. I haven't tried it myself, but you may get some ideas here:
http://db.apache.org/derby/docs/dev/adminguide/cadminrollforward.html

-- 
Knut Anders

Mime
View raw message