Add a Virtual Standby Task to the Plan
Create a Virtual Standby to Azure 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 the recovery point snapshots that are taken from host-based virtual machine nodes, nodes replicated from a remote recovery point server, and the Source of the Virtual Standby task is the one replicated to a different Site. You have to manually power on recovery point snapshots for such nodes.
- When you pause the plan and resume again, the Virtual Standby job does not resume automatically. You must manually run another backup job to start the Virtual Standby job. Also, when you pause the plan, the Pause/Resume Virtual Standby option becomes unavailable. If you do not want the virtual machine to start automatically after you pause the plan, you must manually pause the heartbeat for the nodes.
Follow these steps:
- Click Add a Task from the left pane.
- A new task is added to the left pane.
- From the Task Type drop-down menu, select Virtual Standby.
- The Virtual Standby task is added.
- From the Source tab select one source for the Virtual Standby task.
- Click the Virtualization Server tab and enter the virtualization server and monitoring server details.
- You can use any physical computer or virtual machine as the monitor server .
- You cannot use the backup source server as the monitor server.
- Monitor server configuration is not required if the nodes are replicated from a remote recovery point server or the Source of the Virtual Standby task is the one replicated to a different Site.
- Monitor server configuration is not required if the Virtual Standby Source is the replicate task and the replication target RPS server is inside Azure.
- Click the Virtual Machine tab and enter the details for VM Basic Settings, VM DataStore for VMware, VM path for Hyper-V, and VM Network.
- Storage (general purpose v1)
- StorageV2 (general purpose v2)
- Click the Advanced tab and provide the following details:
- Number of threads uploading for each job: Default Value: 4
- Buffer size for each thread: Default Value: 4096 KB
- Missing heartbeat for source machine--Virtual Standby sends alert notifications when the monitor server does not detect a heartbeat from the source server.
- VM powered on for source machine configured with auto power ON--Virtual Standby sends alert notifications when a virtual machine that was configured to power on automatically when a heartbeat is not detected is powered on .
- VM powered on for source machine configured with manual power ON--Virtual Standby sends alert notifications when a virtual machine is manually powered on.
- Virtual Standby errors/failure/crash--Virtual Standby sends alert notifications if an error is detected during the conversion process.
- Virtual Standby success--Virtual Standby sends alert notifications when a virtual machine is powered on successfully.
- The Virtual Standby did not start successfully from the Recovery Point Snapshot--Virtual Standby sends alert notifications if the Automatically start the Virtual Machine Stand-in Recovery option is enabled, but a virtual machine is not powered on automatically.
- Click Save.
- The changes are saved and the Virtual Standby task is automatically deployed to the Virtual Standby server.
- Note: When the Virtual Standby task is complete, the virtual machine standby volume is created. The standby virtual machine is created only after the virtual machine is powered on from Arcserve UDP.
Virtualization Type
Specify Azure as the Virtualization Type.
Account Name
Select an existing Azure account or click Add to create an account.
For more information, see how to add a cloud account.
Resource Group
Select an existing resource group or click Add to create a resource group.
For more information, see Resource group in Azure.
Region
Select the region where you want the standby VM to operate in Azure. For more information, see Regions in Azure.
Monitor
Specify the host name of the server that monitors the status of the source server.
Notes:
User Name
Specify the user name to log into the monitoring system.
Password
Specify the password for the user name to log into the monitoring system.
Protocol
Specify HTTP or HTTPS as the protocol that you want to use for communication between the Arcserve UDP and the monitoring server.
Port
Specify the port that you want to use for data transfer between Arcserve UDP and monitoring server.
VM Name Prefix
Specify a prefix that you want to add to the display name of virtual machine on Azure.
Default value: UDPVM_
Recovery Point Snapshots
Specify the number of recovery point snapshots (recovery points) for the standby virtual machine. The maximum number of recovery point snapshots count is 29.
Default value: 5
Combine all unconverted sessions into a single recovery point snapshot
Select if you want to combine all unconverted sessions into a single recovery point snapshot when next scheduled VSB job takes place.
Default: Selected
Virtual Machine Size
Microsoft Azure provides a wide selection of Virtual Machine Sizes optimized to suit different use cases. They have varying combinations of CPU, memory, storage, and networking capacity. For more information about Virtual Machine Size and how they meet your computing needs, view Sizes of Windows virtual machine in Azure.
Storage Account Name
Select an existing Storage Account Name or create a Storage Account in Azure. When you create Storage Account in Azure, you must specify one of the following as Account Kind
For more information, see Storage account in Azure.
Virtual Network
Select an existing Virtual Network or create a Virtual Network in Azure. For more information, see Virtual Network in Azure.
Subnet
Select an existing Virtual Network Subnet based on the selected Virtual Network or add a Subnet in Azure. For more information, see Add Subnet in Azure.
Network Security Group
Select an existing Network Security Group or create a Network Security Group in Azure. Configure the security group rules to open the related ports, including 3389 for remote desktop, 8014, 8015 for Arcserve UDP communication. For more information, see Network Security Group.
Enable auto assign Public IP
Select to assign the public IP to Standby VM automatically when the standby VM starts in Azure.
Automatically start the Virtual Machine
Specify if you want to start the virtual machine automatically.
Note: This option is not available 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 Azure.
Timeout
Specify the time that the monitor server must wait for a heartbeat before a recovery point snapshot is powered on .
Frequency
Specify the frequency that the source server communicates the heartbeats to the monitor server.
Example: The Timeout value specified is 60. The Frequency value specified is 10. The source server communicates 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.
Customize job parameters
You can customize job parameters for the following options:
Enable Email Alerts
Select to enable email alerts. You receive email alerts based on the settings that you provide.
Note: This option is not available for the 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.
Note: This option is not available for host-based virtual machine nodes and the 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.
You have successfully created and deployed the Virtual Standby to Azure plan.