Add a Virtual Standby to Google Cloud Task to the Plan

Create a Virtual Standby to Google Cloud task so that the backup data is converted to a virtual machine format and a virtual machine is created.

Notes:

• Virtual Standby to Google Cloud does not support automatic start of the Standby VM.
• Even if you enable the email alert for the automatic power on of VM for source machine configured with auto power ON, no alerts will be sent.
• If you pause the plan, the Virtual Standby job will not start. When you resume the plan again, the Virtual Standby job does not resume automatically. You have to manually run another backup job to start the Virtual Standby job. Also, if the plan is paused the Pause/Resume Virtual Standby option will not be available. If you do not want the virtual machine to start automatically after the plan is paused, then manually pause the heartbeat for the nodes.

Follow these steps:.

1. Click Add a Task from the left pane.
2. A new task is added to the left pane.
2. From the Task Type drop-down menu, select Virtual Standby.
3. The Virtual Standby task is added.
3. From the Source tab select a source for the Virtual Standby task.
4. Click the Virtualization Server tab.
5. Select Google Cloud as the virtualization type and enter details.

Virtualization Type - Google Cloud

Virtualization Type

Specify Google Type as the virtualization type.

Account Name

Select the existing Google Cloud account to access Google Cloud. You can also add a new account by clicking Add. For more information, see Add a Cloud Account for Google Cloud.

Compute Regions

Select the Google Cloud region where your cloud proxy is located. Arcserve UDP supports all Google Cloud global regions.

Compute Zones

Select the Google Cloud compute zone where your cloud proxy is located. Arcserve UDP supports all Google Cloud compute zones.

VSB Cloud Proxy

Specify one Google Cloud instance in the selected region as the cloud proxy.

Note: The Google Cloud instance must have Arcserve UDP agent installed.

Username and Password

Specify the credential to login at the VSB cloud proxy.

Protocol

Specify HTTP or HTTPS as the protocol that you want to use for communication between the source Arcserve UDP agent on VSB cloud proxy.

Port

Specify the port that you want to use for data transfer between the source server and the VSB cloud proxy.

Note: As the cloud proxy is used for data transfer, the related ports must be enabled to access inbound in Google VPC firewall security group, including TCP 8014 and 4091.

6. Click the Virtual Machine tab and enter the details for Basic setting, Cloud Storage setting and Networks setting.
7. Apply the following Virtual Machine options to Google Cloud:

VM Name Prefix

Specify the prefix that you want to add to the display name for the virtual machine on the Google Cloud.

Default value: udpvm-

Recovery Point Snapshots

Specify the number of recovery point snapshots (recovery points) for the Virtual Standby machine.

Combine all unconverted sessions into a single recovery point snapshot

Specify whether to combine all unconverted sessions into a single recovery point snapshot when next scheduled VSB job takes place.

Default: Selected

Instance Type

Google Cloud provides a wide selection of instance types optimized to suit different use cases. Instances are virtual servers that can run applications. They have varying combinations of CPU, memory, storage, and networking capacity, and provide the flexibility to choose the appropriate mix of resources for your applications. For more information about instance types and how they meet your computing needs, see link for more information.

Storage Setting

Compute Engine offers several disk based storage options for your VMs, see link for more information.

Network Setting

Lets you define the VPC, subnets, the NICs and firewall for the Virtual Standby virtual machine on Google Cloud.

Note: When the Enable auto assign public IP check box is enabled, due to the limitation of Google Cloud, only one NIC is mapped to Google Cloud and others are discarded.

7. Click the Virtual Machine tab and enter the details for Basic setting, Cloud Storage setting and Networks setting.
8. Click the Advanced tab and provide the following details:

Add data transfer to Cloud Throttling schedule

See Add Data Transfer to Cloud Throttling Schedule for more information.

Automatically start the Virtual Machine

Specify if you want to start the virtual machine automatically.

Note: This option is unavailable for host-based virtual machine nodes and nodes replicated from a remote recovery point server and the Source of the Virtual Standby task is the one replicated to a different Site. The Virtual Standby Source is the replicate task and the replication target RPS server inside Google Cloud.

Timeout

Specify the time that the monitor server must wait for a heartbeat before it powers on a recovery point snapshot.

Frequency

Specify the frequency that the source server communicates heartbeats to the monitor server.

Example: The Timeout value specified is 60. The Frequency value specified is 10. The source server will communicate heartbeats in 10-second intervals. If the monitoring server does not detect a heartbeat within 60 seconds of the last heartbeat that was detected, the monitor server powers on a virtual machine using the latest recovery point snapshot.

Enable Email Alerts

Lets you receive email alerts depending on the settings that you provide. When you select this option, further categories of email alerts are enabled for your selection.

• Configure Email- Lets you configure the email settings. Click Configure Email and configure the email server and proxy server details. For more information about how to configure the email settings, see Configure Email and Alerts.
• Missing heartbeat for source machine- Virtual Standby sends alert notifications when the monitor server does not detect a heartbeat from the source server.

Note: For nodes from Replicate from a remote Recovery Point Server or if the source of the Virtual Standby task is the one that is replicated to a different site, this option is not available.

• VM powered on for source machine configured with auto power ON- Virtual Standby sends alert notifications when it powers on a virtual machine that was configured to power on automatically when a heartbeat is not detected.

Note: For nodes from Replicate from a remote Recovery Point Server or if the source of the Virtual Standby task is the one that is replicated to a different site, this option is not available. This option is unavailable for host-based virtual machine nodes also.

• VM powered on for source machine configured with manual power ON- Virtual Standby sends alert notifications when it manually powers on a virtual machine.
• Virtual Standby errors/failure/crash- Virtual Standby sends alert notifications when it detects an error that occurred during the conversion process.
• Virtual Standby success- Virtual Standby sends alert notifications when it detects that a virtual machine powered on successfully.
• The Virtual Standby did not start successfully from the Recovery Point Snapshot- Virtual Standby sends alert notifications when it detects that a virtual machine was not powered automatically and the Automatically start the Virtual Machine Stand-in Recovery option is specified.
• Hypervisor is not reachable- Virtual Standby sends alert notifications when it detects that it cannot communicate with the ESX Server system or the Hyper-V system.
• VM storage free space less than- Virtual Standby sends alert notifications when it detects insufficient free disk space on the defined hypervisor path. The detection occurs when the amount of free disk space is less than the user-defined threshold. The threshold can be defined either an absolute value (MB) or as a percentage of the capacity of the volume.
9. Click Save.
10. The changes are saved and the Virtual Standby task is automatically deployed to the Virtual Standby server.