Before You Begin
Before you restore EC2 instances, consider the following limitations:
- To restore an EC2 instance from a backup that is stored in an archive backup repository, you must retrieve the archived data first. You can either retrieve the archived data manually before you begin the restore operation, or launch the data retrieval process right from the Restore wizard. To learn how to retrieve data manually, see Retrieving EC2 Data From Archive.
- When you restore an EC2 instance to a new location or with different settings, Veeam Backup for AWS will restore the instance with one network interface and will assign a new primary private IP address to the restored instance.
- If stop protection or termination protection are enabled for an EC2 instance, Veeam Backup for AWS will not be able to restore the instance and will raise an error notifying that you must disable stop protection or termination protection on the source instance.
- Veeam Backup for AWS does not support restore of IPv6 addresses, tags of Elastic IP addresses and prefixes assigned to Amazon EC2 network interfaces.
- When you restore an EC2 instance to the original location, Veeam Backup for AWS will restore the instance and all network interfaces that were attached to the source EC2 instance. However, consider the following:
- If the Elastic IP address that was assigned to the source EC2 instance is still assigned to this EC2 instance, the address will be reassigned to the restored instance.
- If the Elastic IP address is in use by any other EC2 instance, Veeam Backup for AWS will raise a warning. If you decide to proceed with the restore operation, the address will not be associated with the restored instance. Note that Veeam Backup for AWS will not allocate a new Elastic IP address to your AWS account.
- If the Elastic IP address that was assigned to the source EC2 instance has been removed from AWS, Veeam Backup for AWS will attempt to restore this address using the native AWS capabilities.
- If private IP addresses that were assigned to the source EC2 instance are in use by the source or any other EC2 instance, Veeam Backup for AWS will raise a warning. If you decide to proceed with the restore operation, the restored EC2 instance will be assigned new private IP addresses.
- If the source instance still exists in AWS, Veeam Backup for AWS will raise a warning. If you decide to proceed with the restore operation, the source EC2 instance, including all EBS volumes and all network interfaces attached to it, will be automatically deleted from AWS.
Note that EBS volumes excluded from the backup scope and volumes for which the DeleteOnTermination attribute is set to false will also be deleted from AWS.
- An IAM role you plan to specify for the restore operation must have the following permissions: outposts:ListOutposts, outposts:GetOutpostInstanceTypes. To grant the necessary permissions for the IAM role, use the AWS Management Console. For more information on how to grant permissions to an IAM role, see AWS Documentation.
- If an Outpost subnet is specified in the worker instance network settings, restore of an EC2 instance to an AWS Region to which the AWS Outpost is connected may fail. The issue occurs if the default worker instance type is not supported for the AWS Outpost. To work around the issue, change the default worker profiles as described in section Managing Worker Profiles.