issue

If your backup appliance is deployed in a highly secured environment with all outbound connections restricted, you must perform the following configuration steps to make Veeam Plug-Infor Google Cloudfunction properly:Allow internet access to the following Google Cloud APIs:Compute Engine APIIAM Service Account Credentials APIIdentity and Access Management (IAM) APICloud Resource Manager APICloud Billing APIPub/Sub APICloud Storage APICloud Key Management Service APICloud Logging APITo learn how to configure Private Google Access, seethis Google Cloud KB article.Allow access to the Google Cloud metadata server that stores backup appliance metadata, to the NTP server that provides accurate timing to the backup appliance, and to theCloud DNS server.To do that, create firewall rules to connect to the address169.254.169.254 (metadata.google.internal)through the ports TCP80and UDP53, 123Allow access to Ubuntu repositories that provide updates for the backup appliance. Ubuntu repositories are almost entirely defined by FQDNs that do not have static addresses behind them. That is why you can create the following firewall rules to receive the updates:Destination EndpointProtocolPortsecurity.ubuntu.comTCP80Allow access to the Microsoft update server that provides updates for Microsoft .NET Framework installed on the backup appliance. Update servers are almost entirely defined by FQDNs that do not have static addresses behind them. That is why you can create the following firewall rules to receive the updates:Destination EndpointProtocolPortpackages.microsoft.comTCP443Allow access to the SMTP server that sends email notifications for Veeam Plug-Infor Google Cloud. SMTP servers are almost entirely defined by FQDNs that do not have static addresses behind them. That is why you can create the following firewall rules to send the notifications:Destination EndpointProtocolPort<FQDN of your SMTP server>TCP587Allow access to the Veeam Update Notification Server that provides security updates for Veeam Plug-Infor Google Cloud. The server is almost entirely defined by the FQDN that does not have static addresses behind it. That is why you can create the following firewall rules to receive the updates:Destination EndpointProtocolPortrepository.veeam.comTCP443For all CLOUDFRONT service IP ranges, seethis .JSON file.If this KB article did not resolve your issue or you need further assistance with Veeam software, please create aVeeam Support Case.