What is Backup and DR Service?

This page provides an overview of Google Cloud Backup and DR Service and how it works.

Google Cloud Backup and DR Service is a powerful, centralized, cloud-first backup and disaster recovery solution for cloud-based and hybrid workloads. Backup and DR Service enables you to recover your data quickly, supporting rapid resumption of critical business operations.

How it works

Backup and DR Service stores backup data in its original, application-readable format, resulting in many workloads being made available directly from long-term backup storage with no need for time-consuming data movement or translation.

After an initial full backup is performed, your data (general applications, VMware VMs, Compute Engine VMs, databases, and file systems) is backed up incrementally, updating and storing any data that has changed since the last backup.

All backups are executed on a backup/recovery appliance that can be located in the same region and zone as the workload. The backup/recovery appliances are managed using the Backup and DR management console, which uses object and job metadata provided by the backup/recovery appliance to give you a holistic view of your backups across multiple workloads and simplifying management of your data protection plans and stored data.

Basic overview of Google Cloud Backup and DR

Access Google Cloud Backup and DR using the management console

Backup and DR Service ensures that your data is managed, protected, and accessible using both hybrid and cloud-based backup/recovery appliances that are managed using the Backup and DR management console. Features of the management console include the following:

  • Holistic view of all your applications: See an aggregated view of backup/recovery appliance health and resource utilization through for all managed appliances.

  • Data backup and recovery: Discover and manage applications using the Onboarding wizard and perform backup and recovery processes.

  • Backup/recovery appliance management: Manage backup/recovery appliances, assign resources, create and assign roles to users, and create and manage storage pools.

  • Backup plan configuration: Configure backup plans to define how long to retain data.

  • Data mounting, cloning, or restoration: Access your captured and backed up data and perform mount, clone, LiveClone, restore, or replicate operations for backup images of your applications.

  • Backup/recovery appliance monitoring: Monitor backup/recovery appliance health and system performance in real-time.

  • Detailed reporting: View reports about jobs, backup plan compliance, resource utilization, and audit reports.

How Backup and DR Service works

The following workflow describes how Backup and DR Service creates and applies a backup plan to protect your data.

  1. Create and apply a backup plan. Use the Backup Plans tab in the management console to create data-handling policies that manage the following aspects of your data backups:

    • How often your application data is backed up by the backup/recovery appliance.

    • How long your application data backups are retained.

    • Where and how application data backups are replicated.

    To learn more about creating a backup plan for your data, see Backup plans.

    After you configure your backup plan, you must apply it to your application to enable the plan. See How to apply a backup plan.

  2. Restore your data when needed. After your application has a backup image according to your backup plan, you can restore the application from the image back to production at any time. To learn more about the restore function, see Restore overview.

  3. Access your backed up data. There are multiple methods for accessing your data in production or other storage formats. For quality assurance, migration to new storage, and more use cases, see Data access.

Quickstart guides

The following quickstart guides can help you begin a backup and recovery workflow for your application:

What's next

Depending on whether you've already deployed Backup and DR Service, go to the next page: