Return-Path: 
 <users-return-7910-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org>
Delivered-To: apmail-subversion-users-archive@minotaur.apache.org
Received: (qmail 61432 invoked from network); 28 Feb 2011 18:50:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 28 Feb 2011 18:50:33 -0000
Received: (qmail 64413 invoked by uid 500); 28 Feb 2011 18:50:32 -0000
Delivered-To: apmail-subversion-users-archive@subversion.apache.org
Received: (qmail 64359 invoked by uid 500); 28 Feb 2011 18:50:29 -0000
Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@subversion.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@subversion.apache.org>
List-Post: <mailto:users@subversion.apache.org>
List-Id: <users.subversion.apache.org>
Delivered-To: mailing list users@subversion.apache.org
Received: (qmail 64352 invoked by uid 99); 28 Feb 2011 18:50:29 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Feb 2011 18:50:29 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of dcchapman@acm.org designates
 64.142.16.245 as permitted sender)
Received: from [64.142.16.245] (HELO a.mail.sonic.net) (64.142.16.245)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Feb 2011 18:50:22 +0000
Received: from [192.168.1.115] (70-36-212-24.dsl.static.sonic.net
 [70.36.212.24])
	(authenticated bits=0)
	by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id p1SInxQJ017729
	(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO);
	Mon, 28 Feb 2011 10:50:00 -0800
Message-ID: <4D6BEE3F.7020208@acm.org>
Date: Mon, 28 Feb 2011 10:49:35 -0800
From: David Chapman <dcchapman@acm.org>
Organization: Chapman Consulting
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: James Ralston <qralston+ml.svn-users@andrew.cmu.edu>
CC: users@subversion.apache.org
Subject: Re: can "svnadmin dump" tolerate read-only repository access?
References: <DC2920A02FB84A20096F15BA@hamachi.sei.cmu.edu>
In-Reply-To: <DC2920A02FB84A20096F15BA@hamachi.sei.cmu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 2/28/2011 10:37 AM, James Ralston wrote:
> <snip>
> Question: if I "svnadmin dump" a repository, is it safe to allow
> read-only access to the repository while the dump is in progress?  Or
> is it the case that permitting even read access could interfere with
> the "svnadmin dump" operation?
>
> I ask because it will take a non-trivial amount of time to perform
> svnadmin dump/load operations on all of Subversion repositories.  If
> we can at least permit read-only access while this upgrade is in
> progress, that will have much less of an impact on our users then it
> we have to block all access during the upgrade...
>

A "hot copy" by definition is one that will safely allow read-only 
access while the backup is in progress.

-- 
     David Chapman         dcchapman@acm.org
     Chapman Consulting -- San Jose, CA