Sai Pullabhotla wrote:
Rick,
Thanks for the reply. I briefly looked at the 10.4. documentation and
it seems that the replication is designed for Derby running as a
network server. Is this true?
No it is not true. You can run replication in the embedded mode also.
Our application runs Derby in embedded mode and our customers are
wanting to replicate the application on a regular basis (as and when
any file/data changes) to the HA systems. What would be our options
here to keep the Derby database up-to-date on the HA system?
I am worried about what you mean by up to date here. You see replication
in derby is
asynchronous, we only promise transaction consistency. You can read some
more on replication
in derby here
http://wiki.apache.org/db-derby/ReplicationWriteup
You can replicate an existing embedded database following the steps
listed here. You will find
the combination of the documentation in derby and this wiki
comprehensive, feel free to raise
any doubts you have.
Narayanan
Thanks and Regards,
Sai Pullabhotla
On Thu, May 15, 2008 at 12:14 PM, Rick Hillegas
<[EMAIL PROTECTED]> wrote:
Hi Sai,
Single-node master/slave replication with manual failover was added to Derby
in version 10.4. You should not try to manually copy a Derby database which
is in use.
Hope this helps,
-Rick
Sai Pullabhotla wrote:
Hello,
We have a need to replicate Derby Database from the production system
to the High Availability system. The software we use monitors for any
file changes on the production system and replicates the changed files
to the High Availability system. My question is -
Is it safe to copy the Derby data files to another system while the
database is in use on the source system? Will the database on the
destination still be usable if we do this?
Thanks & Regards,
--
Sai Pullabhotla
www.jMethods.com
