이 페이지에서는 VMware용 Google Distributed Cloud(소프트웨어 전용)로 만든 관리자 클러스터를 백업 및 복원하는 방법을 설명합니다. 백업 프로세스에는 gkectl 명령줄 도구를 사용하여 클러스터의 etcd 데이터, 보안 비밀, 인증서를 백업하는 작업이 포함됩니다. 관리자 클러스터를 수동으로 백업하고 복원할 수도 있습니다.
관리자 클러스터 백업
관리자 클러스터 백업이 클러스터 생성, 업데이트, 업그레이드 전후에 자동으로 수행되도록 설정할 수 있습니다. 또한 필요한 경우 언제든지 주문형 백업을 수행할 수 있습니다.
관리자 클러스터 백업에는 다음이 포함됩니다.
관리자 클러스터 etcd 데이터
보안 비밀
인증서
상시 사용 설정 보안 비밀 암호화 기능이 사용 설정된 경우 상시 사용 설정 보안 비밀 암호화 키 및 구성 파일
관리자 클러스터 kubeconfig 파일(1.29 이상)
관리자 클러스터 SSH 키 파일(1.29 이상)
백업 크기는 클러스터 크기에 따라 3MB~100MB가 될 수 있습니다.
관리자 클러스터 백업 기능 사용 설정
기본적으로 이 기능은 사용 중지되어 있습니다. 관리자 클러스터 백업 기능을 사용 설정하려면 다음 안내를 따르세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how to back up and restore an admin cluster created with\nGoogle Distributed Cloud (software only) for VMware. The backup process includes backing\nup the cluster's etcd data, Secrets, and certificates using the `gkectl`\ncommand-line tool. You can also\n[back up and restore](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/back-up-admin-cluster) an admin\ncluster manually.\n\nTo back up and restore a cluster with\n[advanced cluster](/kubernetes-engine/distributed-cloud/vmware/docs/concepts/advanced-clusters) enabled, see\n[Back up and restore advanced clusters with gkectl](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/back-up-and-restore-advanced-cluster-with-gkectl).\n| **Note:** Using a third-party backup tool, such as Veeam, to back up an admin cluster isn't supported. Backing up the cluster with a third-party tool might lead to unforeseen errors in cluster operations.\n\nBack up an admin cluster\n\nYou can set up admin cluster backups so they are automatically performed before\nand after cluster creation, update, and upgrade. You can also perform an\non-demand backup whenever you deem it necessary.\n\nAn admin cluster backup includes the following:\n\n- Admin cluster etcd data\n- Secrets\n- Certificates\n- Always-on secrets encryption keys and config files if always-on secrets encryption feature is enabled\n- Admin cluster kubeconfig file (1.29 and higher)\n- Admin cluster SSH key file (1.29 and higher)\n\nThe size of a backup can range from 3 MB--100 MB depending on the size of the cluster.\n\nEnable the admin cluster backup feature\n\nBy default this feature is disabled. To enable the admin cluster backup feature:\n\n1. Add the following section to the [admin cluster configuration file](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest):\n\n ```\n clusterBackup:\n datastore: DATASTORE\n ```\n\n Replace \u003cvar class=\"edit\" translate=\"no\"\u003eDATASTORE\u003c/var\u003e with the datastore where you want to store the backup. The datastore must be in the same datacenter as the admin cluster.\n\n For non HA admin cluster, backups are located in the \"anthos-backup/\u003cvar translate=\"no\"\u003eDATADISK_PATH\u003c/var\u003e\" directory of the specified datastore.\n\n For HA admin cluster, backups are located in \"anthos/\u003cvar translate=\"no\"\u003eADMIN_CLUSTER_NAME\u003c/var\u003e/backup\" directory of the specified datastore.\n2. Update the admin cluster:\n\n ```\n gkectl update admin --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config ADMIN_CLUSTER_CONFIG\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_KUBECONFIG\u003c/var\u003e with the path of your admin cluster kubeconfig file.\n - \u003cvar translate=\"no\"\u003eADMIN_CLUSTER_CONFIG\u003c/var\u003e with the path of your admin cluster configuration file.\n\nDisable the admin cluster backup feature\n\n1. Remove the `clusterBackup` section from the admin cluster configuration file.\n\n ```\n clusterBackup:\n datastore: DATASTORE\n ```\n2. Update the admin cluster with this change, using this command:\n\n ```\n gkectl update admin --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config ADMIN_CLUSTER_CONFIG\n ```\n\nUpdate the backup datastore\n\nYou can update the datastore where backups are stored by updating `clusterBackup.datastore` to reflect the new location. The new datastore must be in the same datacenter as the admin cluster.\n\n1. Edit the admin cluster configuration file to change the `clusterBackup.datastore` value.\n\n ```\n clusterBackup:\n datastore: new-datastore\n ```\n2. Update the admin cluster with this change, using this command:\n\n ```\n gkectl update admin --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config ADMIN_CLUSTER_CONFIG\n ```\n\nOn-demand backup\n\nTo trigger an on-demand admin cluster backup, run the following command:\n\n\u003cbr /\u003e\n\n```\ngkectl backup admin --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config ADMIN_CLUSTER_CONFIG\n \n```\n\n\u003cbr /\u003e\n\nLimit on number of backups\n\nYou can have a maximum total of six backups, divided into a maximum of three on-demand backups, and a maximum of three backups from cluster update, upgrade or create operations. These backups are automatically rotated should these limits be exceeded. No manual intervention is necessary.\n\nRestore an admin cluster **Warning:** Using a backup to restore your admin cluster is a last resort. We do not recommend that you restore from a backup file unless the admin cluster is completely broken. Contact Google Support for help in deciding the best course of action.\n\nYou should restore an admin cluster only when it is completely broken with data loss or corruption. For example,\n\n- The admin master data disk is lost or corrupted.\n- The admin cluster's etcd is lost or corrupted.\n- The admin cluster's control plane secrets and certificates are lost or corrupted.\n\nDo not use this approach to restore a working admin cluster to an arbitrary previous state. This restore feature should not be used as a way to revert admin cluster operations such as a cluster update or cluster upgrade.\n\nDo not use this approach to restore HA admin cluster. For HA admin cluster we only support `gkectl repair admin-master`, but not `gkectl repair admin-master --restore-from-backup`.\n\nTo recreate the admin cluster from a backup, run the following command:\n\n\u003cbr /\u003e\n\n```\n gkectl repair admin-master --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config ADMIN_CLUSTER_CONFIG --restore-from-backup\n \n```\n\n\u003cbr /\u003e\n\nThis command retrieves all of the backups of this admin cluster from the datastore defined in the `clusterBackup` section of the admin cluster configuration file, and it prompts you to select the one from which you want to use to restore the admin cluster."]]
