This is a summary of the key features and capabilities currently supported by Google Compute Engine Disaster Recovery by JetStream.

Protection

    • Cross-project protection and recovery of VMs.
    • Supported disk types:
      • Balanced Persistent Disk
      • Performance (SSD) Persistent Disk
      • Hyperdisk Balanced
      • Hyperdisk Extreme
      • Hyperdisk Balanced High Availability
    • Supports VM configured with zonal or regional disks.
    • Recovery Groups: Groups of VMs replicated and recovered at a single consistent point in time.
    • Independent VM protection.
    • Supports VM disks configured with CMEK encryption.
    • Supports VM instances configured with CMEK encryption.
    • Supports VMs configured with zonal or global DNS.

Replication and Configuration Change Monitoring

    • Continuous monitoring and reporting of replication status.
    • DR events and error reporting in UI and email notification through Google Cloud logging.
    • Continuous monitoring of VM configuration changes and automatically handle disk additional and removal from protected VM.

Recovery Runbook

    • Separate runbook for failover, test failover and failback recoveries.
    • Boot sequence and boot delay can be configured for Recovery Group VMs.
    • VM Network:
      • VPC network and sub-network mapping to the recovery region
      • Retain internal IP address of network interface
      • Assign static/ephemeral internal IP address to network interface
      • Assign static external IP address to network interface
      • Configure DNS servers and DNS suffix settings
    • VMs network tag management.
    • VM label management.
    • VM reservation assignment.

Recovery 

    • Test Failover:
      • Fully automated creation of test VMs from the current state of the protected VMs using consistent cloned disks.
      • Fully automated cleanup of test VMs after the completion of DR drills.
    • Failover:
      • Supports recovery from various partial and full site disaster scenarios.
      • Planned failover with ability to gracefully shutdown primary VMs before recovery to the secondary region.
    • Failback:
      • Fully automated failback of VMs back to the primary region and resumption of VM protection after failback.
      • Ability to precisely control when to switch over VMs from the recovery to primary region during failback.