Hi,
As a consultant I've been running restorations to GCE using both VBR OnPremise and on GCP and on multiple different VPC/Shared VPC network configurations.
Very recently I found out that my restore jobs were no longer working on a Hub and Spoke network configuration. Where Backup repo is on a dedicated isolated project, VBR either onprem or on a dedicated service project and spoke, restored workloads on various service projects on whatever spoke they belong to.
To find out what the issue were I've setup log level to its max value (6). Therefor I realized that VBR is now using the default Compute Engine service account to be attached to Cloud Build jobs ? First of all as a best practice we always delete the default service accounts in our projects. But anyway I does not make sense to me that suddenly VBR has decided to use GCE SA instead of CloudBuild SA to run cloud build operations ?
As a consultant I've been running restorations to GCE using both VBR OnPremise and on GCP and on multiple different VPC/Shared VPC network configurations.
Very recently I found out that my restore jobs were no longer working on a Hub and Spoke network configuration. Where Backup repo is on a dedicated isolated project, VBR either onprem or on a dedicated service project and spoke, restored workloads on various service projects on whatever spoke they belong to.
To find out what the issue were I've setup log level to its max value (6). Therefor I realized that VBR is now using the default Compute Engine service account to be attached to Cloud Build jobs ? First of all as a best practice we always delete the default service accounts in our projects. But anyway I does not make sense to me that suddenly VBR has decided to use GCE SA instead of CloudBuild SA to run cloud build operations ?
Statistics: Posted by paa__ — Jun 26, 2024 12:57 pm