Meta tags:
description= Backup, high-availability, and disaster recovery options for Compute Engine instances and disks. Learn how machine images, snapshots, and replication meet your RPO, RTO, and cost requirements;
Headings (most frequently used words):
for, and, disk, data, protection, options, instances, with, disaster, recovery, replication, disks, instance, testing, debugging, backups, images, snapshots, protect, against, outages, stay, organized, collections, save, categorize, content, based, on, your, preferences, what, next, default, back, up, settings, created, in, the, console, products, pricing, support, resources, engage, machine, backup, dr, service, clones, instant, os, standard, archive, zonal, synchronous, regional, asynchronous,
Text of the page (most frequently used words):
and (148), #create (129), for (126), vms (106), the (99), with (83), disk (82), about (72), #instance (68), troubleshoot (62), use (59), disks (55), manage (49), snapshots (42), data (42), view (39), server (39), backup (37), images (37), compute (36), using (36), configure (35), windows (34), recovery (33), from (33), instances (33), performance (33), mig (33), your (31), engine (31), machine (31), overview (31), cloud (30), google (29), disaster (28), reservation (27), set (27), you (26), replication (24), hyperdisk (24), that (23), image (23), sql (21), resources (20), custom (20), monitor (20), regional (19), configuration (19), network (19), availability (18), backups (18), instant (18), access (18), gpu (18), policies (17), workloads (17), workload (17), back (17), service (17), linux (17), groups (16), creation (16), reservations (16), best (15), protect (15), persistent (15), storage (15), options (15), ssh (15), recommendations (15), testing (14), high (14), standard (14), time (14), snapshot (14), new (14), attached (14), based (14), host (14), load (14), virtual (14), apply (14), connect (14), this (13), zonal (13), zones (13), multiple (13), management (13), bulk (13), microsoft (13), cluster (13), practices (12), default (12), can (12), stateful (12), archive (12), boot (12), minutes (12), protection (12), sole (12), see (11), more (11), application (11), region (11), option (11), choose (11), metadata (11), type (11), delete (11), asynchronous (10), scale (10), existing (10), across (10), migs (10), machines (10), migrate (10), add (10), logs (10), regions (9), failover (9), optimized (9), source (9), maintenance (9), licenses (9), managed (9), tenant (9), openshift (9), shutdown (9), start (9), hpc (9), are (8), license (8), console (8), learn (8), between (8), applications (8), copy (8), change (8), schedules (8), enable (8), import (8), cpu (8), resource (8), login (8), optimize (8), internal (8), install (8), agent (8), update (8), guest (8), keys (8), h4d (8), flexibility (8), dns (8), tpu (8), all (7), thumb (7), setting (7), synchronous (7), zone (7), location (7), operating (7), restore (7), clones (7), following (7), method (7), networking (7), commitments (7), startup (7), balancing (7), benchmark (7), manually (7), idle (7), addresses (7), request (7), deploy (7), mysql (7), remove (7), templates (7), events (6), system (6), support (6), send (6), against (6), rto (6), event (6), operations (6), capabilities (6), hours (6), long (6), types (6), uses (6), automatically (6), errors (6), project (6), projects (6), policy (6), plans (6), monitoring (6), usage (6), security (6), migration (6), updates (6), files (6), nested (6), gpus (6), group (6), mode (6), demand (6), pools (6), run (6), extension (6), transfer (6), customized (6), spot (6), code (5), samples (5), understand (5), details (5), created (5), outage (5), rpo (5), plan (5), perform (5), require (5), same (5), doesn (5), term (5), production (5), designed (5), creating (5), local (5), when (5), clone (5), cloning (5), work (5), environment (5), seconds (5), full (5), databases (5), accounts (5), future (5), drivers (5), virtualization (5), nvidia (5), placement (5), node (5), highly (5), available (5), build (5), multi (5), modify (5), capacity (5), audit (5), symphony (5), email (5), scripts (5), manager (5), systems (5), enhanced (5), stop (5), tenancy (5), control (5), workstation (5), faq (5), flex (5), português (4), español (4), other (4), down (4), two (4), different (4), low (4), outages (4), provide (4), infrastructure (4), user (4), recommend (4), cost (4), cases (4), configurations (4), not (4), stored (4), place (4), without (4), debugging (4), specific (4), consistent (4), one (4), deletion (4), automatic (4), tools (4), distributed (4), authentication (4), issues (4), ubuntu (4), bandwidth (4), tcp (4), pmu (4), number (4), ssd (4), get (4), share (4), upgrade (4), live (4), autoscaling (4), cross (4), requests (4), calendar (4), single (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), suspend (4), resize (4), graceful (4), locations (4), review (4), bound (4), terms (3), information (3), need (3), updated (3), content (3), apache (3), replicate (3), offers (3), critical (3), zero (3), balanced (3), such (3), failures (3), instead (3), target (3), including (3), software (3), once (3), template (3), deleted (3), upgrades (3), which (3), lets (3), duplicate (3), needs (3), efficiency (3), development (3), point (3), export (3), goal (3), how (3), only (3), enabled (3), api (3), predefined (3), accidental (3), services (3), advanced (3), strategies (3), requirements (3), volumes (3), solutions (3), guides (3), observability (3), analytics (3), troubleshooting (3), encryption (3), pro (3), serial (3), patterns (3), higher (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), list (3), ibm (3), spectrum (3), deploying (3), during (3), prepare (3), deployment (3), rhel (3), certificates (3), query (3), state (3), disable (3), properties (3), account (3), increase (3), schedule (3), lifecycle (3), design (3), size (3), non (3), pool (3), move (3), workstations (3), series (3), tpus (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), site (2), youtube (2), center (2), started (2), pricing (2), products (2), last (2), 2026 (2), utc (2), licensed (2), under (2), feedback (2), next (2), protects (2), complete (2), letting (2), ideal (2), must (2), affecting (2), failback (2), consistency (2), fails (2), any (2), synchronously (2), within (2), asynchronously (2), failure (2), another (2), malicious (2), attacks (2), scheduling (2), compliance (2), restored (2), faster (2), geo (2), redundant (2), retention (2), while (2), incremental (2), they (2), because (2), accelerate (2), process (2), identical (2), provision (2), fast (2), operational (2), quickly (2), helps (2), ready (2), isolated (2), replicates (2), rare (2), differential (2), copies (2), better (2), space (2), environments (2), table (2), summarizes (2), affect (2), selected (2), automated (2), settings (2), secure (2), define (2), comprehensive (2), scaling (2), improve (2), permissions (2), document (2), recover (2), test (2), deployments (2), objective (2), documentation (2), sdk (2), languages (2), frameworks (2), costs (2), industry (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), quota (2), commitment (2), consumption (2), registration (2), sles (2), port (2), collecting (2), nodes (2), report (2), arm (2), core (2), rdp (2), general (2), app (2), latency (2), analyze (2), visible (2), cores (2), committed (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), web (2), autohealing (2), iis (2), external (2), shared (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), provider (2), running (2), directory (2), redis (2), writer (2), always (2), alwayson (2), name (2), file (2), authenticate (2), synchronization (2), global (2), switch (2), byol (2), payg (2), byos (2), changes (2), families (2), guide (2), securing (2), simulate (2), topology (2), together (2), repairs (2), repair (2), check (2), suspended (2), stopped (2), distribution (2), physical (2), cancel (2), limit (2), interfaces (2), ipv6 (2), static (2), decrease (2), basic (2), scoped (2), appliances (2), throughput (2), encrypt (2), names (2), format (2), mount (2), memory (2), extreme (2), credentials (2), organization (2), through (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), apis (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, github, status, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, page, java, registered, trademark, oracle, its, affiliates, developers, creative, commons, attribution, read, what, secondary, recoverable, large, entire, ensure, effective, suited, very, continue, minimal, disruption, tolerate, loss, these, writes, simultaneously, either, business, maintaining, continuously, however, corruption, error, daily, consider, every, hourly, lower, rarely, accessed, required, audits, cold, might, than, archival, remote, specifically, both, durable, also, caching, bootable, installed, reusable, many, purposes, rapid, minimize, downtime, avoid, unlike, fully, functional, contains, creates, instantly, usable, independent, disturbing, standardized, rollback, failed, particular, saved, malware, scans, impacting, verification, offloading, staging, detailed, instructions, regardless, suit, means, preselected, should, have, protecting, transient, isn, backs, regular, basis, but, most, centralized, until, encourages, tab, features, mounting, directly, storing, vaults, immutability, indelibility, vmware, automation, their, crash, capture, auditing, reporting, retaining, governance, oversight, defend, ransomware, cyber, resilience, immutable, indelible, defined, stores, implement, discussed, keep, mind, even, was, permanent, unless, warning, debug, recommended, solution, each, implementing, variety, right, case, save, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, common, pay, viewing, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, resiliency, communication, reduce, compact, idpf, interface, irdma, driver, nic, customize, threads, per, sustained, merge, split, extend, renew, purchase, savings, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, https, consuming, consume, combine, cud, allow, sharing, decisions, signals, serving, predictions, organize, labels, replica, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, passive, inactive, setups, built, integrations, validation, were, deployed, transition, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, address, mailjet, mailgun, sendgrid, sending, blue, green, lamp, joomla, asp, net, interactive, mongodb, flask, terraform, servers, over, mtls, random, generator, virtio, rng, accurate, protocol, ntp, append, els, after, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, functionality, risks, command, vpc, controls, confidential, kek, expiration, shielded, attributes, handle, notices, faulty, unmanaged, preserved, turn, off, alternate, repairing, maintain, click, override, selectively, applying, out, rebalance, reenable, proactive, redistribution, shape, distribute, info, spread, edit, rename, reset, resume, restart, referrers, uuid, corrupted, alerts, vss, regionally, considerations, make, provisioned, iops, limits, evaluate, help, kms, customer, supplied, symbolic, links, practice, device, ram, attach, additional, exapools, verify, identity, ptr, record, rates, tags, restrict, automate, password, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, browser, connections, networks, iso, imported, prerequisites, importing, exporting, bring, own, path, detach, reattach, constraint, accounting, examples, slurm, reserved, team, slice, slices, adds, scenarios, deterministic, base, aci, configured, preempted, historical, alternative, similar, displays, ops, logging, subnet, public, has, gpudirect, ultra, specify, minimum, platform, hostname, quickstarts, iam, roles, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, free, skip, main,
Text of the page (random words):
s view and understand vm insights view and understand mig insights manage idle vm recommendations idle vm recommendations overview view and apply idle vm recommendations configure idle vm recommendations manage reservation recommendations reservation recommendations overview view and apply idle reservation recommendations view and apply underutilized reservation recommendations configure idle reservation recommendations configure underutilized reservation recommendations overcommit cpus on sole tenant vms manual live migration about manual live migration manually live migrate vms share sole tenant node groups next generation dynamic resource management cost savings get discounts for committed usage about commitments and committed use discounts cuds resource based cuds purchase resource based commitments without attached reservations with attached reservations for os licenses manage resource based commitments renew commitments automatically extend commitment terms merge and split commitments upgrade commitments share resource based cuds across projects get discounts for sustained usage disk performance optimize hyperdisk performance optimize persistent disk performance optimize local ssd performance workload performance set the number of threads per core customize the number of visible cpu cores analyze the cpu performance using the pmu pmu overview enable the pmu in vms manage the pmu in vms network performance network bandwidth use google virtual nic use irdma network driver use idpf network interface configure a vm with higher bandwidth reduce latency by using compact placement policies optimize tcp network communication optimize tcp network performance optimize tcp network resiliency benchmark higher bandwidth vms optimize app latency with load balancing use dpdk to improve network performance network performance and gpu vms networking and gpu machines use higher network bandwidth patterns for using multiple host nics troubleshoot general tips troubleshoot connectivity troubleshoot rdp troubleshoot ssh troubleshoot os login troubleshoot vms troubleshoot vm operations troubleshoot vm creation troubleshoot resource availability errors troubleshoot bulk api vm creation troubleshoot vm reboots and shutdowns troubleshoot vm suspension troubleshoot vm updates troubleshoot unresponsive vms troubleshoot vm startup troubleshoot fstab errors troubleshoot kernel panic collecting core dumps rescue an inaccessible vm troubleshoot cpu bus locks troubleshoot cpu soft lockups troubleshoot vm configurations troubleshoot arm vms troubleshoot gpu vms troubleshoot nvidia gpu errors generate a nvidia bug report for blackwell gpus troubleshoot nested virtualization troubleshoot using vm screenshots troubleshoot sole tenant nodes troubleshoot vm performance issues troubleshoot sudoers files troubleshoot windows vms troubleshoot windows vms collecting diagnostic information troubleshoot using the serial console troubleshoot using the serial console viewing serial port output troubleshoot instance groups troubleshoot managed instance groups migs troubleshoot os management troubleshoot licenses troubleshoot image import and export troubleshooting sles pay as you go registration troubleshooting ubuntu pro registration troubleshoot metadata server troubleshoot metadata server troubleshoot networking issues troubleshoot common networking issues troubleshoot network drivers troubleshoot vm performance issues troubleshoot storage troubleshoot disk creation troubleshoot full disks and disk resizing troubleshoot disk encryption troubleshoot nvme disks troubleshoot instant snapshots troubleshoot standard snapshots troubleshoot reservations and commitments troubleshoot reservation creation troubleshoot reservation consumption troubleshooting reservation monitoring troubleshoot reservation updates troubleshoot future reservation creation and updates troubleshoot automatic commitment renewal troubleshoot quota errors troubleshoot concurrent operation quota errors troubleshoot workload authentication troubleshoot default service accounts troubleshoot workload to workload authentication ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation compute compute engine guides send feedback data protection options for disks and instances stay organized with collections save and categorize content based on your preferences this document helps you choose the right option to protect your compute engine resources based on your recovery time objective rto recovery point objective rpo use case and cost requirements compute engine offers a variety of options to protect the following resources compute engine instances persistent disk google cloud hyperdisk each data protection option is designed for specific use cases and recovery needs to protect your critical data we recommend implementing one of the following backup or replication solutions goal recommended solution test debug or manage deployments for disks use instant snapshots disk clones or custom os images for instances use machine images back up for disaster recovery for disks use standard or archive snapshots for instances use machine images or backup and dr service high availability for disaster recovery for disks use synchronous or asynchronous replication warning to protect your data you must implement one of the strategies discussed in this document keep the following in mind no automatic backups compute engine doesn t automatically back up your resources such as instances and disks unless you configure a backup or replication option permanent deletion you can t recover a deleted instance disk image or snapshot even if the deletion was accidental data protection options for instances the following table summarizes data protection options for instances data protection options for instances goal option rpo rto use cases testing or disaster recovery machine images minutes to hours minutes to hours stores an instance s configuration metadata permissions and data from all attached disks long term instance backup and restore instance cloning and replication disaster recovery backup and dr service policy defined minutes to hours defend against ransomware and improve cyber resilience with immutable and indelible backups protect instances while retaining governance and oversight comprehensive monitoring auditing and reporting for compliance instance testing and debugging to clone an instance for testing or debugging scaling instances or system maintenance use machine images machine images machine images are ideal for cloning instances because they capture a comprehensive point in time copy of your source instance letting you clone your production environment without affecting it when you create a new instance from a machine image the new instance is a clone of the source instance including the full instance configuration and a crash consistent copy of the data from all attached persistent disk and hyperdisk volumes to back up only your instance s disks and not the full instance configuration use standard or archive snapshots to learn more about machine images see about machine images instance backups for disaster recovery to back up instances and their attached disks for disaster recovery use machine images or backup and dr service backup and dr service backup and dr service lets you create backup plans that define automated backup schedules data retention policies and replication strategies we recommend backup and dr service for workloads with the following requirements manage backups across multiple projects advanced policy based automation support for google cloud services including compute engine vms and vmware engine vms protection from accidental deletion or malicious attacks by storing backups in secure isolated backup vaults that support immutability and indelibility cost efficiency with incremental backups low rto with features that enable instant mounting and in place access to data directly from backups to learn more about backup and dr service see about backup and dr service back up plans default back up settings for instances created in the console when you create a new instance using the google cloud console compute engine uses a predefined default backup method until you change it this encourages consistent use of automated backups across your project one of the following options is automatically selected in the data protection tab backup plan we recommend this option for most projects as it offers centralized policy based backups if the backup and dr api is enabled for your project this option is your predefined default backup method snapshot schedules this option is selected if the backup and dr service isn t enabled snapshot schedules automatically backs up the disks attached to your instance on a regular basis but it doesn t back up the full instance configuration no backups this option means no backup method is preselected you should only choose this if you have another method for protecting your data or if the data is transient and doesn t require backups regardless of the default backup setting you can choose a different backup method when you create the instance to best suit the needs of a specific workload this setting doesn t affect existing instances for detailed instructions on how to view or change your project s default backup setting see configure the default backup setting for the console data protection options for disks the following table summarizes data protection options for disks data protection options for disks goal option rpo rto use cases testing disk clones zero seconds to minutes quickly create staging environments from production copy a disk for backup verification or export offloading perform malware scans without impacting source disk performance testing instant snapshots seconds to minutes seconds to minutes create a backup of a disk s data at a particular point in time that s saved in the same location as the source disk fast rollback for user errors or failed software upgrades stored as differential copies for better performance and space efficiency testing os images n a n a create multiple instances with identical boot disks create standardized development and testing environments disaster recovery standard and archive snapshots minutes to hours minutes to hours geo redundant disk backups for disaster recovery stored as differential copies for better performance and space efficiency disaster recovery synchronous replication zero seconds to minutes replicates data synchronously across two zones in the same region to provide high availability in the rare event of a zonal outage not designed for data backup disaster recovery asynchronous replication seconds to minutes minutes replicates data asynchronously across two regions to provide high availability in the rare event of a regional outage not designed for data backup disk testing and debugging you can use clones instant snapshots or custom os images to back up a disk for testing and debugging disk clones to create a ready to use copy of a disk use a disk clone instead of creating a snapshot disk cloning creates an instantly usable independent duplicate of a disk which lets you work with production data in an isolated environment without disturbing your production workloads unlike a snapshot which is a backup that needs to be restored to a new disk a clone is a new fully functional disk that contains all the data from the source disk at the time of creation to learn more about disk clones see duplicate a disk with clones instant snapshots to quickly back up a disk for operational purposes such software upgrades or system testing use an instant snapshot instant snapshots are in place backups stored in the same zone or region as the source disk which lets you restore data to a new disk in minutes this rapid recovery helps minimize downtime and avoid long maintenance windows instant snapshots are designed for fast operational recovery not disaster recovery instant snapshots are stored in the same location as the source disk and are automatically deleted when the source disk is deleted for long term storage or disaster recovery use standard or archive snapshots instead of instant snapshots to learn more about instant snapshots see about instant snapshots os images to create multiple new instances with identical boot disks or to create disks at scale use a custom operating system os image you can create a custom os image from an existing boot disk an os image is a complete bootable copy of your disk including the operating system custom configurations and any installed software once created you can use the os image as a reusable template to provision new boot disks for many vms to create disks at scale use os images instead of creating multiple disks from a snapshot os images are faster because compute engine uses local caching in the target zones to accelerate the creation process to learn more about custom images see about os images disk backups for disaster recovery you can use standard and archive snapshots to back up a disk for disaster recovery you can also use synchronous and asynchronous replication to protect your applications from zonal or regional outages standard and archive snapshots to protect your data from regional or zonal failures or for long term archival use standard or archive snapshots standard and archive snapshots are remote geo redundant backups designed specifically for disaster recovery and long term data retention while both types provide durable incremental backups they re optimized for different use cases use standard snapshots to protect production data that might need to be restored with a faster recovery time than archive snapshots use archive snapshots as a lower cost storage option for data that s rarely accessed such as backups required for compliance audits or long term cold storage we recommend scheduling hourly standard snapshots if you require daily snapshots consider scheduling snapshots every 6 hours to learn more about standard and archive snapshots see about archive and standard disk snapshots disk replication for disaster recovery for business critical workloads that require high availability or disaster recovery capabilities use disk replication to protect your applications from zonal or regional outages replication protects against infrastructure failure by maintaining a continuously updated copy of your data in another location however replication doesn t protect against data corruption user error or malicious attacks you can replicate your disk data either synchronously within a region or asynchronously between regions protect against zonal outages with synchronous rep...
|
