VM Migration to Google Cloud NetApp Volumes NFS Datastore on Google Cloud VMware Engine using Veeam Replication feature
Customers who currently use Veeam for their data protection requirements continue using that solution to migrate the workloads to GCVE and enjoy the benefits of Google Cloud NetApp Volumes NFS Datastores.
Overview
Authors: Suresh Thoppay, NetApp
VM Workloads running on VMware vSphere can be migrated to Google Cloud VMware Engine (GCVE) utilizing Veeam Replication feature.
This document provides a step-by-step approach for setting up and performing VM migration that uses Google Cloud NetApp Volumes, Veeam, and the Google Cloud VMware Engine (GCVE).
Assumptions
This document assumes you have either Google Cloud VPN or Cloud Interconnect or other networking option in place to establish network connectivity from existing vSphere servers to Google Cloud VMware Engine.
There are multiple options for connecting on-premises datacenters to Google Cloud, which prevents us from outlining a specific workflow in this document. Refer to the Google Cloud documentation for the appropriate on-premises-to-Google connectivity method. |
Deploying the Migration Solution
Solution Deployment Overview
-
Make sure NFS datastore from Google Cloud NetApp Volumes is mounted on GCVE vCenter.
-
Ensure Veeam Backup Recovery is deployed on existing VMware vSphere environment
-
Create Replication Job to start replicating virtual machines to Google Cloud VMware Engine instance.
-
Perform Failover of Veeam Replication Job.
-
Perform Permanent Failover on Veeam.
Deployment Details
Make sure NFS datastore from Google Cloud NetApp Volumes is mounted on GCVE vCenter
Login to GCVE vCenter and ensure NFS datastore with sufficient space is available.
If not, Please refer Mount NetApp Volumes as NFS datastore on GCVE
Ensure Veeam Backup Recovery is deployed on existing VMware vSphere environment
Please refer Veeam Replication Components documentation to install required components.
Create Replication Job to start replicating virtual machines to Google Cloud VMware Engine instance.
Both on-premises vCenter and GCVE vCenter needs to be registered with Veeam. Setup vSphere VM Replication Job
Here is a video explaining how to
Configure Replication Job.
Replica VM can have different IP from the source VM and can also be connected to different port group. For more details, check the video above. |
Perform Failover of Veeam Replication Job
To Migrate VMs, perform Perform Failover
Perform Permanent Failover on Veeam.
To treat GCVE as your new source environment, perform Permanent Failover
Benefits of this solution
-
Existing Veeam backup infrastructure can be utilized for migration.
-
Veeam Replication allows changing VM IP addresses on target site.
-
Has ability to remap existing data replicated outside of Veeam (like replicated data from BlueXP)
-
Has ability to specify different network portgroup on target site.
-
Can specify the order of VMs to power on.
-
Utilizes VMware Change Block Tracking to minimize the amount of data to send across WAN.
-
Capability to execute pre and post scripts for replication.
-
Capability to execute pre and post scripts for snapshots.