Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4A422821.4010704@sun.com>
Date: Wed, 24 Jun 2009 14:20:33 +0100
From: Alan Burlison <Alan.Burlison@sun.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090505)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Replication question: docs not clear
References: <4A4219D8.4010005@sun.com> <4A421C91.9000003@sun.com>
 <wjo8ws71dblh.fsf@sun.com>
In-Reply-To: <wjo8ws71dblh.fsf@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Knut Anders Hatlen wrote:

> Both of those scenarios should work. Whether or not the server is
> running while the database is copied doesn't really matter, but the
> database itself must not be booted.

OK, thanks.  Most other databases I've used would get a bit confused if 
you started fiddling with the contents of their data file directories 
while they were running, it might be worth noting in the docs that this 
is OK for Derby.

> By the way, there is a documentation request that describes a slightly
> easier procedure to start replication. See
> https://issues.apache.org/jira/browse/DERBY-4196. I don't know if it is
> relevant in your setup, but I thought I'd mention it in case it could
> simplify things.

Yes, it probably is relevant.  I assume that if you start the master 
database with startMaster=true it locks the database until the client is 
running, or do you have to manually make sure no clients connect until 
after the slave is up and running?

-- 
Alan Burlison
--