[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: how to backup repository with all history?

From: James <oldyoungguy88_at_yahoo.com>
Date: Tue, 10 Feb 2015 04:25:37 +0000 (UTC)

I have few repositories in my svn-root directory. I have put a conf folder at the same level as other repositories. that conf folder contains a authz and a passwd file which are shared by all repositories. By doing this I can setup users and their privilege in one place. But because of this conf folder, I cannot do hotcopy automatically. I am thinking just tar all of them daily. 

My purpose of backup is just in case my machine die. So how big the difference will be for my tar approach and the hotcopy?
     From: Nico Kadel-Garcia <nkadel_at_gmail.com>
 To: James <oldyoungguy88_at_yahoo.com>
Cc: "users_at_subversion.apache.org" <users_at_subversion.apache.org>
 Sent: Monday, February 9, 2015 10:54 PM
 Subject: Re: how to backup repository with all history?
On Mon, Feb 9, 2015 at 9:44 PM, James <oldyoungguy88_at_yahoo.com> wrote:

> I read there are at least three ways to do backup:
> 1. hotcopy;
> 2. dump;
> 3. incremental backup;
> I am just wondering are them all have the history included? If I restore any
> of them, I will get everything, including the history or previous revisions,
> back?

In theory, yes. In practice..... there are some operations, such as
dumping and reloading with large binaries or sensitive data excluded,
that are designed to *alter* history and clear undesired material This
can cause oddness if you have a linked slave, which is yet another way
to do backup. There are also operations that will, once a history is
corrupted, merely replicate the corrupted history. And remember that
the deprecated Berkeley DB logs from older Subversion environments are
not cross-platrofm compatible, so bringing those to another host can
cause trouble.

Received on 2015-02-10 05:26:12 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.