Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of sven.helmberger@gmx.de
 designates 213.165.64.20 as permitted sender)
Message-ID: <49DB1E78.6050500@gmx.de>
Date: Tue, 07 Apr 2009 11:35:52 +0200
From: Sven Helmberger <sven.helmberger@gmx.de>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: Using rsync to backup a couchdb database
References: <49DAF78B.3060805@michevan.id.au>
In-Reply-To: <49DAF78B.3060805@michevan.id.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Evan McLean schrieb:
> In one of the recent podcasts, it was mentioned that to backup a couchdb 
> database you can just copy the file.  I understand how this works with 
> using cp as the important header blocks are in the start of the file and 
> the rest is append only.
> 
> It was also stated that you could use rsync and I wasn't so sure.  Is it 
> safe to assume that rsync starts at the start of the file and works it's 
> way forward like a regular copy program would?  Not that familiar with 
> the inner workings of it.
> 
> E.

Since rsync just uses clever interleaved hashing to find out which parts 
of the files have changed, it will find out that there was only stuff 
appended to the files and just replicate that.

I don't see why this shouldn't work.

Regards,
Sven Helmberger