How to Create a Virtual Standby to Hyper-V

Create a Virtual Standby task so that the backup data is converted to a virtual machine format and a virtual machine is created. The Virtual Standby feature also monitors the heartbeat of the source node so that when the source node is down, the virtual machine immediately takes over as the source node.

Notes:

• Virtual Standby cannot automatically power on recovery point snapshots taken from host-based agentless virtual machines.
• If you pause the plan, the Virtual Standby job will not start. When you resume the plan again, the Virtual Standby job is not resumed 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 you have to 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 one source for the Virtual Standby task.
4. Click the Virtualization Server tab and enter the virtualization server and monitoring server details.

HyperV Host Name

Specify the host name of the Hyper-V system.

User Name

Specify the user name that is required to log in to the Hyper-V system.

Note: The account that you specify must be an administrative account or an account with administrative privileges on the Hyper-V system.

Password

Specify the password for the User Name that is required to log in to the Hyper-V system.

Protocol

Specify HTTP or HTTPS as the protocol that you want to use for communication between the Arcserve UDP server and the Hyper-V Server system (monitoring server).

Port

Specify the port that you want to use for data transfer between the Arcserve UDP server and the Hyper-V Server system (monitoring server).

5. Note: To validate the Hyper-V system, click Connect.
5. Click the Virtual Machine tab and enter the details for the VM Basic Settings, VM path for Hyper-V, and VM Network.

Apply the following Virtual Machine options:

Basic Settings

Complete the following Basic settings:

VM Name Prefix

Specify the prefix that you want to add to the display name for the virtual machine on the Hyper-V system.

Default value: UDPVM_

CPU Count

Specify the minimum and maximum CPU count supported by the standby virtual system.

Memory

Specify the total amount of RAM in MB to be allocated to the standby virtual machine.

Note: The amount of RAM specified must be a multiple of four.

Recovery Point Snapshots

Specify the number of recovery point snapshots for the standby virtual machine. The maximum number of recovery point snapshots is 24 for Hyper-V virtualization servers.

All virtual disks share the same path

Select this option to specify the location on the Hyper-V server where you want to store the conversion data.

Clear the check box to specify the location on the Hyper-V server where you want to store the conversion data for each virtual disk.

Note: The Arcserve UDP solution does not support creating virtual disk images (VHD/VHDX files) on compressed volumes and volumes that are encrypted by the file system. If the path specified resides on compressed or encrypted Hyper-V volumes, Arcserve UDP prevents you from creating the Virtual Standby task.

VM Network

Lets you define the NICs, virtual networks, and paths that the Hyper-V server uses to communicate with the virtual machines. Specify one of the following options and complete the required fields.

Same number of network adapters as source at last backup

Select this option to define how to map the virtual NIC to the virtual network. Specify this option when the virtual machine contains virtual NICs and a virtual network.

Clear the check box to define the name of the virtual network that you want the NIC to use to communicate.

6. Click the Advanced tab and provide the following details:

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.

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.

• 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.
7. Click Save.
8. The changes are saved and the Virtual Standby task is automatically deployed to the Virtual Standby server.

You have successfully created and deployed the Virtual Standby plan.