I guess I'm not sure as to what's going on with the file as it is being copied and changed at the same time. I assume that the file must be append-only for this to work, but are ALL db changes indeed append only? I remember reading that updating a tree-node also updates all its ancestors (to track latest seq) and I wonder if those changes are also append only.
On 25 November 2010 13:21, Robert Newson <[email protected]> wrote: > just copy the file, there's no need to stop couchdb. Replication would > be another way, of course. > > On Thu, Nov 25, 2010 at 11:16 AM, afters <[email protected]> wrote: > > 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. > > >
