Prerequisites for GCP
Perform the following prerequisites before disaster recovery.
All resources and settings that were enabled in the primary deployment must also be enabled in the secondary deployment. For example, if the primary deployment used Dedicated Compute with Load Balancer, then the secondary must also be configured the same way.
Ensure the secondary deployment uses the same region (DrRegion) as the primary deployment.
Both the primary and replica instances must be in the same VPC.
Your VPC must have at least two subnets:
One in the primary region.
One in the secondary (replica) region.
Ensure your Private Service Connect IP range has enough available IP addresses to accommodate both Cloud SQL instances.
Promote the read replica once you want to run DR.
In case of automated deployment, a primary Kyvos deployment is created when the enableDr (in the kyvosparams.tfvars file) parameter is set to true.
In case of wizard-based deployments, set up cross-region replication for Secret manager, CloudSQL, and Cloud Storage bucket.
To replicate key resources across regions in Google Cloud Platform (GCP), perform the following steps.
Cloud SQL – Cross-Region Replication: To replicate a Cloud SQL instance to another region:
Go to the Cloud SQL section in the GCP Console.
Locate the instance you want to replicate.
Click the three-dot menu (︙) on the right-hand side.
Select Create read replica.
Choose a different region for the replica.
Cloud Storage (Buckets) – Manual Replication: GCP buckets do not automatically replicate across regions. To replicate a bucket:
Create a new bucket in your secondary region.
Manually copy the contents of your primary bucket to the secondary bucket.
Secret Manager – Manual Replication: Secret Manager does not natively support multi-region replication.
To replicate secrets:In your secondary region, create a new Secret Manager.
Manually copy each version of the secrets from the primary deployment.