Redundent Disks with Google Cloud Virtual Machine

For this scenario, I will recommend other options for having always availability on your web service, as the issue is often the instance itself and not the disk regarding GCE running websites possible issues.

First thing to have in mind is to have a robust system, since a lot of us never take this in mind when using GCP compute engine (specially for web servers) as certain events are unpredictable, and it is best to be prepared for these events (region out of resources, ongoing known issues, VM failure).

I can tell that creating a Managed Instance Group will work for you as it will keep your service up in case of failure, it let you operate apps on multiple identical VMs. You can make your workloads scalable and highly available by taking advantage of automated MIG services, including: autoscaling, autohealing, regional (multiple zone) deployment, and automatic updating.

You can use managed instance group (MIG) for scenarios like these:

-Stateless serving workloads, such as a website frontend.

-Stateless batch, high-performance, or high-throughput compute workloads, such as image processing from a queue.

-Stateful applications, such as databases, legacy applications, and long-running batch computations with checkpointing.

A managed instance group creates each of its managed instances based on the instance template and optional stateful configuration that you specify.

Since you are searching for high availability on your web server, Instance groups keeps VM instances running. If a VM in the group stops, crashes, or is deleted by an action other than an instance group management command (for example, an intentional scale in), the instance group automatically recreates that VM in accordance with the original instance’s specification (same VM name, same template) so that the VM can resume its work.