-
Notifications
You must be signed in to change notification settings - Fork 423
Guide: migrating from OSS to Cloud using BACKUP/RESTORE commands #4663
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
base: main
Are you sure you want to change the base?
Guide: migrating from OSS to Cloud using BACKUP/RESTORE commands #4663
Conversation
|
@Blargian is attempting to deploy a commit to the ClickHouse Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
docs/cloud/onboard/02_migrate/01_migration_guides/07_OSS_to_Cloud/02_oss_to_cloud_backups.md
Outdated
Show resolved
Hide resolved
docs/cloud/onboard/02_migrate/01_migration_guides/07_OSS_to_Cloud/02_oss_to_cloud_backups.md
Outdated
Show resolved
Hide resolved
docs/cloud/onboard/02_migrate/01_migration_guides/07_OSS_to_Cloud/02_oss_to_cloud_backups.md
Outdated
Show resolved
Hide resolved
docs/cloud/onboard/02_migrate/01_migration_guides/07_OSS_to_Cloud/02_oss_to_cloud_backups.md
Outdated
Show resolved
Hide resolved
docs/cloud/onboard/02_migrate/01_migration_guides/07_OSS_to_Cloud/02_oss_to_cloud_backups.md
Outdated
Show resolved
Hide resolved
|
Hey Shaun - I've reviewed this and think we need to do some rewording and restructuring to align with docs standards for new or updated guides. A few things I'm thinking:
Happy to discuss or pair on this. |
| "Principal": { | ||
| "AWS": "arn:aws:iam::782985192762:user/docs-s3-user" | ||
| }, | ||
| "Action": "s3:*", |
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.
Do you think it's worth mentioning that the bucket policy makes it possible to do all actions on the bucket?
|
|
||
| ## Overview {#overview-migration-approaches} | ||
|
|
||
| There are two primary methods to migrate from self-managed ClickHouse (OSS) to ClickHouse Cloud: |
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.
Maybe say 'migrate data'
| ::: | ||
|
|
||
| ## OSS preparation {#oss-setup} | ||
|
|
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.
Let's add a sentence explaining what we're doing, something like:
We'll first spin up a ClickHouse cluster using a Docker Compose configuration from our examples repository.
And then continue with the instructions
Perhaps we can also put something that says they can ignore spinning up the ClickHouse cluster if they already have one running themselves?
| ### Create sample data {#create-sample-data} | ||
|
|
||
| For this guide, we'll use the New York taxi dataset as sample data. | ||
| Follow the first two steps of the [New York taxi data guide](/getting-started/example-datasets/nyc-taxi) to create the table and load data. |
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 found this a bit confusing as I thought I should go to that guide but actually we include the instructions below, so let's explain that. Something like:
We're going to follow the first two steps of the [New York taxi data guide](/getting-started/example-datasets/nyc-taxi) to create the table and load data.
Those steps are included below for your convenience
|
|
||
| In the `CREATE TABLE` DDL statement we specified the table engine type as `MergeTree`, however | ||
| ClickHouse Cloud works with [`SharedMergeTree`](/cloud/reference/shared-merge-tree). When restoring a backup, ClickHouse automatically converts `ReplicatedMergeTree` to `SharedMergeTree`. | ||
| However, you'll need to convert any `MergeTree` tables to `ReplicatedMergeTree` before backing them up. |
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.
Let's move this whole explanation to be just below the DDL statement.
I'm also wondering why did we create the table as MergeTree only to then convert it to replicated in the following section? If people are using a cluster, would they usually be having their tables as ReplicatedMergeTree anyway?
If so then maybe we can include the explanation of how to convert a table from MergeTree to ReplicatedMergeTree as a mini guide that we link to rather than having it inline this one?
| #highlight-end | ||
| ] | ||
| }, | ||
| "Action": "s3:*", |
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.
Do they need to this set to all actions?
| - Quotas | ||
| - User-defined functions | ||
|
|
||
| If you're using a different CSP, you can use the `TO S3()` (for both AWS and GCP) and `TO AzureBlobStorage()` syntax. |
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.
Maybe spell out CSP (cloud service provider) - not sure if the acronymn is super well know to end users.
|
|
||
| This article demonstrates how to leverage role-based access to authenticate with Amazon Simple Storage Service (S3) and access your data securely from ClickHouse Cloud. | ||
| This guide demonstrates how ClickHouse Cloud customers can leverage role-based access to authenticate with Amazon Simple Storage Service (S3) and access their data securely. | ||
| Before diving into the setup for secure S3 access, it is important to understand how this works. Below is an overview of how ClickHouse services can access private S3 buckets by assuming into a role within customers' AWS account. |
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 we don't need into
Below is an overview of how ClickHouse services can access private S3 buckets by assuming into a role within customers' AWS account.
becomes
Below is an overview of how ClickHouse services can access private S3 buckets by assuming a role within customers' AWS account.
Summary
Adds a guide on how to migrate from OSS to Cloud using BACKUP/RESTORE commands.
Also splits out the guide on how to set up an S3 bucket and IAM role into it's own page instead of a snippet and updates the images. The previous one is quite outdated.
Backup and restore docs are improved here: #4049
Checklist