#1 Global Leader in Data Protection & Ransomware Recovery

How to Configure Connections Required for Veeam Backup for Google Cloud in Highly Secured Environments

KB ID: 4157
Product: Veeam Backup for Google Cloud | 1.0 | 2.0 | 3.0 | 4.0 | 5.0
Published: 2021-05-11
Last Modified: 2022-06-17
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

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 Backup for Google Cloud function properly:

  1. Allow internet access to the following Google Cloud APIs:

    To learn how to configure Private Google Access, see this Google Cloud KB article.
     
  2. 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 the Cloud DNS server. To do that, create firewall rules to connect to the address 169.254.169.254 (metadata.google.internal) through the ports TCP 80 and UDP 53, 123
  3. Allow 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 Endpoint Protocol Port
    security.ubuntu.com TCP 80

  4. Allow 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 Endpoint Protocol Port
    packages.microsoft.com TCP 443

  5. Allow access to the SMTP server that sends email notifications for Veeam Backup for 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 Endpoint Protocol Port
    <FQDN of your SMTP server> TCP 587

  6. Allow access to the Veeam Update Notification Server that provides security updates for Veeam Backup for 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 Endpoint Protocol Port
    repository.veeam.com TCP 443

    For all CLOUDFRONT service IP ranges, see this .JSON file.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.