Hi Joan,
Thank you very much for getting back to me! So I'll implement the script to archive all the files in our main data directory. Thank you again. Chris Mantell Programmer Athinoula A Martinos Center for Biomedical Imaging Massachusetts General Hospital Building 149 - South Central Charlestown, MA 02129 [email protected] ________________________________ From: Joan Touzet <[email protected]> Sent: Wednesday, January 16, 2019 6:57:06 PM To: [email protected] Subject: Re: Backing Up CouchDB 2.2 External Email - Use Caution Hi Chris, http://docs.couchdb.org/en/latest/maintenance/backups.html has everything you need. Sadly this documentation didn't land in time for our 2.3.0 release. These instructions are applicable for any 2.x release. All the best, Joan ----- Original Message ----- > From: "Christopher Arthur Mantell" <[email protected]> > To: [email protected] > Sent: Wednesday, January 16, 2019 5:19:48 PM > Subject: Backing Up CouchDB 2.2 > > Hi, > > > With Couch 1.7, we have a python script that makes an archive of all > our .couch and .view files in /usr/lib/couchdb for back up. > > > With Couch 2.2, there are shards directories and in order to make an > archived backup, would I have to copy all the files in the shards > directories? > > > Any suggested approach to backing up our Couch files apart from > replication? > > > I'm curious if it's possible to use these archived files to make an > exact copy on a brand new CouchDB server. > > > Thank you, > > > Chris Mantell > > Programmer > > Athinoula A Martinos Center for Biomedical Imaging > Massachusetts General Hospital > Building 149 - South Central > Charlestown, MA 02129 > [email protected] > > > The information in this e-mail is intended only for the person to > whom it is > addressed. If you believe this e-mail was sent to you in error and > the e-mail > contains patient information, please contact the Partners Compliance > HelpLine at > http://www.partners.org/complianceline . If the e-mail was sent to > you in error > but does not contain patient information, please contact the sender > and properly > dispose of the e-mail. >
