"title"=>"Google Cloud Backup and DR upgrade: VM protection made easier",
"summary"=>"
We're excited to announce a major enhancement to Google Cloud Backup and DR, making it simpler than ever to safeguard your critical Google Compute Engine virtual machines (VMs). You can now leverage the power of Google Cloud tags, including inheritance, to easily configure backup policies for Compute Engine VMs, ensuring consistent protection of your dynamic cloud environments.
\nThe challenge of managing VM backups
\nManaging backups for a large number of Compute Engine VMs can be complex, especially when VMs are frequently added, removed, or modified. Manually assigning backup policies to individual VMs is time-consuming and can be error-prone, potentially leaving vital resources unprotected.
\nThe power of tag-based backups
\nWith our new tag-based backup approach, you can leverage the organizational power of tags to automate the protection of your Compute Engine VMs. Here's how it works:
\n- \n
- \n
Assign your tags: Apply meaningful tags to your organization, folders, projects, or directly to your VMs. These tags might reflect application names, environments (production, development, testing), or criticality levels.
\n \n - \n
Create tag-based policies: Within Google Backup and DR, you can create backup policies with your desired backup schedules, retention periods, and recovery regions. After policy creation, you can assign them to specific tags.
\n \n - \n
Automate protection: Any VM with a matching tag is automatically assigned the backup policy. New VMs inheriting those tags immediately gain protection.
\n \n
Benefits of tag-based backups
\n- \n
- \n
Simplified management: Drastically reduce the administrative overhead of configuring VM backups at scale by updating the policy attached to the tag rather than at an individual VM backup level.
\n \n - \n
Consistent protection: Ensure new VMs with inherited tags from the project, folder, or organization are automatically protected without manual intervention.
\n \n - \n
Flexibility: Adjust your backup strategies easily by modifying tags or creating new tag-based policies, including support for tags assigned using Terraform
\n \n
For example, you can easily tag all production projects with the tag backupdr-dynamicprotect:production. You could then create a backup policy that does the following:
\n- \n
- \n
Takes daily snapshots of VMs in those projects that inherit the backupdr-dynamicprotect:production tag
\n \n - \n
Retains backups for 30 days
\n \n - \n
Updates your Terraform script to include your new protection tag to ensure protection of every new Compute Engine instance that’s created
\n \n
Getting started
\n- \n
- \n
Review the Google Backup and DR documentation on tag-based backups.
\n \n - \n
Develop a tagging strategy for your Compute Engine VMs.
\n \n - \n
Create backup policies that target your chosen tags.
\n \n - \n
Attend ARC205, Protect your critical workloads and recover your most critical asset - your data at Google Cloud Next.
\n \n
"content"=>nil,
"author"=>"Ashika Ganesh",
"link"=>"https://cloud.google.com/blog/products/storage-data-transfer/tags-support-in-backup-and-dr-service-simplifies-vm-protection/",
"published_date"=>Mon, 01 Apr 2024 16:00:00.000000000 UTC +00:00,
"image_url"=>nil,
"feed_url"=>"https://cloud.google.com/blog/products/storage-data-transfer/tags-support-in-backup-and-dr-service-simplifies-vm-protection/",
"language"=>nil,
"active"=>true,
"ricc_source"=>"feedjira::v1",
"created_at"=>Wed, 03 Apr 2024 14:31:15.737876000 UTC +00:00,
"updated_at"=>Tue, 14 May 2024 04:40:19.299110000 UTC +00:00,
"newspaper"=>"Google Cloud Blog",
"macro_region"=>"Technology"}