이 페이지에서는 Google Distributed Cloud (GDC) 오프라인 환경에서 클러스터 워크로드의 백업 계획을 만들고 관리하는 방법을 설명합니다.
백업 계획은 백업 시퀀스의 구성, 위치, 관리 기능을 제공합니다. 백업 계획에는 소스 클러스터와 백업할 워크로드 선택을 포함한 백업 구성이 포함됩니다. 모든 클러스터에 하나 이상의 백업 계획을 제공하는 것이 좋습니다.
각 클러스터에 백업 계획을 하나 이상 만들 수 있습니다. 다음과 같은 이유로 클러스터의 백업을 파티셔닝할 수 있습니다.
하루에 한 번 대규모로 백업을 수행하는 대신 하루 중 여러 번 소규모로 백업을 수행합니다.
클러스터의 일부를 다른 것보다 더 자주 백업합니다(예: 일부 네임스페이스의 경우 매일 백업, 다른 것은 시간별 백업).
단일 클러스터 또는 가상 머신 (VM)은 하나 이상의 백업 계획에 속할 수 있습니다. 백업 계획은 두 개 이상의 클러스터에 걸쳐 있을 수 없지만, 단일 백업 계획은 동일한 클러스터에 있는 경우 여러 VM을 캡처할 수 있습니다. 모든 백업 및 복원 리소스는 프로젝트 이름과 연결되어야 합니다.
시작하기 전에
백업 계획을 만들려면 다음이 필요합니다.
필요한 ID 및 액세스 역할:
사용자 클러스터 백업 관리자: 사용자 클러스터의 백업 및 복원 계획과 같은 백업 리소스를 관리합니다. 조직 IAM 관리자에게 사용자 클러스터 백업 관리자 (user-cluster-backup-admin) 역할을 부여해 달라고 요청하세요. 자세한 내용은 역할 정의를 참고하세요.
애플리케이션 운영자인 경우 사용자 클러스터 백업 관리자 권한이 있는 관리자에게 백업 계획을 만들어 달라고 요청하세요.
백업 계획 만들기
해당 일정에 따라 백업이 자동으로 생성되도록 백업 계획의 크론 일정을 정의하는 것이 좋습니다. 워크로드를 수동으로 백업할 수도 있습니다. 자세한 내용은 수동 백업 만들기를 참고하세요.
클러스터 네임스페이스 수정을 클릭한 다음 클러스터 네임스페이스 추가를 클릭하여 네임스페이스를 입력합니다.
이 클러스터 내에서 선택된 보호되는 애플리케이션을 클릭하고 네임스페이스와 애플리케이션 이름을 지정하여 리소스를 추가합니다.
보호된 애플리케이션 수정을 클릭한 다음 보호된 애플리케이션 추가를 클릭하여 네임스페이스와 보호된 애플리케이션을 입력합니다.
보안 비밀 포함을 클릭하여 Kubernetes Secret 리소스를 포함합니다.
백업에 볼륨 데이터를 포함하려면 영구 볼륨 데이터 포함을 클릭합니다. 복원 중에 빈 볼륨을 만들려면 이 체크박스를 선택 취소합니다.
일정 및 보관 섹션에서 다음 단계를 완료하고 계속을 클릭합니다.
일정을 정의하려면 CRON 문자열 필드에 표준 크론 구문을 사용하여 표현식을 입력합니다. 예를 들어 10 3 * *
* 표현식은 매일 오전 3시 10분에 백업을 만듭니다. 모든 시간은 UTC로 해석됩니다. 예약된 백업 간의 최소 간격은 10분입니다.
다음 기간이 지나면 백업 삭제 필드에서 백업을 보관할 일수를 설정합니다. 일수가 지나면 백업이 자동으로 삭제됩니다.
백업을 삭제할 수 없는 기간의 일수를 설정합니다.
보관 정책을 잠그려면 자물쇠 아이콘을 클릭하여 잠금을 끄기에서 켜기로 전환합니다.
백업 계획 세부정보를 검토하고 계획 만들기를 클릭합니다.
API
클러스터에 ClusterBackupPlan 커스텀 리소스를 만들어 백업을 예약합니다. 백업 계획은 backupSchedule에 따라 주기적으로 백업을 예약합니다.
ClusterBackupPlan 리소스는 네임스페이스 리소스입니다. ClusterBackupPlan의 예는 다음과 같습니다.
[[["이해하기 쉬움","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\u003eBackup plans in Google Distributed Cloud (GDC) air-gapped define the configuration, location, and management for a series of backups, allowing for multiple smaller backups throughout the day or differing backup frequencies for different parts of a cluster.\u003c/p\u003e\n"],["\u003cp\u003eEach cluster should have at least one backup plan, and a single cluster or virtual machine (VM) can be part of multiple backup plans, although a plan cannot span across multiple clusters.\u003c/p\u003e\n"],["\u003cp\u003eBackup plans can be created and managed through the GDC console or the API, with options to back up the entire cluster, specific namespaces, or selected applications, and the ability to include secrets and persistent volume data.\u003c/p\u003e\n"],["\u003cp\u003eBackup plans can be scheduled using cron syntax, and users can set retention policies for backups, including how long to keep backups and for how many days they are prevented from being deleted.\u003c/p\u003e\n"],["\u003cp\u003eBackup plans can be viewed, edited, and deactivated through the GDC console by users with the appropriate roles, with deactivation preventing future backups without deleting existing ones.\u003c/p\u003e\n"]]],[],null,["# Plan a set of backups\n\nThis page describes how to create and manage backup plans for cluster workloads in Google Distributed Cloud (GDC) air-gapped.\n\n*Backup plans* provide the configuration, location, and management functions for\na sequence of backups. A backup plan contains a backup configuration, including\nthe source cluster and the selection of workloads to back up. Google recommends\nproviding every cluster with at least one backup plan.\n\nYou can create one or more backup plans for each cluster. You might want to\npartition the backups of your cluster for one of the following reasons:\n\n- Instead of having one very large backup taken at a single time of the day, you want multiple smaller backups distributed throughout the day.\n- You want to back up some portions of your cluster more often than others, such as daily backups for some namespaces and hourly backups for others.\n\nA single cluster or virtual machine (VM) can belong to one or more backup plans.\nA backup plan cannot span more than one cluster; however, a single backup plan\ncan capture multiple VMs if they exist in the same cluster. All backup\nand restore resources must be associated with a project name.\n\nBefore you begin\n----------------\n\nTo create a backup plan, you must have the following:\n\n- The necessary identity and access role:\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. For more information, see [Role definitions](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/iam/role-definitions).\n- If you are an Application Operator, ask your administrator that has User Cluster Backup Admin privileges to create a backup plan for you.\n\nCreate a backup plan\n--------------------\n\nWe recommend that you define a cron schedule for the backup plan, so that\nbackups are automatically created according to that schedule. You can also\nmanually back up your workloads. For more information, see [Create a manual backup](/distributed-cloud/hosted/docs/latest/gdch/platform-application/pa-ao-operations/back-up-workloads#create-manual-backup).\n\nCreate backup plans using the GDC console or the API. \n\n### Console\n\n1. Sign in to the GDC console.\n2. In the navigation menu, click **Backup for Clusters**.\n3. Click **Create Backup Plan**.\n4. In the **Plan details** section, complete the following steps and click **Continue** :\n 1. In the **Cluster** list, select the cluster to back up.\n 2. In the **Project** list, select the project.\n 3. In the **Backup plan name** field, enter your chosen backup plan name.\n 4. (Optional) In **Backup plan description** enter a description for the backup plan.\n 5. In the **Backup repo** field, select a backup repository. Backup repositories are a set of object storage implementations.\n 6. Click **Next**.\n5. In the **Scope and encryption** section, complete the following steps\n and click **Continue**:\n\n 1. Select one of the following scopes for the backup plan:\n\n 1. Click **Entire cluster** to back up all namespace resources in the backup.\n 2. Click **Selected namespaces within the cluster** to choose the namespaces in the backup to restore.\n 1. Click **Edit Cluster Namespace** and then **Add Cluster\n Namespace** to enter a **Namespace**.\n 3. Click **Selected protected applications within this cluster** to add resources by specifying the namespace and the application name.\n 1. Click **Edit Protected Applications** and then **Add\n Protected Application** to enter a **Namespace** and **Protected Application**.\n 2. Click **Include Secrets** to include Kubernetes `Secret` resources.\n\n 3. Click **Include persistent volume data** if you want the volume data\n in your backup. Clear this checkbox if you want to create empty\n volumes during the restore.\n\n6. In the **Schedule and retention** section, complete the following steps\n and click **Continue**:\n\n 1. To define a schedule, enter an expression using standard cron syntax in the **CRON string** field. For example, the expression `10 3 * *\n *` creates a backup at 0310 every day. All times are interpreted as UTC. The minimum interval between scheduled backups is 10 minutes.\n 2. In the **Delete backups after** field, set the number of days for which to retain the backup. Once the number of days is reached, the backup is automatically deleted.\n 3. Set the number of days during which backups cannot be deleted.\n 4. To lock the retention policy, click the lock icon to turn the lock from **Off** to **On**.\n7. Review the backup plan details and click **Create Plan**.\n\n### API\n\nCreate a `ClusterBackupPlan` custom resource in the cluster to schedule backups. A\nbackup plan periodically schedules backups based on the `backupSchedule`.\n`ClusterBackupPlan` resources are namespace resources. Here's an example of a `ClusterBackupPlan`: \n\n apiVersion: backup.gdc.goog/v1\n kind: ClusterBackupPlan\n metadata:\n name: backup-plan\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 targetCluster:\n targetClusterType: UserCluster\n targetClusterName:\n kind: \"Cluster\"\n name: \"cluster-sample\"\n backupSchedule:\n cronSchedule: \"*/30 * * * *\"\n paused: false\n clusterBackupConfig:\n backupScope:\n selectedNamespaces:\n namespaces: [\"nginx\"]\n clusterBackupRepositoryName: backup-repository\n retentionPolicy:\n backupDeleteLockDays: 10\n backupRetainDays: 10\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\nAfter a backup plan is created, backups are automatically created with the\nspecified backup configuration based on the backup schedule.\n\nView a backup plan\n------------------\n\nView a backup plan using the GDC console:\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 backup plans in an organization or select a project to see all backup plans in a project.\n - Backup Creator: Select a project to see all backup plans in a project.\n4. Click the **Backup Plans** tab.\n5. Click a backup plan in the list to view its details. Users with User Cluster Backup Admin privileges can view all backup plans in the organization. Users with the Backup Creator role can view all backup plans in the selected project.\n\nEdit a backup plan\n------------------\n\nEdit a backup plan using the GDC console:\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 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 that you want to edit.\n6. Click the **Plan Configuration** tab to view the fields that can be modified.\n7. Click the *edit* Edit icon for **Schedule and retention** to edit that resource:\n\n 1. To update a schedule, enter an expression using standard cron syntax in the **CRON string** field. For example, the expression `10 3 * * *` creates a backup at 0310 every day. All times are interpreted as UTC. The minimum interval between scheduled backups is 10 minutes.\n 2. In the **Delete backups after** field, set the number of days for which to retain the backup. Once the number of days is reached, the backup is automatically deleted.\n 3. In the **Prevent deletion for** field, set the number of days during which backups cannot be deleted.\n\n | **Note:** If both fields are enabled, the value of the **Prevent deletion for** field must be less than the value of the **Delete backups after** field.\n 4. To lock the retention policy, click the lock icon\n from **Off** to **On**.\n\n | **Note:** Once the retention policy is locked, you won't be able to edit the retention policy of this backup plan again. You can only update the schedule.\n 5. Click the **Save** button to confirm your changes.\n\nDeactivate a backup plan\n------------------------\n\nDeactivate a backup plan using the GDC console:\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 backup plans in an organization or select a project to see all backup plans in a project.\n - Backup Creator: Select a project to see all backup plans in a project.\n4. Click the **Backup Plans** tab.\n5. Click the name of the backup plan you want to deactivate.\n6. Click the **Deactivate Plan** button.\n7. Enter the name of the backup plan you are deactivating into the field.\n8. Click the **Deactivate** button to complete the deactivation of this backup plan.\n\n | **Note:** This operation cannot be undone. Deactivating the backup plan does not delete the backups contained within it, but no new backups can be created automatically or manually.\n\nWhat's next\n-----------\n\n- [Back up your workloads](/distributed-cloud/hosted/docs/latest/gdch/platform-application/pa-ao-operations/cluster-backup/back-up-workloads)"]]
