[GitHub] [couchdb-documentation] piripillo opened a new issue #554: couchdb disaster recovery

[GitBox <gi...@apache.org>]

piripillo opened a new issue #554:
URL: https://github.com/apache/couchdb-documentation/issues/554


   [NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ )
   
   ## Description
   i have a couchdb 3.1 cluster with 2 nodes VM and i backup daily data and etc folder
   i would like to create, starting from backup same servers and data in a new environment (i would like to simulate a complete down on the old infrastructure)
   i setup two couchdb, than i restore the 2 folder, than i change the ipaddress under vm.args
   i add and remove the ip on the cluster to matching the actual configuration
   https://docs.couchdb.org/en/stable/cluster/nodes.html#adding-a-node
   
   in the interface i can see all the databases but are in status [This database failed to load.]
   in the log file i have [Failed to ensure auth ddoc _users/_design/_auth exists for reason: read_failure]
   if i try to browse _users/_design/_auth i receave
   error	"internal_server_error"
   reason	"No DB shards could be opened."
   ref	2822102114
   
   there is a step by step guide to do this?
   
   [NOTE]: # ( Describe the problem you're encountering. )
   [TIP]:  # ( Do NOT give us access or passwords to your actual CouchDB! )
   
   ## Steps to Reproduce
   
   [NOTE]: # ( Include commands to reproduce, if possible. curl is preferred. )
   
   ## Expected Behaviour
   disaster solution for a cluster starting from backup
   
   [NOTE]: # ( Tell us what you expected to happen. )
   
   ## Your Environment
   
   [TIP]:  # ( Include as many relevant details about your environment as possible. )
   [TIP]:  # ( You can paste the output of curl http://YOUR-COUCHDB:5984/ here. )
   
   * CouchDB version used:3.1
   * Browser name and version:
   * Operating system and version:ubuntu 18
   
   ## Additional Context
   
   [TIP]:  # ( Add any other context about the problem here. )
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [couchdb-documentation] wohali commented on issue #554: couchdb disaster recovery

[GitBox <gi...@apache.org>]

wohali commented on issue #554:
URL: https://github.com/apache/couchdb-documentation/issues/554#issuecomment-635461487


   The problem you're facing is that the `-name` parameter that you're changing is used by CouchDB internally for every database to log where the shards are stored.
   
   If your entries in `-name` were **DNS entries**, not IP addresses, you'd do exactly what you said, change DNS, and everything would be fine.
   
   If you insist on using IP addresses, you're going to have to edit the `_dbs` document for every database you have, and change all instances of every IP address for all machines to the new IP address. Not only is this error prone, it's a pain in the arse :)
   
   So, switch to DNS, and always put `-name couchdb@couchdb-1.myhost.com` in `vm.args`, not IP addresses.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [couchdb-documentation] wohali commented on issue #554: Document couchdb disaster recovery process

[GitBox <gi...@apache.org>]

wohali commented on issue #554:
URL: https://github.com/apache/couchdb-documentation/issues/554#issuecomment-809686158


   We addressed the `-name` portion of this in #596.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org