Return-Path: 
 <users-return-17675-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org>
X-Original-To: apmail-subversion-users-archive@minotaur.apache.org
Delivered-To: apmail-subversion-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 35264104FB
	for <apmail-subversion-users-archive@minotaur.apache.org>;
 Fri, 12 Apr 2013 13:56:35 +0000 (UTC)
Received: (qmail 45732 invoked by uid 500); 12 Apr 2013 13:56:34 -0000
Delivered-To: apmail-subversion-users-archive@subversion.apache.org
Received: (qmail 45684 invoked by uid 500); 12 Apr 2013 13:56:34 -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 45677 invoked by uid 99); 12 Apr 2013 13:56:34 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 13:56:34 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of marcus.james@gmail.com
 designates 209.85.215.53 as permitted sender)
Received: from [209.85.215.53] (HELO mail-la0-f53.google.com) (209.85.215.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 13:56:27 +0000
Received: by mail-la0-f53.google.com with SMTP id fp13so2485089lab.26
        for <users@subversion.apache.org>;
 Fri, 12 Apr 2013 06:56:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=/RPcgC5ZW3TqS1vZrKvMbuRJ+9p4uZhYca+NY/CxWvs=;
        b=fG0NLSMxVL3M1mWNTAksq3PNkEmTUn8glo+sTYDDsXVF6MuHyyBChzfy6lJ/86BE2F
         W5w8ox1Y9oiIxHVAC/ogijs34sVIQew6dsKKaDjcH7yvAAJ+/T1KAzDAuw3RHpzBaium
         X9SiHsVPIf6A8NdYedhlSKsYQx4DGjOH8Rybilm995c4gcM3q3oOAssbzLDGmgoDTtV1
         +zTL5JgDiT/ft+vWLKpKxuTcGEnJwyj+mvkO/mzuc8zji/wSISNaiVdrNxbzXXEeWchV
         dQkzkCnTuf/gIvQbascQWLlsj9f5+kEaIey0NYmdvmBdZ5XNLv4nKFJCLDSTRCHG018O
         Ot8A==
MIME-Version: 1.0
X-Received: by 10.152.4.131 with SMTP id k3mr3027308lak.26.1365774967365; Fri,
 12 Apr 2013 06:56:07 -0700 (PDT)
Received: by 10.112.5.36 with HTTP; Fri, 12 Apr 2013 06:56:07 -0700 (PDT)
Date: Fri, 12 Apr 2013 09:56:07 -0400
Message-ID: 
 <CAM54t=YtEf0wpuNREpY-7Y4q4gd3XDb1NnvZG_uZPsdd+MW5Jg@mail.gmail.com>
Subject: Dealing with binaries and migrating a 36G repository
From: James Marcus <marcus.james@gmail.com>
To: users@subversion.apache.org
Content-Type: multipart/alternative; boundary=089e013d1730c5e56c04da2a4313
X-Virus-Checked: Checked by ClamAV on apache.org

--089e013d1730c5e56c04da2a4313
Content-Type: text/plain; charset=ISO-8859-1

Hi,
I have been trying to migrate a hosted repository that is 36G.  This is
difficult because we have offshore teams, so the repository is almost
always active.  Before I got here, it seems that someone had the build
process check in each binary after it was built.... Urgh!

I'm looking for tips on migrating this repository?

I have a list of the revisions that are greater then 10M

I have looked for svndump filters to exclude certain revisions, and
considered other migration paths, but exporting 36G then scp'ing it off to
another host takes a long time and I think it would be best if I  could
export everything except the binaries.. Is there a way to do this with
svndump?

Current server is running:

[dagger]$ svn --version
svn, version 1.5.1 (r32289)

Target servers is running 1.7

Both servers are Linux.

Thanks,
James

--089e013d1730c5e56c04da2a4313
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div style>I have been trying to migrate a hosted repos=
itory that is 36G. =A0This is difficult because we have offshore teams, so =
the repository is almost always active. =A0Before I got here, it seems that=
 someone had the build process check in each binary after it was built.... =
Urgh!</div>
<div style><br></div><div style>I&#39;m looking for tips on migrating this =
repository?</div><div style><br></div><div style>I have a list of the revis=
ions that are greater then 10M</div><div style><br></div><div style>I have =
looked for svndump filters to exclude certain revisions, and considered oth=
er migration paths, but exporting 36G then scp&#39;ing it off to another ho=
st takes a long time and I think it would be best if I =A0could export ever=
ything except the binaries.. Is there a way to do this with svndump?</div>
<div style><br></div><div style>Current server is running:=A0</div><div sty=
le><br></div><div style><div>[dagger]$ svn --version</div><div>svn, version=
 1.5.1 (r32289)</div><div><br></div><div style>Target servers is running 1.=
7</div>
<div style><br></div><div style>Both servers are Linux.</div><div style><br=
></div><div style>Thanks,</div><div style>James</div><div style><br></div><=
/div></div>

--089e013d1730c5e56c04da2a4313--