From e2bff256398a298f48117b2d1effe650d2081113 Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Thu, 12 Dec 2024 11:06:57 -0500 Subject: [PATCH] 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.