Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 n.breunese@vpro.nl does not designate 193.138.205.158 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Best way to backup and restore after going offline
From: Nils Breunese <n.breunese@vpro.nl>
In-Reply-To: 
 <CALfshb3uoiqZgH2LjPQmDqtRbOcpujL6zcuXc6P=xihMbgMmsw@mail.gmail.com>
Date: Tue, 7 May 2013 23:59:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <26DFFECD-2D89-45EC-A003-E824445F2BB8@vpro.nl>
References: 
 <CALfshb3uoiqZgH2LjPQmDqtRbOcpujL6zcuXc6P=xihMbgMmsw@mail.gmail.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>

andy e <virtualandy@gmail.com> wrote:

> We're trying to replicate a database while connected to the great big
> Internet (the npm repo, actually). But after it is finished =
replicating we
> need to take our copy and run it in a different and offline =
environment.
>=20
> What's the best way to proceed? Just backup the database file(s), then =
copy
> them over to our offline instance (we do this via disc/usb/etc). =
Anything
> to be aware of when doing this ("make sure to grab this file", "run =
this
> command first before importing")?

A single .couch file represents a single database. You can just copy =
over these files. There's even no need to shut down the source instance =
(unlike when using something like MySQL for instance).

If you also want to copy over the generated view indexes, you can also =
copy over the hidden directories in the data directory. This only makes =
sense if regenerating these indexes on the target instance takes a lot =
of time.

> Is there any way to pick up just the changed documents, so that the =
second
> time we do this, we only have to transfer what is new (versus copying =
the
> entire thing again)? That's not too big of a deal if so but would be a
> nice-to-have.

Updating your online copy could be done by rerunning replication from =
npm to your online instance. You could use rsync to just copy over the =
differences in the file at the block level. Or you could start a second =
CouchDB instance on the offline machine (use a different IP address =
and/or port) using the updated database files on the transfer medium and =
run replication between those two CouchDB instances on the offline =
machine.

HTH, Nils.=