Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 90303 invoked from network); 16 May 2008 05:33:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 May 2008 05:33:59 -0000 Received: (qmail 56822 invoked by uid 500); 16 May 2008 05:34:00 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 56788 invoked by uid 500); 16 May 2008 05:34:00 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 56763 invoked by uid 99); 16 May 2008 05:34:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 May 2008 22:34:00 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=FS_REPLICA,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.19.7] (HELO sineb-mail-2.sun.com) (192.18.19.7) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2008 05:33:04 +0000 Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4G5XtOA006083 for ; Fri, 16 May 2008 05:34:05 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K0Y00J014EUD500@mail-apac.sun.com> (original mail from V.Narayanan@Sun.COM) for derby-user@db.apache.org; Fri, 16 May 2008 13:31:58 +0800 (SGT) Received: from [129.158.228.208] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K0Y009U24P48A09@mail-apac.sun.com> for derby-user@db.apache.org; Fri, 16 May 2008 13:31:57 +0800 (SGT) Date: Fri, 16 May 2008 11:03:05 +0530 From: Narayanan Subject: Re: Replicating Derby Database Files In-reply-to: <44ed9df20805151132p1c8aeedbg6641b012b7968927@mail.gmail.com> Sender: V.Narayanan@Sun.COM To: Derby Discussion Message-id: <482D1C91.9070009@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <44ed9df20805150919s30c6f4a5k855ba32936edfad3@mail.gmail.com> <482C6F6D.1000008@sun.com> <44ed9df20805151132p1c8aeedbg6641b012b7968927@mail.gmail.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080505) X-Virus-Checked: Checked by ClamAV on apache.org 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 > 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 >>> >>> >> > > > >