# Standard vs regional provisioned disks, for ex. GCP

**URL:** <https://forums.percona.com/t/standard-vs-regional-provisioned-disks-for-ex-gcp/34571>\
**Category:** Percona Operator for MongoDB\
**Created:** [October 24, 2024, 7:57am UTC](https://forums.percona.com/t/standard-vs-regional-provisioned-disks-for-ex-gcp/34571 "2024-10-24T07:57:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamoser](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jamoser](https://forums.percona.com/u/jamoser)\
**Post date:** [October 24, 2024, 7:57am UTC](https://forums.percona.com/t/standard-vs-regional-provisioned-disks-for-ex-gcp/34571/1 "2024-10-24T07:57:48Z")

</div>

Hello

Standard → disk in one zone  
Regional → disk mirrored in 2 zones

What is your recommendation ? In case of Regional and I would want to specify Zone a and c, how would you configure this on your cr.yaml (in GCP, GKE) ?

Since the disks are created automatically I see some problems to define in what zones they should be created …

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [October 28, 2024, 8:46am UTC](https://forums.percona.com/t/standard-vs-regional-provisioned-disks-for-ex-gcp/34571/2 "2024-10-28T08:46:38Z")

</div>

Hey @jamoser.

Seems what you are trying to do is to replicate the data across multiple zones on the storage layer. There are various designs on how you can approach it.

1. Rely on MongoDB replication and affinity.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/0/a/0af90acd696902de6622317ff8db9d0453cbfd14.png)

1. Rely on regional storage replication, run just one MongoDB node

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/5/a/5a817f3d9e7f2ed215367de443257903b71e6c54.png)

1. Rely on regional storage replication, but also do MongoDB replication

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/d/3/d36b03263b36a04fe1fa44631834c3718f3a9250.png)

As for recommendations: go with (1).  
Option 2 is possible, but I don’t see any good reason for it. Storage level replication can be good, but only when you have full control over replication and disk flush. Without it, you may end up with inconsistent data. Also failover will be always longer.  
Option 3 - not sure why would anyone want and if it is even possible.

As for your question - can you set specific zones for Regional disks with operator - it is set on the storage class level. From their docs:

```auto
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: regionalpd-storageclass
provisioner: pd.csi.storage.gke.io
parameters:
  type: pd-balanced
  replication-type: regional-pd
volumeBindingMode: WaitForFirstConsumer
allowedTopologies:
- matchLabelExpressions:
  - key: topology.gke.io/zone
    values:
    - europe-west1-b
    - europe-west1-c

```

But again, pls read above.