Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 97726 invoked from network); 25 Nov 2010 11:17:04 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Nov 2010 11:17:04 -0000 Received: (qmail 95004 invoked by uid 500); 25 Nov 2010 11:17:03 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 94794 invoked by uid 500); 25 Nov 2010 11:17:03 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 94786 invoked by uid 99); 25 Nov 2010 11:17:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Nov 2010 11:17:02 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of afters.mail@gmail.com designates 209.85.214.196 as permitted sender) Received: from [209.85.214.196] (HELO mail-iw0-f196.google.com) (209.85.214.196) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Nov 2010 11:16:56 +0000 Received: by iwn6 with SMTP id 6so131537iwn.11 for ; Thu, 25 Nov 2010 03:16:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=qZMgtjEL46wiTVJnSx6vqUSOQnBmnnHI0kjgKxBVJfo=; b=gYZi49KZWuYKxm9tQdtBxSl4F/RKx0XRUgj9X20d5OgQuI3WXKTSUid/DHMnNzd/+x GJkmk6E1/49AsCmycpHwdrWXIpqxhyPFROwb8oY/K2u6jLC1WPBXH9WVZO6rmOqWJ/3j 8uUp6gzgSPGXtsps5YcoY7GI2ME0fLjkSGQ2w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iRPqkskUCm/Civ0LfAVU0bSQIcQ+yJfVqbEeNTDzUzFynn6wEj7eeUkEDGd6Ydv0zt uHQwRWPZgS3Vk5ave+8tF4j6rUPPWgsH4C6/6OMb9Juqw4zzdY8AdA4PIMz/sFpC1uw+ 3ZWZDgmCjMjAgqWBMGLsbwAZ0hPskCza4qhNc= MIME-Version: 1.0 Received: by 10.231.192.76 with SMTP id dp12mr410028ibb.185.1290683795606; Thu, 25 Nov 2010 03:16:35 -0800 (PST) Received: by 10.231.215.3 with HTTP; Thu, 25 Nov 2010 03:16:35 -0800 (PST) Date: Thu, 25 Nov 2010 13:16:35 +0200 Message-ID: Subject: Incremental backups From: afters To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016367d6b72278cc70495debd41 --0016367d6b72278cc70495debd41 Content-Type: text/plain; charset=ISO-8859-1 hi folks, As I'm about to implement it myself, I'm curious to know how people handle incremental backups for their DB's. The straight-forward way, as I see it, is to shutdown couch and use a tool like rsync or duplicity to backup db files. It should do the job well, and as an added bonus, it could also be used to backup views. Does anyone know if a similar backup could be done while the couch is still on (and the db is being updated)? Does anyone do incremental backups using replication? a. --0016367d6b72278cc70495debd41--