Merge branch 'main' of github.com:ClickHouse/clickhouse-docs-private into ppv2

gingerwizard · gingerwizard · commit 333bc6d12ce6 · 2025-01-27T14:53:17.000Z
diff --git a/docs/en/about-us/support.md b/docs/en/about-us/support.md
@@ -7,7 +7,20 @@ sidebar_position: 30
 
 ClickHouse provides Support Services for our ClickHouse Cloud users and customers. Our objective is a Support Services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our Support Services](https://clickhouse.com/support/program/) page.
 
-[Login to the Cloud console](https://clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. Customers can only log Severity 3 tickets for single replica services across tiers. The exception is for a service leveraging the compute-compute separation feature, where the parent service is running 3+ replicas.
+[Login to the Cloud console](https://clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. 
+
+**Service level agreements ("SLA")**
+Classification of severity levels for issues reported and response times.
+
+| Severity Level  | Trial                 | Basic                    | Scale                      | Enterprise                                                                             |
+|-----------------|-----------------------|--------------------------|----------------------------|----------------------------------------------------------------------------------------|
+| Severity 1      | Not available         | Not available            | 1 hour 24x7                | 30 minute 24x7                                                                         |
+| Severity 2      | Not available         | Not available            | 4 business hours           | 2 business hours                                                                       |
+| Severity 3      | 1 business day        | 1 business day           | 1 business day             | 1 business day                                                                         | 
+
+(*) Business hours are Monday 00:00 UTC to Saturday 00:00 UTC
+
+Customers can only log Severity 3 tickets for single replica services across tiers. The exception is for a service leveraging the compute-compute separation feature, where the parent service is running 3+ replicas.
 
 You can also subscribe to our [status page](https://status.clickhouse.com) to get notified quickly about any incidents affecting our platform.
 
diff --git a/docs/en/cloud/manage/backups/configurable-backups.md b/docs/en/cloud/manage/backups/configurable-backups.md
@@ -0,0 +1,44 @@
+---
+sidebar_label: Configurable Backups
+slug: /en/cloud/manage/backups/configurable-backups
+description: Configurable Backups
+title: Configurable Backups
+keywords: [backups, cloud backups, restore]
+---
+
+import CloudNotSupportedBadge from '@theme/badges/CloudNotSupportedBadge';
+import ScalePlanFeatureBadge from '@theme/badges/ScalePlanFeatureBadge';
+
+<ScalePlanFeatureBadge feature="Configurable Backups" linking_verb_are="True"/>
+
+ClickHouse Cloud allows you to configure the schedule for your backups for **Scale** and **Enterprise** tier services. Backups can be configured along the following dimensions based on your business needs.
+
+- **Retention**: The duration of days, for which each backup will be retained. Retention can be specified as low as 1 day, and as high as 30 days with several values to pick in between.
+- **Frequency**: The frequency allows you to specify the time duration between subsequent backups. For instance, a frequency of "every 12 hours" means that backups will be spaced 12 hours apart. Frequency can range from "every 6 hours" to "every 48 hours" in the following hourly increments: `6`, `8`, `12`, `16`, `20`, `24`, `36`, `48`.
+- **Start Time**: The start time for when you want to schedule backups each day. Specifying a start time implies that the backup "Frequency" will default to once every 24 hours.  Clickhouse Cloud will start the backup within an hour of the specified start time.
+
+:::note
+The custom schedule will override the default backup policy in ClickHouse Cloud for your given service.
+:::
+
+To configure the backup schedule for a service, go to the **Settings** tab in the console and click on **Change backup configuration**.
+
+<div class="eighty-percent">
+![Configure backup settings](../images/backup-settings.png)
+</div>
+<br/>
+
+This opens a tab to the right where you can choose values for retention, frequency, and start time. You will need to save the chosen settings for them to take effect.
+
+<div class="eighty-percent">
+![Select backup retention and frequency](../images/backup-configuration-form.png)
+</div>
+<br/>
+
+:::note
+Start time and frequency are mutually exclusive. Start time takes precedence.
+:::
+
+:::note
+Changing the backup schedule can cause higher monthly charges for storage as some of the backups might not be covered in the default backups for the service. See ["Understanding backup cost"](./overview.md/#understanding-backup-cost) section below.
+:::
diff --git a/docs/en/cloud/manage/backups/export-backups-to-own-cloud-account.md b/docs/en/cloud/manage/backups/export-backups-to-own-cloud-account.md
@@ -1,6 +1,6 @@
 ---
 sidebar_label: Export Backups to your Own Cloud Account
-slug: /en/cloud/manage/bring-your-own-bucket
+slug: /en/cloud/manage/backups/export-backups-to-own-cloud-account
 title: Export Backups to your Own Cloud Account
 ---
 
@@ -9,12 +9,12 @@ import EnterprisePlanFeatureBadge from '@theme/badges/EnterprisePlanFeatureBadge
 <EnterprisePlanFeatureBadge/>
 
 ClickHouse Cloud supports taking backups to your own cloud service provider (CSP) account (AWS S3, Google Cloud Storage, or Azure Blob Storage).
-For details of how ClickHouse Cloud backups work, including "full" vs. "incremental" backups, see the [backups](./backups.md) docs.
+For details of how ClickHouse Cloud backups work, including "full" vs. "incremental" backups, see the [backups](overview.md) docs.
 
 Here we show examples of how to take full and incremental backups to AWS, GCP, Azure object storage as well as how to restore from the backups.
 
 :::note
-Users should be aware that any usage where backups are being exported to a different region in the same cloud provider, or to another cloud provider (in the same or different region) will incur [data transfer](./network-data-transfer.mdx) charges.
+Users should be aware that any usage where backups are being exported to a different region in the same cloud provider, or to another cloud provider (in the same or different region) will incur [data transfer](../network-data-transfer.mdx) charges.
 :::
 
 ## Requirements
diff --git a/docs/en/cloud/manage/backups/index.md b/docs/en/cloud/manage/backups/index.md
@@ -0,0 +1,11 @@
+---
+slug: /en/cloud/manage/backups
+title: Backups
+description: Table of contents page for backups.
+keywords: [backups, configurable backups, export backups to own cloud]
+---
+
+| Page                      | Description |
+|---------------------------|-------------|
+| [Overview](./overview.md) |             |
+|                           |             |
diff --git a/docs/en/cloud/manage/backups/overview.md b/docs/en/cloud/manage/backups/overview.md
@@ -1,7 +1,8 @@
 ---
-sidebar_label: Backups
-slug: /en/cloud/manage/backups
-description: Managing backups in ClickHouse Cloud
+sidebar_label: Overview
+sidebar_position: 0
+slug: /en/cloud/manage/backups/overview
+title: Overview
 keywords: [backups, cloud backups, restore]
 ---
 
@@ -20,65 +21,27 @@ In the screenshot below, the solid line squares show full backups and the dotted
 
 On Day 1, a full backup is taken to start the backup chain. On Day 2, an incremental backup is taken, and we now have a full and incremental backup available to restore from. By Day 7, we have one full backup and six incremental backups in the chain, with the most recent two incremental backups visible to the user. On Day 8, we take a new full backup, and on Day 9, once we have two backups in the new chain, the previous chain is discarded.
 
-![Backup chain](./images/backup-chain.png)
+![Backup chain](../images/backup-chain.png)
 
 *Example backup scenario in Clickhouse Cloud*
 
 ## Default backup policy
 
-All services will default to one backup, retained for a day with the new Pricing tiers. 
-Users who need additional backups can do so by configuring additional backups under the settings tab of the Cloud Console. 
-No free backups are included in the new pricing.
-
-## Configurable backups
-
-<ScalePlanFeatureBadge feature="Configurable Backups" linking_verb_are="True"/>
-
-ClickHouse Cloud allows you to configure the schedule for your backups for **Scale** and **Enterprise** tier services. Backups can be configured along the following dimensions based on your business needs.
-
-- **Retention**: The duration of days, for which each backup will be retained. Retention can be specified as low as 1 day, and as high as 30 days with several values to pick in between.
-- **Frequency**: The frequency allows you to specify the time duration between subsequent backups. For instance, a frequency of "every 12 hours" means that backups will be spaced 12 hours apart. Frequency can range from "every 6 hours" to "every 48 hours" in the following hourly increments: `6`, `8`, `12`, `16`, `20`, `24`, `36`, `48`.
-- **Start Time**: The start time for when you want to schedule backups each day. Specifying a start time implies that the backup "Frequency" will default to once every 24 hours.  Clickhouse Cloud will start the backup within an hour of the specified start time.
-
-:::note
-The custom schedule will override the default backup policy in ClickHouse Cloud for your given service.
-:::
-
-To configure the backup schedule for a service, go to the **Settings** tab in the console and click on **Change backup configuration**.
-
-<div class="eighty-percent">
-![Configure backup settings](./images/backup-settings.png)
-</div>
-<br/>
-
-This opens a tab to the right where you can choose values for retention, frequency, and start time. You will need to save the chosen settings for them to take effect.
-
-<div class="eighty-percent">
-![Select backup retention and frequency](./images/backup-configuration-form.png)
-</div>
-<br/>
-
-:::note
-Start time and frequency are mutually exclusive. Start time takes precedence. 
-:::
-
-:::note
-Changing the backup schedule can cause higher monthly charges for storage as some of the backups might not be covered in the default backups for the service. See ["Understanding backup cost"](#understanding-backup-cost) section below.
-:::
+In the Basic, Scale, and Enterprise tiers, backups are metered and billed separately from storage. All services will default to one backup with the ability to configure more, starting with the Scale tier, via the Settings tab of the Cloud Console.
 
 ## Backup status list
 
-Your service will be backed up based on the set schedule, whether it is the default daily schedule or a custom schedule picked by you. All available backups can be viewed from the **Backups** tab of the service. From here, you can see the status of the backup, the duration, as well as the size of the backup. You can also restore a specific backup using the **Actions** column.
+Your service will be backed up based on the set schedule, whether it is the default daily schedule or a [custom schedule](./configurable-backups.md) picked by you. All available backups can be viewed from the **Backups** tab of the service. From here, you can see the status of the backup, the duration, as well as the size of the backup. You can also restore a specific backup using the **Actions** column.
 
-![List of backups statuses](./images/backup-status-list.png)
+![List of backups statuses](../images/backup-status-list.png)
 
 ## Understanding backup cost
 
 ClickHouse Cloud includes two backups for free, but choosing a schedule that requires retaining more data, or causes more frequent backups can cause additional storage charges for backups. If you do not change the default settings, you will not incur any backup cost.
 
 To understand the backup cost, you can view the backup cost per service from the usage screen (as shown below). Once you have backups running for a few days with a customized schedule, you can get an idea of the cost and extrapolate to get the monthly cost for backups.
 
-![Backup usage chart](./images/backup-usage.png)
+![Backup usage chart](../images/backup-usage.png)
 
 Estimating the total cost for your backups requires you to set a schedule. We are also working on updating our [pricing calculator](https://clickhouse.com/pricing), so you can get a monthly cost estimate before setting a schedule. You will need to provide the following inputs in order to estimate the cost:
 - Size of the full and incremental backups
@@ -97,14 +60,14 @@ Backups are restored to a new ClickHouse Cloud service, not to the existing serv
 
 After clicking on the **Restore** backup icon, you can specify the service name of the new service that will be created, and then restore this backup:
 
-![Restoring a backup](./images/backup-restore.png)
+![Restoring a backup](../images/backup-restore.png)
 
 The new service will show in the services list as `Provisioning` until it is ready:
 
-<img src={require('./images/backup-service-provisioning.png').default}    
-  class="image"
-  alt="Provisioning service in progress"
-  style={{width: '80%'}} />
+<img src={require('../images/backup-service-provisioning.png').default}    
+class="image"
+alt="Provisioning service in progress"
+style={{width: '80%'}} />
 
 ## Working with your restored service
 
@@ -189,12 +152,12 @@ After you have successfully inserted the data into your original service, make s
 
 <CloudNotSupportedBadge/>
 
-The `UNDROP` command is not supported in ClickHouse Cloud. If you accidentally `DROP` a table, the best course of action is to restore your last backup and recreate the table from the backup. 
+The `UNDROP` command is not supported in ClickHouse Cloud. If you accidentally `DROP` a table, the best course of action is to restore your last backup and recreate the table from the backup.
 
 To prevent users from accidentally dropping tables, you can use [`GRANT` statements](/docs/en/sql-reference/statements/grant) to revoke permissions for the [`DROP TABLE` command](/docs/en/sql-reference/statements/drop#drop-table) for a specific user or role.
 
 :::note
-To prevent accidental deletion of data, please note that by default it is not possible to drop tables >`1TB` in size in ClickHouse Cloud. 
+To prevent accidental deletion of data, please note that by default it is not possible to drop tables >`1TB` in size in ClickHouse Cloud.
 Should you wish to drop tables greater than this threshold you can use setting `max_table_size_to_drop` to do so:
 
 ```sql
@@ -203,6 +166,10 @@ SYNC SETTINGS max_table_size_to_drop=2097152 -- increases the limit to 2TB
 ```
 :::
 
+## Configurable Backups
+
+If you want to set up a backups schedule different from the default backup schedule, take a look at [Configurable Backups](./configurable-backups.md).
+
 ## Export backups to your own cloud account
 
-For users wanting to export backups to their own cloud account, see [here](/docs/en/cloud/manage/bring-your-own-bucket).
+For users wanting to export backups to their own cloud account, see [here](./export-backups-to-own-cloud-account.md).
diff --git a/docs/en/cloud/manage/billing.md b/docs/en/cloud/manage/billing.md
@@ -24,7 +24,7 @@ Storage costs are the same across tiers and vary by region and cloud service pro
 
 Storage and backups are counted towards storage costs and billed separately. 
 All services will default to one backup, retained for a day. 
-Users who need additional backups can do so by configuring additional [backups](./backups.md) under the settings tab of the Cloud Console.
+Users who need additional backups can do so by configuring additional [backups](backups/overview.md) under the settings tab of the Cloud Console.
 
 ### How do I estimate compression?
 
diff --git a/docs/en/cloud/manage/jan2025_faq/billing.md b/docs/en/cloud/manage/jan2025_faq/billing.md
@@ -36,8 +36,14 @@ If committed spend contracts exhaust credits before their renewal date, we bill
 
 Users on a monthly PAYG plan will continue to be billed using the old pricing plan for the Development and Production services. They have until July 23, 2025, to migrate to the new plan self-serve, or they will all be migrated to the Scale configuration on this day and billed based on the new plan.
 
+### Where can I reference legacy plans?
+
+Legacy plans are available for reference [here](https://clickhouse.com/pricing?legacy=true). 
+
 ## Marketplaces
 
 ### Are there changes to how users are charged via the CSP marketplaces?
 
 Users who sign up to ClickHouse Cloud via a CSP Marketplace incur usage in terms of CHCs (ClickHouse Cloud Credits). This behavior has not changed. However, the underlying composition of the credit usage will align with the pricing and packaging changes outlined here and include charges for any data transfer usage and ClickPipes once those are live.
+
+
diff --git a/docs/en/cloud/manage/jan2025_faq/dimensions.md b/docs/en/cloud/manage/jan2025_faq/dimensions.md
@@ -63,4 +63,4 @@ The new pricing model will take effect for all organizations created after **Jan
 
 ### What happens to current users?
 
-Existing users will have a **60-day grace period** during which the ClickPipes service will continue to be offered for free. Billing will automatically start for ClickPipes for existing users on **March 24th, 2025.**
+Existing users will have a **8 week grace period** during which the ClickPipes service will continue to be offered for free. Billing will automatically start for ClickPipes for existing users on **March 24th, 2025.**
diff --git a/docs/en/cloud/manage/jan2025_faq/plan_migrations.md b/docs/en/cloud/manage/jan2025_faq/plan_migrations.md
@@ -58,7 +58,7 @@ The console will prompt you with recommended options for each service based on h
 
 ### How do users size and estimate the cost of "warehouses" in the new pricing?
 
-Please refer to the pricing calculator that will help estimate the cost based on your workload size and tier selection.
+Please refer to the pricing calculator on the [Pricing](https://clickhouse.com/pricing) page, which will help estimate the cost based on your workload size and tier selection.
 
 
 ## Undertaking the migration
diff --git a/docs/en/cloud/manage/jan2025_faq/summary.md b/docs/en/cloud/manage/jan2025_faq/summary.md
@@ -81,7 +81,7 @@ Detailed breakdown of effective dates is below:
 * **New Customers**: The new plans will take effect on **January 23, 2025** for new customers of ClickHouse Cloud. 
 * **Existing PAYG Customers**: Pay-as-you-go (PAYG) customers will have 6 months until **July 23, 2025** to migrate to new plans.
 * **Existing Committed Spend Customers**: Customers with committed spend agreements can renegotiate their terms at the end of their current contract.
-* **New usage dimensions** for Data Transfer and ClickPipes are effective for both PAYG and Committed Spend customers 60 days following this announcement on **March 24, 2025**. 
+* **New usage dimensions** for Data Transfer and ClickPipes are effective for both PAYG and Committed Spend customers 8 weeks following this announcement on **March 24, 2025**. 
 
 ## What actions should you take?
 
diff --git a/docs/en/cloud/reference/changelog.md b/docs/en/cloud/reference/changelog.md
@@ -6,7 +6,7 @@ title: Cloud Changelog
 
 In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibility](/docs/en/cloud/reference/cloud-compatibility.md) page.
 
-## January 23, 2024
+## January 27, 2025
 
 ### Changes to ClickHouse Cloud tiers
 
diff --git a/docs/en/cloud/reference/warehouses.md b/docs/en/cloud/reference/warehouses.md
@@ -152,7 +152,7 @@ Because this compute-compute separation is currently in private preview, there a
 
 4. **Inserts in one read-write service can prevent another read-write service from idling if idling is enabled.** Because of the previous point, a second service perform background merge operations for the first service. These background operations can prevent the second service from going to sleep when idling. Once the background operations are finished, the service will be idled. Read-only services are not affected and will be idled without delay.
 
-5. **CREATE/RENAME/DROP DATABASE queries could be blocked by idled/stopped services by default (limitation will be removed in GA).** These queries can hang. To bypass this, you  can run database management queries with `settings distributed_ddl_task_timeout=0` at the session or per query level. For example:
+5. **CREATE/RENAME/DROP DATABASE queries could be blocked by idled/stopped services by default.** These queries can hang. To bypass this, you  can run database management queries with `settings distributed_ddl_task_timeout=0` at the session or per query level. For example:
 
 ```sql
 create database db_test_ddl_single_query_setting
diff --git a/sidebars.js b/sidebars.js
diff --git a/src/css/custom.scss b/src/css/custom.scss

Original file line number	Diff line number	Diff line change
`@@ -63,4 +63,4 @@ The new pricing model will take effect for all organizations created after **Jan`
`63`	`63`
`64`	`64`	`### What happens to current users?`
`65`	`65`
`66`		`-Existing users will have a 60-day grace period during which the ClickPipes service will continue to be offered for free. Billing will automatically start for ClickPipes for existing users on March 24th, 2025.`
	`66`	`+Existing users will have a 8 week grace period during which the ClickPipes service will continue to be offered for free. Billing will automatically start for ClickPipes for existing users on March 24th, 2025.`