From b5d55365a5b02f45bd0220d57e88adc1936947d3 Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Thu, 12 Dec 2024 10:27:50 -0500 Subject: [PATCH 1/3] docs: update backup and restore for data dir --- .../pages/admin-guides/management/operations/backup-restore.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/admin-guides/management/operations/backup-restore.mdx b/docs/pages/admin-guides/management/operations/backup-restore.mdx index 165b65de5f4f3..5eb28433fdfa8 100644 --- a/docs/pages/admin-guides/management/operations/backup-restore.mdx +++ b/docs/pages/admin-guides/management/operations/backup-restore.mdx @@ -41,7 +41,7 @@ Teleport audit logs, logged events have a TTL of 1 year. | Backend | Recommended backup strategy | | - | - | -| Local Filesystem | Back up the `/var/lib/teleport/storage` directory and the output of `tctl get all --with-secrets`. | +| Local Filesystem | Back up the data directory (`/var/lib/teleport/` by default) and the output of `tctl get all --with-secrets`. | | DynamoDB | [Follow AWS's guidelines for backup and restore](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/BackupRestore.html) | | etcd | [Follow etcd's guidelines for disaster recovery](https://etcd.io/docs/v2/admin_guide) | | Firestore | [Follow GCP's guidelines for automated backups](https://firebase.google.com/docs/database/backups) | From e2bff256398a298f48117b2d1effe650d2081113 Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Thu, 12 Dec 2024 11:06:57 -0500 Subject: [PATCH 2/3] docs: update configuration ref --- .../pages/admin-guides/management/operations/backup-restore.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/admin-guides/management/operations/backup-restore.mdx b/docs/pages/admin-guides/management/operations/backup-restore.mdx index 5eb28433fdfa8..8d9b6f2fe830b 100644 --- a/docs/pages/admin-guides/management/operations/backup-restore.mdx +++ b/docs/pages/admin-guides/management/operations/backup-restore.mdx @@ -14,7 +14,7 @@ backed up and lays out our recommended approach for performing backups. Teleport's Proxy Service and Nodes are stateless. For these components, only -`teleport.yaml` should be backed up. +the configuration file (default `/etc/teleport.yaml`) should be backed up. The Auth Service is Teleport's brain, and depending on the backend should be backed up regularly. From 0dc84e99f71f7a5e19141edaef32bd3e524b0b32 Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Thu, 12 Dec 2024 11:07:30 -0500 Subject: [PATCH 3/3] docs: update teleport config ref --- .../pages/admin-guides/management/operations/backup-restore.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/admin-guides/management/operations/backup-restore.mdx b/docs/pages/admin-guides/management/operations/backup-restore.mdx index 8d9b6f2fe830b..3a94126669867 100644 --- a/docs/pages/admin-guides/management/operations/backup-restore.mdx +++ b/docs/pages/admin-guides/management/operations/backup-restore.mdx @@ -14,7 +14,7 @@ backed up and lays out our recommended approach for performing backups. Teleport's Proxy Service and Nodes are stateless. For these components, only -the configuration file (default `/etc/teleport.yaml`) should be backed up. +the configuration file (`/etc/teleport.yaml` by default) should be backed up. The Auth Service is Teleport's brain, and depending on the backend should be backed up regularly.