Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First draft of Docs on Backup #406

Merged
merged 11 commits into from Jun 30, 2016
Merged

Conversation

ttmc
Copy link
Contributor

@ttmc ttmc commented Jun 27, 2016

  • A first draft of the section "Backing Up & Restoring Data"
  • Moved the "Nodes, Clusters & Federations" (terminology) section from under "Topic Guides" to under "BigchainDB Clusters & Federations"
  • Split the section "Set Up and Run a Federation" into separate sections under "BigchainDB Clusters & Federations", because it was going to be too long once all the documentation-to-come came. One of those new separate sections is the new backup section.

@ttmc ttmc self-assigned this Jun 27, 2016
@ttmc ttmc changed the title First draft First draft of Docs on Backup Jun 27, 2016
@codecov-io
Copy link

codecov-io commented Jun 27, 2016

Current coverage is 89.57%

Merging #406 into master will not change coverage

@@             master       #406   diff @@
==========================================
  Files            18         18          
  Lines          1257       1257          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits           1126       1126          
  Misses          131        131          
  Partials          0          0          

Sunburst

Powered by Codecov. Last updated by d6ea728...ca746f6

@trentmc trentmc mentioned this pull request Jun 27, 2016
2 tasks
@r-marques
Copy link
Contributor

👍

@ttmc
Copy link
Contributor Author

ttmc commented Jun 29, 2016

I still want to add some notes about:

  • Using RAID or similar on each node so that if one of the hard drives fails, the node keeps working as if nothing happened, and the failed hard drive can be replaced.
  • Using RethinkDB's existing replication and server tags capabilities to create a set of dedicated "backup-only nodes" --- which would be functionally very similar to continuous backup.

so maybe this won't get merged until after the upcoming version-release.

@ttmc
Copy link
Contributor Author

ttmc commented Jun 29, 2016

@r-marques could you look at the two short subsections I added in commit 877937c ? If you're okay with what I wrote there, then I'll merge this pull request.

@r-marques
Copy link
Contributor

👍

@ttmc ttmc merged commit a78243d into master Jun 30, 2016
@ghost ghost removed the when: In progress label Jun 30, 2016
@ttmc ttmc deleted the feat/283/document-existing-backup-options branch July 29, 2016 12:39
sbellem pushed a commit to sbellem/bigchaindb that referenced this pull request Oct 24, 2016
…xisting-backup-options

First draft of Docs on Backup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants