Review the Prerequisites and Considerations

Verify if you have completed the following prerequisites:

• 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
• Back up the full machine to enable the Virtual Standby task. You cannot create a Virtual Standby task if the backup is not a full backup.
• 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.

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

• Configure the Security group setting on EC2 to open the related ports for inbound access, including TCP 8014 and TCP 4091.
• Verify if the Amazon AWS account can access AWS S3 and AWS EC2. Arcserve UDP does not provide the account.
• You must 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.
• Specific AWS API permissions are required for Amazon IAM users to achieve control and interaction with AWS APIs for VSB to EC2. For details, refer to How to configure IAM granular permissions for IAM users with VSB to EC2.

Considerations:

• .NET framework 4.5 is needed on the source machine to install Amazon PV driver for Virtual Standby to EC2 task.
• The system and boot volume on the source in VSB to EC2 plan must be at the first disk due to AWS limitation.
• The customization to TCP/IP setting cannot apply to the first network interface on EC2 instance due to AWS limitation.
• The elastic IP address assignment is only available for the first network interface on EC2 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 AWS network. Otherwise, the customization makes the EC2 instance inaccessible.
• You cannot modify Enable/Disable auto assign public IP property for the existed sources in the plan and the update only affects the new sources added into the plan.
• You must install PowerShell version 3.0 or above on the source machine before configuring the VSB to EC2 for the following instance types:
• C5, C5d, C5n, F1, G3, G4, H1, I3, I3en, Inf1, m4.16xlarge, M5, M5a, M5ad, M5d, M5dn, M5n, P2, P3, R4, R5, R5a, R5ad, R5d, R5dn, R5n, T3, T3a, X1, X1e, and z1d