Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/compute/docs/disks/data-protection below:

Data protection options | Compute Engine Documentation

Stay organized with collections Save and categorize content based on your preferences.

This document compares the options available on Compute Engine to back up and replicate the following Compute Engine resources:

• Persistent Disk and Google Cloud Hyperdisk volumes
• Virtual machine (VM) and bare metal instances
• Workloads running in Compute Engine and on-premises

To safeguard important data, Google recommends using one of the backup options discussed in this document. You can't recover a compute instance, disk, image, or snapshot if you delete it, even if the deletion was accidental.

Managed backup and disaster recovery (DR) service providing secure storage and centralized backup management at scale for compute instances and other workloads running in Google Cloud.

• Improve cyber resilience with immutable and indelible backups to backup vaults.
• Configure the frequency, storage locations, and retention periods of the backed up resources.
• Empower app developers to protect instances while retaining governance and oversight.
• Comprehensive monitoring, auditing & reporting for compliance.
• Defend against ransomware and other risks through insights into security threat events.

• Captures the state of your disk at a particular point in time.
• Stored as differential copies for better performance and space efficiency.

• Offers all the same benefits as standard snapshots, but at a lower-cost.
• Suited for use cases related to compliance, audit, and long-term cold storage.

• Captures the state of your disk at a particular point in time.
• Each instant snapshot is stored as a differential copy of the disk for more efficient storage and better performance.

• Rapid data restoration after application corruption, user error, or failed upgrades.
• Low RTO and RPO.

• Long term instance backup and restore.
• Instance cloning and replication.

• High availability.
• Not designed for data backup.

• Creates a live duplicate of the source disk that can be instantly attached to an instance.

• Quickly bringing up staging environments from production.
• Replication for backup verification or export offloading.
• Not designed for disaster recovery.

• Instance import and fast disk creation.
• Quickly creating many instances.

Observe the following best practices when creating backups for your disks.

To immediately create a copy of a disk in the same zone for verification or export, use disk clones or instant snapshots instead of standard snapshots. Compared to disk clones and instant snapshots, standard snapshots have longer copy times for upload and download.

Schedule hourly standard snapshots. If you require daily snapshots, consider scheduling snapshots every 6 hours.

To create many disks from a single data source, use images instead of snapshots. Because Compute Engine performs local caching in target zones, disk creation from images is faster than disk creation from snapshots.

To create backups of all disks that are attached to an instance, use machine images. A machine image can be used to backup multiple disks at a time to help ensure that the data captured in the machine image is consistent across all disks. A persistent disk snapshot can only backup a single disk at a time. For more information, see When to use machine images.

With Backup and DR Service, you manage backups of your instances across projects and environments by using advanced policies, centralized monitoring and backup reporting in the following way:

• Create backup vaults that serve as secure storage locations for your backups.
• Create backup plans to configure the schedule and rules for your backup.
• Apply backup plans to existing instances or during instance creation.
• Assign specific permissions for backup access.
• Proactively and reactively monitor backup jobs.
• Create reports for tracking backups across resources spanning multiple projects.
• When needed, restore an instance from a backup vault.

You can also integrate Security Command Center Premium tier with Backup and DR Service to additionally:

• Track audit logs for backup access.
• Monitor for malicious activity on your backups.

• Read Best practices for persistent disk snapshots.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-05-06 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-06 UTC."],[[["Compute Engine offers multiple backup and replication options for Persistent Disk, Hyperdisk volumes, VM instances, and workloads, including on-premises."],["Google recommends using one of the backup solutions discussed, as deleted compute instances, disks, images, or snapshots are unrecoverable, even if accidentally deleted."],["Backup and DR Service is a managed option for secure storage and centralized backup management across multiple projects, providing features like backup vaults, backup plans, and security threat event insights."],["Standard, Archive, and Instant snapshots offer varying levels of cost and access speed for long-term data backup, ranging from geo-redundant storage to rapid data restoration."],["Machine images offer a method to back up and replicate all the disks attached to an instance with consistency across the disks, whereas persistent disk snapshots can only back up a single disk at a time."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3