-
Notifications
You must be signed in to change notification settings - Fork 207
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
Enhance the getting started guide: scheduled backups #1746
Conversation
Signed-off-by: Florent Poinsard <[email protected]>
✅ Deploy Preview for vitess ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Florent Poinsard <[email protected]>
Signed-off-by: Florent Poinsard <[email protected]>
Signed-off-by: Florent Poinsard <[email protected]>
content/en/docs/20.0/user-guides/configuration-advanced/resharding.md
Outdated
Show resolved
Hide resolved
|
||
{{< info >}} | ||
This guide follows on from the Get Started guides. Please make sure that you have | ||
an [Operator](../../../../get-started/operator) or [local](../../../../get-started/local) installation ready. It also assumes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this works only with operator, we should remove the reference to local installation from here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed via 5a977a2
content/en/docs/20.0/user-guides/configuration-advanced/resharding.md
Outdated
Show resolved
Hide resolved
content/en/docs/20.0/user-guides/operating-vitess/backup-and-restore/scheduled-backups.md
Outdated
Show resolved
Hide resolved
content/en/docs/20.0/user-guides/operating-vitess/backup-and-restore/scheduled-backups.md
Outdated
Show resolved
Hide resolved
## Backups | ||
|
||
If you are not familiar with how backups in Vitess work we suggest you familiarize yourself with it. | ||
An [entire guide](../overview/) is available in this section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this line, and hyperlink from [how backups work]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed via 5a977a2
content/en/docs/20.0/user-guides/operating-vitess/backup-and-restore/scheduled-backups.md
Outdated
Show resolved
Hide resolved
the two `customer` shards, and the second one will backup the `commerce` keyspace. | ||
The backups will be stored directly inside the Minikube node, but if you want to backup to for instance S3, you can | ||
change the `location` of the backup in `401_scheduled_backups.yaml`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is worth putting a big WARNING here. Something like:
Please note that is not recommended to run production backups every minute. These schedules are only an example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed via 5a977a2
content/en/docs/20.0/user-guides/operating-vitess/backup-and-restore/scheduled-backups.md
Outdated
Show resolved
Hide resolved
content/en/docs/20.0/user-guides/operating-vitess/backup-and-restore/scheduled-backups.md
Outdated
Show resolved
Hide resolved
Only merge once vitessio/vitess#15969 is merged. |
Co-authored-by: Deepthi Sigireddi <[email protected]> Signed-off-by: Florent Poinsard <[email protected]>
Signed-off-by: Florent Poinsard <[email protected]>
DCO is working wrong right now, manually verified signoff |
This Pull Request adds another segment to our getting started guide with the operator to teach how to schedule backups. It comes as a very last step right after
Resharding
.This PR is related to planetscale/vitess-operator#553 and vitessio/vitess#15969