Veeam Backup for Google Cloud Recovery/Migration Procedure

KB ID: 4068
Product: Veeam Backup for Google Cloud | 1.0 | 2.0 | 3.0
Published: 2020-11-26
Last Modified: 2022-08-16
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.

Challenge

This article explains how to recover Veeam Backup for Google Cloud data in case the backup appliance gets corrupted and requires the data to be moved to a new instance (as the data contains important information about restore points, repositories, policies and so on).

Solution

Recommended Method

Starting with Veeam Backup for Google Cloud 3.0,  Configuration Backup and Restore is available and is now the simplest way to restore/migrate.

Legacy Methods

Before Veeam Backup for Google Cloud 3.0, which added the feature Configuration Backup and Restore, the methods described below were the only migration methods. The methods below are retained on this KB as legacy methods for migration and are still useful for migrating the Veeam Backup for Google Cloud instance between regions.

 

Original deployment still exists
  1. Deploy a new Veeam Backup for Google Cloud instance from Google Cloud Marketplace — in the same region and zone as the old instance.
  2. Stop the old instance.
  3. Go to the VM instance details of your old Veeam Backup for Google Cloud deployment and click the Edit button. Save the service account used to run the old instance.

    Then, detach the additional disk named OLD_DEPLOYMENT_NAME-data-disk.

  4. Go to the VM instance details of your new Veeam Backup for Google Cloud deployment and click the Edit button. Select the saved account from the Service Account drop-down list.

    Then, detach the additional disk named NEW_DEPLOYMENT_NAME-data-disk.

  5. Attach the additional disk named OLD_DEPLOYMENT_NAME-data-disk to the new Veeam Backup for Google Cloud instance, and save the changes.
  6. Start the new instance.
Original deployment does not exist anymore or is corrupted
  1. Deploy a new Veeam Backup for Google Cloud instance from Google Cloud Marketplace.
  2. In the Google Cloud Console, select the project where Veeam Backup for Google Cloud was originally deployed.

    Then, navigate to Disks and create a new SSD persistent disk using the source snapshot named OLD_DEPLOYMENT_NAME-data-region-timestamp in the region where the new Veeam Backup for Google Cloud instance is deployed. Set the size of the disk to 20 GB or more.

  3. Go to the VM instance details of your new Veeam Backup for Google Cloud deployment and click the Edit button. Then, detach the additional disk named NEW_DEPLOYMENT_NAME-data-disk.
  4. Attach the SSD persistent disk created at step 2 to the new Veeam Backup for Google Cloud instance, and save the changes.
  5. Start the new instance.
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.

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.