백업 계획으로 백업 일정이 정의된 경우 해당 일정에 따라 백업이 자동으로 생성됩니다. 백업 계획 일정 범위 밖에서 백업을 수동으로 만들 수도 있습니다. 예를 들어 애플리케이션을 업그레이드하기 전 워크로드를 백업해야 할 수 있습니다. 백업에는 노드 구성, 노드 풀, 초기 클러스터 크기, 사용 설정된 기능과 같은 클러스터 구성 정보가 포함되지 않습니다.
백업에는 두 가지 데이터 형태가 캡처됩니다.
구성 백업: 백업을 진행 중인 클러스터의 API 서버에서 추출한 Kubernetes 리소스 설명 집합입니다.
볼륨 백업: PersistentVolumeClaims의 백업입니다.
콘솔
GDC 콘솔에 로그인합니다.
탐색 메뉴에서 Backup for Clusters를 클릭합니다.
백업 계획 탭을 클릭합니다.
백업에 사용할 요금제를 클릭합니다.
백업 시작을 클릭합니다.
백업 이름과 설명(선택사항)을 입력합니다.
백업을 보관할 일수를 설정합니다. 이 일수가 지나면 백업이 자동으로 삭제됩니다.
백업을 삭제할 수 없는 기간의 일수를 설정합니다.
시작을 클릭합니다.
API
수동 백업은 백업 구성에 대한 기존 백업 계획을 참조해야 하며 백업은 ManualClusterBackupRequest를 실행하여 생성해야 합니다.
[[["이해하기 쉬움","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)"],[[["\u003cp\u003eThis page guides users on managing cluster workload backups in Google Distributed Cloud (GDC) air-gapped environments, covering the creation, viewing, and deletion of backups.\u003c/p\u003e\n"],["\u003cp\u003eCreating manual backups can be done through the GDC console or API, referencing an existing backup plan, and users must have appropriate roles, either User Cluster Backup Admin or Backup Creator.\u003c/p\u003e\n"],["\u003cp\u003eUsers can view backups through the GDC console or \u003ccode\u003ekubectl\u003c/code\u003e, with visibility determined by their assigned role: User Cluster Backup Admins can view all backups, while Backup Creators can only see backups within their project.\u003c/p\u003e\n"],["\u003cp\u003eDeleting backups requires using the GDC console or a \u003ccode\u003eDeleteClusterBackupRequest\u003c/code\u003e via API, and it is important to note that deleting backups is an irreversible action.\u003c/p\u003e\n"],["\u003cp\u003eBackups consist of config backup, a set of kubernetes resource descriptions, and volume backup, a backup of PersistentVolumeClaims, but it does not include cluster configurations.\u003c/p\u003e\n"]]],[],null,["# Back up your workloads\n\nThis page details how to create manual backups, view existing backups, and delete existing backups for cluster workloads in Google Distributed Cloud (GDC) air-gapped.\n\nBefore you begin\n----------------\n\nTo create, view, and delete backups, you must have the following:\n\n- The necessary identity and access role:\n\n - For Platform Administrator (PA) users:\n - User Cluster Backup Admin: manages backup resources such as backup and restore plans in user clusters. Ask your Organization IAM Admin to grant you the User Cluster Backup Admin (`user-cluster-backup-admin`) role.\n - For Application Operator (AO) users:\n - Backup Creator: creates manual backups and restores. Ask your Project IAM Admin to grant you the Backup Creator (`backup-creator`) role.\n - For more information, see [Role definitions](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/iam/role-definitions).\n- AO users can only perform manual backups from an existing backup\n plan.\n\nCreate a manual backup\n----------------------\n\nIf your backup plan defines a schedule for the backup, the backups are\nautomatically created according to that schedule. You can also manually create a backup\noutside the scope of your backup plan schedule. For example, you might want to back\nup your workloads before you upgrade your applications. A backup does not\ninclude cluster configuration information, such as node configurations, node\npools, initial cluster size, or what features are enabled.\n\nTwo forms of data are captured in a backup:\n\n- **Config backup**: A set of Kubernetes resource descriptions extracted from the API server of the cluster undergoing backup.\n- **Volume backup** : A backup of `PersistentVolumeClaims`.\n\n### Console\n\n1. Sign in to the GDC console.\n2. In the navigation menu, click **Backup for Clusters**.\n3. Click the **Backup Plans** tab.\n4. Click the plan that you want to use for the backup.\n5. Click **Start a backup**.\n6. Enter a backup name and an optional description.\n7. Set the number of days to retain the backup. Once this number of days is reached, the backup is automatically deleted.\n8. Set the number of days during which backups cannot be deleted.\n9. Click **Start**.\n\n### API\n\nThe manual backup must reference an existing backup plan for the backup\nconfiguration and the backup must be created by issuing a\n`ManualClusterBackupRequest`.\n\nHere's an example of a `ManualClusterBackupRequest`: \n\n apiVersion: backup.gdc.goog/v1\n kind: ManualClusterBackupRequest\n metadata:\n name: manualbackuprequest-test\n namespace: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePROJECT_NAME\u003c/span\u003e\u003c/var\u003e\n spec:\n clusterBackupName: \"backup-test\"\n clusterBackupPlanRef: \"backupplan-test\"\n deleteLockDays: 5\n retainDays: 6\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT_NAME\u003c/var\u003e with the name of your GDC project.\n\nThis example includes the following values:\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nView a backup\n-------------\n\nUsers with the User Cluster Backup Admin (`user-cluster-backup-admin`) role can see all backups in the organization.\nUsers with the Backup Creator (`backup-creator`) role can see all of the backups in a project. \n\n### Console\n\n1. Sign in to the GDC console.\n2. In the navigation menu, click **Backup for Clusters**.\n3. Click **Select project** to select an organization or project depending on your role:\n - User Cluster Backup Admin: Select an organization to see all backups in an organization or select a project to see all backups in a project.\n - Backup Creator: Select a project to see all backups in a project.\n4. Click the **Backups** tab.\n5. Click a backup in the list to view its details.\n\n### kubectl\n\nView a list of your backups: \n\n kubectl get clusterBackups\n\nAn example of the output: \n\n NAME STATE\n backup-test Succeeded\n\nDelete a backup\n---------------\n\nBackups can't be deleted by a regular interaction with the Kubernetes API\nserver. To delete a backup, use the GDC console or issue a `DeleteClusterBackupRequest`. \n\n### Console\n\nDelete the backup from the **Backups** tab:\n\n1. Sign in to the GDC console.\n2. In the navigation menu, click **Backup for Clusters**.\n3. Click **Select project** to select an organization or project depending on your role:\n - User Cluster Backup Admin: Select an organization to see all backups in an organization, or select a project to see all backups in a project.\n - Backup Creator: Select a project to see all backups in a project.\n4. Click the **Backups** tab.\n5. Click the three-dot menu icon for the backup you want to delete.\n6. Type the name of the backup into the text box.\n7. Click the **Delete Backup** button to complete the deletion of this backup.\n\n | **Note:** This operation can't be undone.\n\nAlternatively, delete the backup by clicking on the backup name when viewing a backup plan:\n\n1. Sign in to the GDC console.\n2. In the navigation menu, click **Backup for Clusters**.\n3. Click **Select project** , and select an organization or project depending on your role:\n - User Cluster Backup Admin: Select an organization to see all of the backup plans in an organization, or select a project to see all of the backup plans in a project.\n - Backup Creator: Select a project to see all of the backup plans in a project.\n4. Click the **Backup Plans** tab.\n5. Click the name of the backup plan containing the backup you want to delete.\n6. Click the **Backups** tab.\n7. Click the name of the backup you want to delete.\n8. Click the **Delete Backup** button.\n9. Enter the name of the backup into the text field.\n10. Click the **Delete** button to complete the deletion of this backup.\n\n | **Note:** This operation can't be undone.\n\n### kubectl\n\nSend a `DeleteClusterBackupRequest` request: \n\n apiVersion: backup.gdc.goog/v1\n kind: DeleteClusterBackupRequest\n metadata:\n name: deletebackuprequest-test\n namespace: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePROJECT_NAME\u003c/span\u003e\u003c/var\u003e\n spec:\n clusterBackupRef: \"backup-test\"\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT_NAME\u003c/var\u003e with the name of your GDC project.\n\nThis example includes the following values:\n\n- `backupName`: the name of the backup being deleted. This backup must exist in the same namespace as the `DeleteClusterBackupRequest`.\n- `DeleteClusterBackupRequest`: the resource that deletes the backup custom resource from the cluster and removes all artifacts associated with that backup from the storage location of the backup, including volume data.\n\n| **Note:** Attempting to delete a `ClusterBackup` resource without applying a `DeleteClusterBackupRequest` resource doesn't clean object storage artifacts and might result in undefined behavior.\n\nWhat's next\n-----------\n\n- [Plan a set of restores](/distributed-cloud/hosted/docs/latest/gdch/platform-application/pa-ao-operations/cluster-backup/plan-restores)"]]
