Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 52097 invoked from network); 10 Dec 2009 12:59:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Dec 2009 12:59:28 -0000 Received: (qmail 76150 invoked by uid 500); 10 Dec 2009 12:59:27 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 76077 invoked by uid 500); 10 Dec 2009 12:59:27 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 76066 invoked by uid 99); 10 Dec 2009 12:59:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2009 12:59:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com designates 209.85.218.214 as permitted sender) Received: from [209.85.218.214] (HELO mail-bw0-f214.google.com) (209.85.218.214) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2009 12:59:19 +0000 Received: by bwz6 with SMTP id 6so6159322bwz.11 for ; Thu, 10 Dec 2009 04:58:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=C8WtzVevOoYENNiK3bA+5IrhAqARHdxg+6v+TmEdQ2E=; b=sA1chMndzEzsQBlIAek/lT4RCMNpwpC7PSx6jvZBwZBksFrBxAgfmyXTQ9DFQfN1xW 1kXlYERn76WX9td4XLfKSFmCOcC+byIt+YteCrFXtj66bSDpBBvMuHBA5VAhqaA/XS4U DlTMbV27sRwfxPJR+2Ty7NWAXkG0cls9dVbG8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=ZHAEdNJ/JY8fGzj63+e8nHE8OHypuRMJmnrm3ztFCDd+Z8B8j91pLtyaeHdr8iB7Jb SdN3by8DdH7Zlad91a0r2V+9zlg9hGiKhLwilGBRTRovMHoXSeahdekIaWNtp93gLYwe Io4/LTfmL4DW3iAxhScB1PuR19dy4eWV6AZJY= MIME-Version: 1.0 Received: by 10.204.152.154 with SMTP id g26mr3273298bkw.54.1260449939105; Thu, 10 Dec 2009 04:58:59 -0800 (PST) In-Reply-To: References: From: Jukka Zitting Date: Thu, 10 Dec 2009 13:58:39 +0100 Message-ID: <510143ac0912100458o11a2ddbmfe363a1640ccc517@mail.gmail.com> Subject: Re: RepositoryCopier requires shutdown of source repositoy? To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Thu, Dec 10, 2009 at 1:34 PM, Samuel Cox wrote: > I need to backup our repository periodically and anticipate using the > RepositoryCopier class. =A0I was curious that 2 of the methods in the Jav= adoc > mention that the source repo must not be modified during the call; howeve= r, > the others do not. =A0Is it possible for me to perform a backup while sti= ll > allowing JCR API calls that modify the repo? =A0In other words, will > RepositoryCopier somehow lock/cache/unlock/flush/etc for me? > =A0I'm guessing it won't/can't do this. You're right, the RepositoryCopier doesn't contain any protection against concurrent changes to the repository. If you allow clients to modify the repository while you're backing it up, you may end up with an inconsistent backup. BR, Jukka Zitting