-
Notifications
You must be signed in to change notification settings - Fork 202
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
Add a webpage that walks through the new backup and restore examples for a local Vitess environment. #1861
base: prod
Are you sure you want to change the base?
Conversation
…ment. Signed-off-by: Shail Pujan <[email protected]>
✅ Deploy Preview for vitess ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Shail Pujan <[email protected]>
content/en/docs/21.0/user-guides/configuration-advanced/resharding.md
Outdated
Show resolved
Hide resolved
that the [MoveTables](../../../migration/move-tables/) and [Resharding](../../../configuration-advanced/resharding) user guides have been followed (which take you through | ||
steps `101` to `306`). | ||
|
||
This guide is useful only if you are using Vitess in a local environment. |
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.
The steps defined here could theoretically be almost replicated on K8S as we are only using vtctldclient
commands. We should mention that this guide is intended for the local getting started guide, but similar steps can be done on a K8S deployment.
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.
Done
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.
I am not seeing this change
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.
I just now push now you can see the changes.
...ent/en/docs/21.0/user-guides/operating-vitess/backup-and-restore/backup_and_restore_local.md
Outdated
Show resolved
Hide resolved
Expected Output | ||
When you run the script, the following output can be expected: |
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.
Something is wrong with the format of Expected Output
, both lines 32 and 33 are rendered on the same line.
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.
removed line 32
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.
I am not seeing it removed
...ent/en/docs/21.0/user-guides/operating-vitess/backup-and-restore/backup_and_restore_local.md
Outdated
Show resolved
Hide resolved
...ent/en/docs/21.0/user-guides/operating-vitess/backup-and-restore/backup_and_restore_local.md
Outdated
Show resolved
Hide resolved
For example, navigating to the directory: | ||
```bash | ||
cd /path/to/local/backup/directory | ||
ls -l | ||
``` |
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.
We should put the full path directly here, so the user can copy-paste. We already know the path ahead of time since it will be under the VTDATAROOT
directory.
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.
Done
...ent/en/docs/21.0/user-guides/operating-vitess/backup-and-restore/backup_and_restore_local.md
Outdated
Show resolved
Hide resolved
```bash | ||
$ ./401_backup.sh | ||
``` |
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.
There is an inconsistency here between how you run 401
and 402
. One contains a $
and the other does not, let's make it consistent please.
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.
Ok added $ to each scripts for maling it consistent
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.
teardown does not have it
...ent/en/docs/21.0/user-guides/operating-vitess/backup-and-restore/backup_and_restore_local.md
Outdated
Show resolved
Hide resolved
|
||
Expected Output | ||
When you run the restore script, the following output can be expected: | ||
```bash |
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.
```bash |
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 bash
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.
Done
…n.sh for cleanup Signed-off-by: Shail Pujan <[email protected]>
|
||
## Local Environment Backup And Restore Steps: | ||
|
||
### Adding a Backup for Local Environment |
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.
### Adding a Backup for Local Environment | |
### Taking a Backup |
This will start the backup process for the customer keyspace and all its shards. | ||
|
||
When you run the script, the following output can be expected: |
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.
This will start the backup process for the customer keyspace and all its shards. | |
When you run the script, the following output can be expected: | |
This will start the backup process for the customer keyspace and all its shards. When you run the script, the following output can be expected: | |
|
||
For example, navigating to the directory: | ||
```bash | ||
$ cd /vtdataroot/backups |
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.
i think using $VTDATAROOT
makes more sense, people might not use /vtdataroot
shail_pujan@SHAIL-PUJAN:~/vtdataroot/backups $ ls | ||
customer | ||
shail_pujan@SHAIL-PUJAN:~/vtdataroot/backups$ cd customer | ||
shail_pujan@SHAIL-PUJAN:~/vtdataroot/backups/customer$ ls | ||
-80 80- | ||
ls -l ./-80/ ./80-/ | ||
./-80/: | ||
total 4 | ||
drwxr-xr-x 2 shail_pujan shail_pujan 4096 Oct 12 12:15 2024-10-12.064518.zone1-0000000300 | ||
|
||
./80-/: | ||
total 4 | ||
drwxr-xr-x 2 shail_pujan shail_pujan 4096 Oct 12 12:15 2024-10-12.064523.zone1-0000000401 | ||
|
||
shail_pujan@SHAIL-PUJAN:~/vtdataroot/backups/customer$ cd ./-80/2024-10-12.064518.zone1-0000000300 | ||
shail_pujan@SHAIL-PUJAN:~/vtdataroot/backups/customer/-80/2024-10-12.064518.zone1-0000000300$ ls -l |
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.
In this block, there is a mix of command thats begins with $
and with shail_pujan@ ...
, so it is a little hard to understand what is going on.
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.
shall we remove shail_pujan?
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.
i think it would be better yes
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.
also it is not clear what instructions we need to follow because the first step is cd /vtdataroot/backups
but then we are in ~/vtdataroot/backups
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.
Ok done
``` | ||
This will safely remove the cluster and associated data, ensuring a clean environment without manual deletions. | ||
|
||
If needed, use the [vtctldclient](../../backup-and-restore/managing-backups)command to remove specific backups, but this is generally not required if you are running the teardown script. |
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.
If needed, use the [vtctldclient](../../backup-and-restore/managing-backups)command to remove specific backups, but this is generally not required if you are running the teardown script. | |
If needed, use the [vtctldclient](../../backup-and-restore/managing-backups) command to remove specific backups, but this is generally not required if you are running the teardown script. |
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.
done with changes.
```bash | ||
./501_teardown.sh | ||
``` | ||
This will safely remove the cluster and associated data, ensuring a clean environment without manual deletions. |
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.
this sentence feels redundant with what we have already written above
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.
This will safely remove the cluster and associated data, ensuring a clean environment without manual deletions. |
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.
done with changes
…stent commands, clearer outputs, and improved directory navigation. Signed-off-by: Shail Pujan <[email protected]>
This PR is For Add new getting started example #1798.
This pull request adds documentation for managing backups and restorations in a local Vitess environment.
Key Changes: