[[["容易理解","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 (世界標準時間)。"],[[["\u003cp\u003eBackup and DR Service is a managed service for backing up and recovering workloads in Google Cloud, offering centralized management, monitoring, and reporting.\u003c/p\u003e\n"],["\u003cp\u003eThe service supports two types of backup storage: backup vaults, which provide immutability and indelibility, and self-managed storage, which allows for multi-region backups and CMEK-encryption.\u003c/p\u003e\n"],["\u003cp\u003eBackup plans define backup frequency, storage location, and retention periods, and can be created in either the Google Cloud console (using backup vaults) or the Backup and DR management console (supporting both storage options).\u003c/p\u003e\n"],["\u003cp\u003eCompute Engine instances, Google Cloud VMware Engine VMs, and self-managed databases like Oracle and SQL Server are supported for backup, with varying features depending on whether the plans are set up in the Management console or Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eBackup vaults have a minimum enforced retention period, ensuring backups cannot be modified or deleted, while self-managed storage does not offer these guarantees but instead offers more storage flexibility.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service overview\n\nThis page provides an overview of Google Cloud Backup and DR Service\ncapabilities, key benefits, what you can back up, and how it works.\n| **Note:** Google Cloud offers a 30-day introductory trial for Backup and DR Service. You can enable the trial to gain insights into your Cloud Storage usage and take actions. For more information about the trial, see [30-day introductory trial for\n| Backup and DR Service](/backup-disaster-recovery/docs/30-day-introductory-trial/intro-trial).\n\nWhat is Backup and DR Service?\n------------------------------\n\nBackup and DR Service is a managed service that provides backup and recovery of\nworkloads running in Google Cloud. Backup and DR Service provides centralized management,\nmonitoring, and reporting of day to day backup operations all from one place.\nThe service supports seamless integration with existing automation using\nTerraform and APIs.\n\nBackup and DR Service provides the following capabilities:\n\n- Centralized backup management\n- Policy-based backup management\n- Comprehensive monitoring and reporting\n- Incremental backups for faster RPO and lower TCO\n- Backup storage: the service supports two types of storage for backups:\n\n - A backup vault is a Google-managed secured and isolated storage\n resource, managed by Backup and DR Service. Backup vault provides the\n following features:\n\n - **Immutability**: your data cannot be changed\n - **Indelibility**: your data cannot be deleted\n\n Backup vault storage is supported for Compute Engine instances,\n Google Cloud VMware Engine VMs, and self-managed Oracle and Microsoft SQL Server\n databases running inside VMs or Bare Metal Solution.\n - Self-managed storage refers to storage resources, excluding backup vaults,\n that you can directly access and manage yourself. Because you manage the\n storage, it can be deleted prematurely by any user who has sufficient\n storage permissions.\n\nWhether using backup vaults or self-managed storage, you create backup plans for your data resources that you have to\nprotect. A backup plan defines when to back up a resource, where to store the\nbackup, and how long to retain the backups.\n\n### Backup vaults\n\nA backup vault is secured and isolated storage, managed by\nBackup and DR Service.\nA backup vault can store backups in a region or in a multi-region,\nas long as the selected location is\n[compatible with the workload location](/backup-disaster-recovery/docs/concepts/backup-vault#workload-location-compatibility).\n\nBackup vault. Backup vaults can be created in these\n[supported locations](/backup-disaster-recovery/docs/concepts/backup-vault#locations).\n\nThe minimum enforced retention period, a property of backup vault,\nensures that backups are strongly secured against modification and deletion for\nthe timeframe you define. You can specify the minimum enforced retention period\nup to 99 years.\n\nYou create, access, and manage backup vaults using Backup and DR Service in\nthe Google Cloud console.\n\nFor full details on backup vaults, see\n[Backup and DR Service backup vault storage](/backup-disaster-recovery/docs/concepts/backup-vault).\n\n### Self-managed storage\n\nSelf-managed storage includes Persistent Disk snapshots and backups in\nCloud Storage buckets that are created to store backup data in your Google Cloud projects.\n\n- The Backup and DR management console is an interface for managing backup to self-managed storage.\n\n| **Note:** To store backups on immutable, indelible storage managed by Backup and DR Service, see [backup vault](/backup-disaster-recovery/docs/concepts/backup-dr#backup-vaults).\n\nBackup plans\n------------\n\nThere are some important differences between backup plans created in the\nGoogle Cloud console and backup plans created in the management console, as described\nin the following table.\n\nBackup plans created in the Google Cloud console use backup vault storage.\n| **Note:** Backup vault storage doesn't support protection of CMEK-encrypted workloads, so if you need those features, set up a backup plan in the Backup and DR management console, using self-managed storage.\n\n### Backup plans created in the Google Cloud console\n\nWhen you create a backup plan in the Google Cloud console, it consists of the following:\n\n- A backup vault storage destination for the backups.\n- One or more backup rules. Backup rules define the following:\n\n - The frequency of backup creation: hourly, daily, weekly, monthly, or yearly.\n - The backup window, the specific day and time of day for the backup job to start and the time by which it must be finished.\n - How long to retain the backup before automatically expiring it.\n\nBackups automatically expire and are deleted after the backup retention period\nis reached. Backups stored in backup vaults are immutable and indelible;\nthey cannot be modified or deleted for the duration of the\nbackup vault's minimum enforced retention period.\n\nYou create a backup plan with backup vault storage from the\nBackup and DR product in the Google Cloud console.\n\nWhen you create a backup plan with backup vault storage, you must select\nan existing backup vault as the storage location for your backups.\nThe backup plan must exist in a\n[location that the workload is compatible with](/backup-disaster-recovery/docs/concepts/backup-vault#workload-location-compatibility).\nAlso, the backup vault must exist when you create the backup plan.\n\n### Backup plans created in the management console\n\nBackup plans are created in the Backup and DR management console and\nthe backup jobs are run on specialized Google Cloud VMs called\nbackup/recovery appliances that you deploy in your own Google Cloud projects.\nThe management console **Backup Plans** tab provides two easy-to-use wizards to\ncreate a data-handling policies that will be applied to your applications:\n\n- Templates: Use the Templates wizard to control the frequency and retention of data. You can also perform data tiering and replication using the Templates wizard, for more information see [Create a backup template](/backup-disaster-recovery/docs/create-plan/create-template#create-temp).\n- Profiles: Use the Profiles wizard to control the physical location and storage pools where data is stored. For more information, see [Create a resource profile](/backup-disaster-recovery/docs/create-plan/create-resource-profiles#create-profile).\n\nBackups automatically expire and are deleted after the backup retention period is reached.\n\nBack up Compute Engine instances\n--------------------------------\n\nCompute Engine instances can be backed up using the Backup and DR\nmanagement console into self-managed storage, and using the Google Cloud console into\nbackup vaults.\n\nBack up Google Cloud VMware Engine VMs\n--------------------------------------\n\nGoogle Cloud VMware Engine VMs are fully supported in the Backup and DR\nmanagement console for both backup vault and self-managed storage.\n\nBack up self-managed Oracle and SQL Server databases\n----------------------------------------------------\n\nSelf-managed Oracle and SQL Server databases are the following databases running\ninside a VM or Bare Metal Solution in your project:\n\n- Oracle databases running on Bare Metal Solution, Compute Engine VMs, or Google Cloud VMware Engine VMs\n- SQL Server databases running on Compute Engine or Google Cloud VMware Engine VMs\n\nThese self-managed databases can be backed up from the Backup and DR\nmanagement console into backup vaults or into self-managed storage.\n\nRestore your data\n-----------------\n\nAfter you have backed up your data, you can restore it to its original location\nor to a different location. You can restore entire virtual machines, specific\ndisks, or individual files. To learn more about how to restore your data, see\nthe [Restore data overview](/backup-disaster-recovery/docs/restore-data/restore-overview).\n\nPricing\n-------\n\nRefer to [Backup and DR Service pricing](/backup-disaster-recovery/pricing) for pricing details.\n\nWhat's next\n-----------\n\nThe following quickstart guides can help you begin a backup and recovery workflow for your application:\n\n- [Protect and recover Compute Engine instances](/backup-disaster-recovery/docs/quickstarts/gce-instances-backup-vault).\n\n- [Protect and recover VMware VMs](/backup-disaster-recovery/docs/quickstarts/vmware-backup-recovery)."]]
