Virtual Standby to EC2 Considerations

Verify that your AWS EC2 instance is used as the VSB cloud proxy with the upgraded latest Amazon PV drivers.

Limitations for Virtual Standby to EC2:

• Due to AWS limitation, VSB to EC2 cannot protect the UEFI node.
• Due to AWS limitation, the protected node must be installed with .NET Framework 4.5.
• The first conversion in AWS takes time depending on the size of the data. As a result, the snapshot generation also takes time.
• The Virtual Standby instance is launched in the same available zone as of the cloud proxy.
• VSB to EC2 only supports Windows 2019, Windows 2016, Windows 2012 R2, Windows 2012 x86/x64, Windows 2008 R2, and Windows 2008 x86/x64.
• Amazon VM uses the private IP assigned by Amazon irrespective of the value set in backup network settings and TCP/IP settings.
• The system and boot volume on the source node in VSB to EC2 plan must be at the first disk due to AWS limitation.
• You cannot modify Enable/Disable auto assign public IP property for the existing nodes in the plan and the update only affects the new nodes added into the plan.
• The elastic IP address assignment is only available for the first network interface on EC2 instance.
• The customization to TCP/IP setting cannot apply to the first network interface on EC2 instance due to AWS limitation.
• The customization to TCP/IP setting is only applicable to the scenario when Direct Access or VPN is configured between primary site and the AWS network. Otherwise, the customization makes the EC2 instance inaccessible.
• Attaching more than 26 volumes with AWS PV driver that is used by Arcserve UDP in one instance may result in performance issues. For more information, see link. We recommend that you create multiple plans with different Cloud proxies on EC2 if the protected nodes need to convert more than 26 volumes to standby instances on EC2.
• The Cloud proxy node is same as the Arcserve UDP Agent and no additional software is required for the Cloud proxy node. As the Cloud proxy node needs to write data to the attached EBS volumes of standby instances, we recommend that you use M or upper series in general purpose instance family to create cloud proxy. For example, m4.largerve | m4.xlarge | m4.2xlarge | m4.4xlarge | m4.10xlarge | m4.16xlarge | m3.medium | m3.large | m3.xlarge | m3.2xlarge.
• When protecting the instances in EC2 with VSB task configured, the VSB proxy instance and the protected agent are not available from the same AMI.
• When protecting the instances in EC2 with VSB task configured, the protected agents on the same proxy are not available from the same AMI.
• VSB to EC2 cannot protect the node having Dynamic system disk for Source machine.