Skip to content

Commit 27e0df3

Browse files
BlargianBlargian
committed
fix links
1 parent 2f1eb07 commit 27e0df3

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

‎docs/operations_/backup_restore/00_overview.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ in the sidebar.
1717

1818
## Introduction {#introduction}
1919

20-
While [replication](../engines/table-engines/mergetree-family/replication.md) provides protection from hardware failures, it does not
20+
While [replication](/engines/table-engines/mergetree-family/replication) provides protection from hardware failures, it does not
2121
protect against human errors: accidental deletion of data, deletion of the wrong
2222
table or a table on the wrong cluster, and software bugs that result in incorrect
2323
data processing or data corruption.
@@ -50,12 +50,12 @@ it on a spare ClickHouse cluster regularly.
5050
The following pages detail the various backup and
5151
restore methods available in ClickHouse:
5252

53-
| Page | Description |
54-
|------------------------------------------------------------------|-----------------------------------------------------------|
55-
| [Backup/restore using local disk or S3 disk](./01_local_disk.md) | Details backup/restore to or from a local disk or S3 disk |
56-
| [Backup/restore using S3 endpoint](./02_s3_endpoint.md) | Details backup/restore to or from an S3 endpoint |
57-
| [Backup/restore using AzureBlobStorage](./03_s3_disk.md) | Details backup/restore to or from Azure blob storage |
58-
| [Alternative methods](./04_alternative_methods.md) | Discusses alternative backup methods |
53+
| Page | Description |
54+
|---------------------------------------------------------------------|-----------------------------------------------------------|
55+
| [Backup/restore using local disk or S3 disk](./01_local_disk.md) | Details backup/restore to or from a local disk or S3 disk |
56+
| [Backup/restore using S3 endpoint](./02_s3_endpoint.md) | Details backup/restore to or from an S3 endpoint |
57+
| [Backup/restore using AzureBlobStorage](./03_azure_blob_storage.md) | Details backup/restore to or from Azure blob storage |
58+
| [Alternative methods](./04_alternative_methods.md) | Discusses alternative backup methods |
5959

6060
Backups can:
6161
- be [full or incremental](#backup-types)

‎docs/operations_/backup_restore/04_alternative_methods.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ or a distributed filesystem like [HDFS](https://hadoop.apache.org/docs/stable/ha
2626
Some local filesystems provide snapshot functionality (for example, [ZFS](https://en.wikipedia.org/wiki/ZFS)),
2727
but they might not be the best choice for serving live queries. A possible solution
2828
is to create additional replicas with this kind of filesystem and exclude them
29-
from the [Distributed](../engines/table-engines/special/distributed.md) tables that are used for `SELECT` queries.
29+
from the [Distributed](/engines/table-engines/special/distributed) tables that are used for `SELECT` queries.
3030
Snapshots on such replicas will be out of reach of any queries that modify data.
3131
As a bonus, these replicas might have special hardware configurations with more
3232
disks attached per server, which would be cost-effective.

‎docs/operations_/backup_restore/_snippets/_generic_settings.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
| `base_backup` | The destination of the base backup used for incremental backups. For example: `Disk('backups', '1.zip')` | |
88
| `use_same_password_for_base_backup` | Whether base backup archive should inherit the password from the query. | |
99
| `structure_only` | If enabled, only backs up or restores the CREATE statements without the actual table data. | |
10-
| `storage_policy` | Storage policy for the tables being restored. See ["using multiple block devices for data storage](../../engines/table-engines/mergetree-family/mergetree.md#table_engine-mergetree-multiple-volumes). Only applicable to the `RESTORE` command. Applies only to tables with an engine from the `MergeTree` family. | |
10+
| `storage_policy` | Storage policy for the tables being restored. See ["using multiple block devices for data storage](/engines/table-engines/mergetree-family/mergetree#table_engine-mergetree-multiple-volumes). Only applicable to the `RESTORE` command. Applies only to tables with an engine from the `MergeTree` family. | |
1111
| `allow_non_empty_tables` | Allows `RESTORE TABLE` to insert data into non-empty tables. This will mix earlier data in the table with the data extracted from the backup. This setting can therefore cause data duplication in the table, use with caution. | `0` |
1212
| `backup_restore_keeper_max_retries` | Max retries for [Zoo]Keeper operations in the middle of a BACKUP or RESTORE operation. Should be big enough so the whole operation won't fail because of a temporary [Zoo]Keeper failure. | `1000` |
1313
| `backup_restore_keeper_retry_initial_backoff_ms` | Initial backoff timeout for [Zoo]Keeper operations during backup or restore | `100` |

0 commit comments

Comments
 (0)