You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a subscription to synchronise the data between a virtual machine and a GCP CloudSQL instance. Before we promote the CloudSQL instance to handle all the traffic, we want to establish bi-directional replication so the existing virtual machine instance can stay as a redundant backup or failover instance.
To set up the bi-directional replication, we need to set forward_origins to {} instead of the default {all}. I checked the existing documentation and found no method to update forward_origins for an existing subscription.
I would be thankful if you could point me out a workaround or method that can update the value for forward_origins in the case of an existing subscription.
Thanks,
Shreyas.
The text was updated successfully, but these errors were encountered:
I have created a subscription to synchronise the data between a virtual machine and a GCP CloudSQL instance. Before we promote the CloudSQL instance to handle all the traffic, we want to establish bi-directional replication so the existing virtual machine instance can stay as a redundant backup or failover instance.
To set up the bi-directional replication, we need to set
forward_origins
to{}
instead of the default{all}
. I checked the existing documentation and found no method to updateforward_origins
for an existing subscription.I would be thankful if you could point me out a workaround or method that can update the value for
forward_origins
in the case of an existing subscription.Thanks,
Shreyas.
The text was updated successfully, but these errors were encountered: