Review the Prerequisites and Considerations for Ad-hoc VSB to GCP

Verify that you have completed the following prerequisite tasks:

Important! Verify if you have created a Virtual Standby (VSB) proxy on the Google Cloud. For more information about how to create a VSB proxy on Google Cloud, see Create a Virtual Standby to Google Cloud Policy.

• You have the server component and a Data Store is created if you want to store the backup data to recovery point servers.
• You have a valid recovery point to create a virtual standby machine. The recovery points can be from one of the following tasks:
• Agent-based Windows Backup
• Agentless VM Backup to RPS
• Copy from remotely-managed RPS
• Copy
• Install the system volume on the first disk. Verify that the system volume and boot volume of the source machine are on the same disk.
• Configure the VPC firewall setting on Google Cloud to open the related ports for inbound access, including TCP 8014 and TCP 4091.
• Verify if the Google Cloud account can access Google Cloud Platform. Cloud Console does not provide the account.
• Specific Google Cloud API permissions are required for Google Cloud Platform users to achieve control and interaction with Google Cloud for VSB to Google Cloud. For details, refer to Configure IAM Granular Permissions for Service Accounts with VSB to Google Cloud.

• Review the see Compatibility Matrix that provides the supported operating systems, databases, and browsers.

Considerations:

• The system and boot volume on the source in VSB to Google Cloud plan must be on the first disk due to Google Cloud limitation.
• The customization to TCP/IP setting cannot apply to the first network interface on Google Cloud instance due to Google Cloud limitation.
• The external IP address assignment is only available for the first network interface on Google Cloud instance.
• The customization to TCP/IP setting is only applicable to the scenario when Direct Access or VPN is configured between primary site and the Google Cloud network. Otherwise, the customization makes the Google Cloud instance inaccessible.
• You cannot modify Enable/Disable auto assign public IP property for the existing sources in the plan and the update only affects the new sources added into the plan.
• Note: As a best practice, we recommend excluding files from antivirus scanning to make sure the virtual standby works properly.