[docs] added backup policy #7084
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✔️ Deploy preview for dgraph-docs ready! 🔨 Explore the source changes: ffde051 🔍 Inspect the deploy logs: https://app.netlify.com/sites/dgraph-docs/deploys/5fcfbd18d537cd0008092f34 😎 Browse the preview: https://deploy-preview-7084--dgraph-docs.netlify.app |
aaroncarey
approved these changes
Dec 8, 2020
There was a problem hiding this comment.
Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @aaroncarey, @danielmai, @MichaelJCompton, and @OmarAyo)
wiki/content/deploy/production-checklist.md, line 93 at r1 (raw file):
Quoted 6 lines of code…
### Backup Policy A backup policy is a predefined, set schedule used to schedule backups of information from business applications. For Dgraph, backups occur when data is copied to disk using the `backup ee` tool. A backup policy helps to ensure data recoverability in the event of accidental data deletion, data corruption a system outage. We **strongly** recommend that you have a backup policy in place before moving your application to the production phase, and we also suggest that you have a backup policy even for pre-production apps supported by Dgraph database instances running in development, staging, QA or pre-production clusters. We suggest that your policy include frequent full and incremental backups. Accordingly, we suggest the following backup policy for your production apps: * [full backup](https://dgraph.io/docs/enterprise-features/binary-backups/#forcing-a-full-backup) every 24hrs * incremental backup every 2/4hrs
LGTM with this change
OmarAyo
added a commit
that referenced
this pull request
Dec 8, 2020
* added backup policy * rephrase (cherry picked from commit 73b36d4)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Suggested to implement and use a backup policy in our prod checklist. Also provided some recommendations
Fixes SUCCESS-189
This change is