Hi Veeam Community,

I have seen many questions (and experienced a few issues myself) when deploying Veeam Backup for Google Cloud (VBGC) in production environments. Most of these could have been avoided with some pre-deployment checks. So, I wanted to share a quick checklist that might help others save time and frustration.

1️: Service Account Preparation

• Create a dedicated Service Account (SA) in GCP.

• Assign all required IAM roles/permissions for each project you plan to back up.

• Test SA access via the VBGC diagnostics tab — all checks should show "Passed" before deployment.

2️: Quota Review

• Check CPU, disk, and instance quotas for each region where VBGC will deploy worker instances.

• Adjust quotas in advance if you plan to use higher-spec worker profiles (e.g., upgrading from e2-highcpu-8 to n2-highmem-16).

3️: Network & Access

• Ensure VBGC and worker instances can access the internet when needed (especially during updates and temporary VM deployment).

• If using private networking, pre-configure firewall rules for VBGC communication.

4️: Worker Profiles

• Keep default profiles as fallback (Primary, Secondary, Archiving) but consider adding custom profiles for specific workloads.

• Verify storage repository connectivity for each profile.

5️: Backup Policy Planning

• Define backup types (snapshot, image-level, file-level) based on workload and RPO/RTO needs.

• Schedule backups during low-traffic hours to avoid performance impact.

• Enable daily backup reports to stay proactive on failures.

6️: Testing Before Production

• Run a test backup and restore (VM, database, file-level) before going live.

• Validate that restored data is accessible and consistent.

Most deployment failures I’ve seen were due to missing permissions, quota issues, or network restrictions. Addressing these before going live will make your VBGC deployment much smoother.