[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-17。"],[],[],null,["# About backups\n\nThis page provides details about backups, backup vaults, and backup policies.\n\nVolume backups\n--------------\n\nNetApp Volumes supports volume backups, which are copies of your\nvolumes stored independently from the volume. Backups are stored in backup\nvaults, which are containers for backups. If a volume is lost or deleted,\nyou can use backups to restore your data to a new volume.\n\nWhen you create the first backup of a volume, all of the volume's used data is\nsent to the backup vault. Subsequent backups of the same volume only include\ndata that has changed from the previous backup. This allows for fast\nincremental-forever backups and reduces the required capacity inside the\nbackup vault.\n\nYou can create manual and scheduled backups. Manual backups can be taken from a\nvolume or from an existing volume snapshot. Scheduled backups require a backup\npolicy.\n\n### Considerations\n\n- Backups aren't supported for volumes protected with customer-managed\n encryption keys (CMEK).\n\n- You can restore backups of large capacity volumes only to a new large capacity\n volume. The regular volume backups can't be restored to large capacity\n volumes and the other way around.\n\n- Backups are supported with volume replication. Source volumes allow you to\n use scheduled backups or to create manual backups. For destination volumes,\n you must use manual backups. If you try to assign a backup policy to a\n destination volume, it will fail. When you reverse a volume replication\n direction, remove the backup policy first from the future destination\n volume.\n\n- Before you use VPC Service Controls, see [Limitations of VPC Service Controls for NetApp Volumes](/netapp/volumes/docs/before-you-begin/service-perimeter#limitations) for more information.\n\n- If you have set a **Minimum enforced retention** policy on a backup vault that\n contains the backup, the backup can't be deleted before the scheduled date in\n the **Deletable on** field. For more information, see [Prevent backup deletion](/netapp/volumes/docs/protect-data/about-backups#prevent_backup_deletion).\n\nBackup vaults\n-------------\n\nBackup vaults are logical containers that store volume backups. You can create\nmultiple backup vaults within each region, and each vault can store multiple\nbackups for multiple volumes in that region.\n\nThere are two types of backup vaults that can exist in a region:\n\n- **In-region backup vaults**: store backups in the same region as the original\n volume.\n\n- **Cross-region backup vaults**: store backups of a volume in a different\n region. When you create a cross-region vault, a source vault is created in the\n volume region, and a destination vault is automatically created in the\n specified destination region. Both vaults store the backup metadata, but only\n the destination vault stores the actual backup data. This allows volumes and\n backups to exist in different regions.\n\n The source vault and the volumes you want to backup must be in the same\n region.\n\n You can restore backups from the source or destination vault by creating a\n new volume in the vault's location.\n\n You must specify a name for the source vault while destination vaults are\n automatically named using the following template:\n\n `\u003csource_vault_name\u003e-destination-\u003c4-random-letters\u003e`\n\n### Considerations\n\n- Volumes can only store backups in one vault.\n\n- You can only backup a volume to a backup vault in the same region.\n\n- In-region backup vaults are generally available (GA) for all service levels.\n You can restore backups located in in-region vaults to any storage pool, for\n any service level, in the backup's region.\n\n- Cross-region backup vaults are supported for Standard, Premium, and Extreme\n service levels and aren't available for the Flex service level. You can\n restore backups located in cross-region vaults to any pool in either the\n source or destination backup vault location.\n\n- When you create a backup vault, you can optionally specify a minimum retention\n period to apply to each new backup stored in the vault. This retention period\n applies to all existing and future backups of the selected backup types stored\n in that vault. For more information, see [Prevent backup deletion](/netapp/volumes/docs/protect-data/about-backups#prevent_backup_deletion).\n\n- You can't change the type of an existing backup vault.\n\nRegion groups\n-------------\n\nYou can create cross-region backup vaults between regions that are part of the\nsame region group. However, you can only restore existing backups by creating a\nnew volume in the source or destination backup vault region. For more\ninformation about region groups across different locations, see\n[volume replication](/netapp/volumes/docs/protect-data/about-volume-replication#considerations_for_volume_replication).\n\nBackup policies\n---------------\n\nBackup policies define a schedule for automated backup creation. You can specify\nhow many daily, weekly, and monthly backups of the volume you want\nNetApp Volumes to retain. If a policy is attached to a volume and\nenabled, then backups are generated automatically.\n\nThe number of backups to store as defined in the policy must align with the\nretention period configured in the backup vault. For more information, see\n[Prevent backup deletion](/netapp/volumes/docs/protect-data/about-backups#prevent_backup_deletion).\n\n### Scheduled backups\n\nScheduled backups use the following backup name format to help you identify the\nexact point in time each backup was taken:\n\n`(daily|weekly|monthly)-scheduled-backup-\u003cid\u003e-\u003ctimestamp\u003e`\n\nThe timestamp is UTC in the following format:\n\n`\u003cYYYY\u003e-\u003cMM\u003e-\u003cDD\u003e-\u003chhmmss\u003e`\n\nYou can't specify the exact time a scheduled backup is created. Scheduled\nbackups that use a backup policy retain the number of specified daily, weekly,\nand monthly backups. When the maximum amount of backups retained is reached, the\noldest backup is deleted.\n\nPrevent backup deletion\n-----------------------\n\n| **Note:** The prevent backup deletion feature is supported for all service levels in the allow-listed General Availability (GA) and isn't open by default. To request access to this feature, contact [sales](https://cloud.google.com/contact?).\n\nThe contents of a backup can't be modified. However, IAM users\nwith the [appropriate permissions](/netapp/volumes/docs/get-started/configure-access/iam)\ncan delete backups. To protect against accidental or malicious deletions by\nadministrators, you have the option to set a retention period for backups that\nprevents their deletion before that period expires.\n\n### Considerations\n\n- You can enable this feature on a backup vault by specifying a retention\n period which must be between 2 to 5475 days, and the type of backups to\n retain.\n\n- You can choose to retain daily, weekly, monthly, or manual backups. You must\n select at least one backup type.\n\n- Each backup created in the vault is assigned an expiry date, calculated by\n adding the vault's retention period to the backup's creation time. The backup\n can't be deleted before this expiry date.\n\n- The scheduled backups are also protected by deletion prevention.\n\n- After you set the minimum retention period for a backup vault, the following\n considerations are applicable:\n\n - The minimum retention period for a backup vault is permanent and can only\n be increased, but can't be decreased. If you increase the retention period,\n it adds the extra time to the current expiry date of each existing backup\n within the vault.\n\n - The backup types you choose to retain can't be modified. However, you can\n add the new backup types.\n\n - Make sure that backups are scheduled and retained for a duration that meets\n or exceeds the defined backup retention period.\n\n For example, if your backup policy specifies 14 daily backups, but you have\n set a retention period of 30 days for daily backups in the vault, the\n scheduler will cause issues. The system tries to delete the oldest daily\n backup after 14 days, but will be blocked until the 30-day retention period\n ends. It is essential to plan your retention period, the type of backups to\n retain, and your backup policy carefully. Note that a volume can hold a\n maximum of 1,000 backups, between manual and scheduled. Once this limit is\n reached, the older backups can't be deleted, and no new backups can be\n created.\n - You are charged for backups. If you use this feature, you can't delete\n backups before they reach their expiry date. Therefore, it is recommended to\n plan this feature usage carefully.\n\nWhat's next\n-----------\n\n[Set up volume backups](/netapp/volumes/docs/protect-data/set-up-volume-backups)."]]