Veeam Data Cloud
User Guide
ASK LLM
Ask ChatGPT
Ask Claude
Ask Gemini
Ask Grok
Ask Perplexity
Related documents
Search

Considerations and Limitations

Before you start using Veeam Data Cloud for AWS and protecting your AWS resources, keep in mind the following limitations and considerations.

Deployment

Veeam Data Cloud for AWS is available only in AWS Global and AWS GovCloud (US) regions.

Software

To access Veeam Data Cloud for AWS, use Microsoft Edge (Chromium only), Mozilla Firefox (latest version) or Google Chrome (latest version). Internet Explorer is not supported.

EC2 Backup

When protecting EC2 instances, consider the following:

When Veeam Data Cloud for AWS backs up EC2 instances with IPv6 addresses assigned, it does not save the addresses. That is why when you restore these instances, IP addresses are assigned according to the settings specified in AWS for the subnet to which the restored instances will be connected.

  • Veeam Data Cloud for AWS may fail to create image-level backups of EC2 instances with product codes if the AMIs that were used to deploy the instances do not support the type of worker instances deployed for the backup operation.
  • [Applies only to image-level backups and file-level recovery from cloud-native snapshots] Veeam Data Cloud for AWS does not support creating image-level backups and restoring EC2 instances with product codes that have vendor restrictions preventing root EBS volumes from being attached to worker instances as secondary volumes. To learn how Veeam Data Cloud for AWS performs EC2 backup, see Protecting EC2 Instances.
  • Veeam Data Cloud for AWS does not support creating cloud-native snapshots and image-level backups for arm64-based EC2 instances if these instances were deployed from AMIs containing product codes.
  • Veeam Data Cloud for AWS runs retention sessions for backup policies at 4:00 AM by default, according to the time zone set on the backup appliance.

RDS Backup

When protecting RDS resources, consider the following:

The IAM role that is associated with the SQLSERVER_BACKUP_RESTORE option must have the permissions required to access temporary Amazon S3 buckets. The IAM role must also have a trust relationship and a permissions policy attached to allow the Amazon RDS service to assume the role. For more information on the backup and restore option, see AWS Documentation.

  • Veeam Data Cloud for AWS runs retention sessions at 4:00 AM by default, according to the time zone set on the backup appliance.

DynamoDB Backup

When protecting DynamoDB tables, consider the following:

  • Veeam Data Cloud for AWS supports creating cloud-native backups for DynamoDB tables only to the same AWS accounts to which the source tables belong.

For Veeam Data Cloud for AWS to be able to create cloud-native backups for DynamoDB tables, you must configure the AWS Backup settings to enable both the Opt-in service and the advanced features for Amazon DynamoDB backups. Otherwise, Veeam Data Cloud for AWS will automatically enable these settings for each AWS Region specified in the backup policy settings in your AWS account while performing backup operations. For more information on advanced DynamoDB backup, see AWS Documentation.

  • Veeam Data Cloud for AWS uses the AWS Backup service to create DynamoDB backups. The DynamoDB backup service is not supported.
  • Veeam Data Cloud for AWS runs retention sessions at 4:00 AM by default, according to the time zone set on the backup appliance.

Redshift Clusters Backup

When protecting Redshift clusters, consider the following:

For Veeam Data Cloud for AWS to be able to create cloud-native backups of Redshift clusters, you must enable the Opt-in service for the Redshift resource type in the AWS Backup settings. Otherwise, Veeam Data Cloud for AWS will automatically enable the service for each AWS Region specified in the backup policy settings in your AWS account while performing backup operations. For more information on considerations for using AWS Backup with Amazon Redshift, see AWS Documentation.

  • Veeam Data Cloud for AWS runs retention sessions at 4:00 AM by default, according to the time zone set on the backup appliance.

Redshift Serverless Backup

When protecting Redshift Serverless namespaces, consider the following:

  • Veeam Data Cloud for AWS supports creating cloud-native backups for Redshift Serverless namespaces only to the same AWS accounts to which the source namespaces belong and the same AWS Region where the source namespaces reside.
  • Make sure that workgroups are associated with Redshift Serverless namespaces that you plan to protect. Otherwise, the backup operation may fail to complete successfully.
  • Veeam Data Cloud for AWS runs retention sessions at 4:00 AM by default, according to the time zone set on the backup appliance.

EFS Backup

When protecting EFS file systems, consider the following:

  • Veeam Data Cloud for AWS runs retention sessions at 4:00 AM by default, according to the time zone set on the backup appliance.

FSx Backup

When protecting FSx file systems, consider the following:

  • Veeam Data Cloud for AWS supports creating cloud-native backups for FSx file systems only to the same AWS accounts to which the source file systems belong.

For Veeam Data Cloud for AWS to be able to create cloud-native backups for FSx file systems, you must enable the Opt-in service for the FSx resource type in the AWS Backup settings. Otherwise, Veeam Data Cloud for AWS will automatically enable the service for each AWS Region specified in the backup policy settings in your AWS account while performing backup operations.

  • Veeam Data Cloud for AWS does not support creating cloud-native backups for Amazon FSx for NetApp ONTAP file systems. However, you can back up Amazon FSx for NetApp ONTAP file systems using the Veeam Backup & Replication console. For more information, see the Veeam Backup & Replication User Guide, section Unstructured Data Backup.
  • Veeam Data Cloud for AWS does not support creating cloud-native backups for Amazon FSx for Windows File Server file systems that use AWS Secrets Manager to store service account credentials when joined to a self-managed Microsoft Active Directory (AD).
  • Veeam Data Cloud for AWS does not support creating cloud-native backups for Amazon FSx for Lustre file systems with the Scratch deployment type.
  • Veeam Data Cloud for AWS does not support creating cloud-native backups for Amazon FSx for Lustre with the data repository association.
  • Veeam Data Cloud for AWS uses the AWS Backup service to create FSx backups and backup copies. The AWS Backup service does not support creating backup copies of FSx backups stored in Opt-in Regions.
  • Veeam Data Cloud for AWS runs retention sessions at 4:00 AM by default, according to the time zone set on the backup appliance.

EC2 Restore

When restoring EC2 instances, consider the following:

  • If you restore multiple EC2 instances that have the same EBS volume attached, Veeam Data Cloud for AWS creates a separate volume for each instance and enables the Multi-Attach option for all volumes. After the restore operation completes, you can manually delete extra EBS volumes in the AWS Management Console and attach the necessary volume to the instances.

For more information on Amazon EBS Multi-Attach, see AWS Documentation.

  • [Applies only if you plan to restore EBS volumes] Veeam Data Cloud for AWS does not attach restored EBS volumes to any EC2 instances — the volumes are placed to the specified location as standalone EBS volumes.
  • [Applies only if you plan to restore EC2 instances to a new location or with different settings] Veeam Data Cloud for AWS restores EC2 instances with a single network interface and assigns a new primary private IP address to each instance.
  • [Applies only if you plan to restore EC2 instances to the original location] Veeam Data Cloud for AWS restores the instance and all network interfaces that were attached to the source EC2 instance. However, there are limitations regarding Elastic IP and private IP addresses. For more information, see Performing EC2 Instance Restore.
  • [Applies only if you plan to restore EC2 instances to the original location] If stop protection or termination protection is enabled on an EC2 instance, Veeam Data Cloud 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.
  • [Applies only if you plan to restore EC2 instances to the original location] Veeam Data Cloud for AWS does not support restoring EC2 instances if the source instances with termination protection and stop protection enabled still exist in AWS.
  • Veeam Data Cloud for AWS does not support restore of IPv6 addresses, tags of Elastic IP addresses or prefixes assigned to Amazon EC2 network interfaces attached to EC2 instances.

RDS Restore

When restoring RDS resources, consider the following

For more information on Amazon Aurora Global Database feature, see AWS Documentation.

  • When restoring Aurora DB clusters to a new location, Veeam Data Cloud for AWS creates only primary DB instances in the restored clusters. Additional writer DB instances (for Aurora multi-master clusters) or Aurora Replicas (for Aurora DB clusters with single-master replication) must be added manually in the AWS Management Console after the restore operation completes.

To learn how to add DB instances to Amazon Aurora DB clusters, see AWS Documentation.

  • Veeam Data Cloud for AWS does not support restoring RDS resources to the original location if deletion protection is enabled for the source resource.
  • [Applies only if you perform restore databases of Microsoft SQL Server and PostgreSQL DB instances from image-level backups] Keep in mind the following:
  • Veeam Data Cloud for AWS supports restoring databases only to the same AWS Region where the source DB instances reside.
  • The database account that you specify for the restore operation will become the owner of all restored databases.
  • Veeam Data Cloud for AWS does not support restoring original database accounts, including their predefined roles and access privileges. Therefore, you will have to manually recreate these accounts on the restored databases and reassign their privileges after the restore process completes.
  • [Applies only if you perform restore databases of Microsoft SQL Server DB instances from image-level backups] Keep in mind the following:
  • The target DB instance must be set to the same time zone as the source DB instance. Otherwise, your applications may encounter data consistency issues.
  • The target DB instance must run the same or a later engine version as the source DB instance. Otherwise, the restore operation will fail to complete successfully.
  • Veeam Data Cloud for AWS does not support restoring databases that contain the FILESTREAM file group.
  • Veeam Data Cloud for AWS does not support restoring databases of DB instances that have a zero backup retention period to DB instances that have a nonzero retention period due to the incompatibility in database recovery models. This is the expected behavior caused by AWS technical limitations.

DynamoDB Restore

When restoring DynamoDB tables, consider the following:

  • Veeam Data Cloud for AWS supports restoring DynamoDB tables only to the same AWS account to which the source tables belong.
  • Veeam Data Cloud for AWS supports restoring only those DynamoDB table properties that are described in section DynamoDB Backup.
  • The AWS Backup service does not support copying DynamoDB cloud-native backups stored in a cold storage tier to another AWS Region. These means that you will only be able to use these backups to restore tables to the same AWS Region in which the backups reside after being transitioned from a warm storage tier.
  • You can change the Time to Live (TTL) setting for DynamoDB tables only an hour after the restore operation completes.

 

Redshift Restore

When restoring Redshift clusters, consider the following:

  • Veeam Data Cloud for AWS supports restoring Amazon Redshift clusters only to the same AWS accounts to which the source clusters belong and the same AWS Region where the source clusters reside.
  • Veeam Data Cloud for AWS supports restoring only those Redshift cluster properties that are described in section Redshift Clusters Backup.
  • Veeam Data Cloud for AWS does not support restoring Amazon Redshift clusters with the Multi-AZ deployment. These clusters will be restored as clusters with the Single-AZ deployment.

Redshift Serverless Restore

When restoring Redshift Serverless namespaces, consider the following:

  • Veeam Data Cloud for AWS supports restoring Amazon Redshift Serverless namespaces only to the same AWS accounts to which the source namespaces belong and the same AWS Region where the source namespaces reside.
  • Veeam Data Cloud for AWS supports restoring only those Redshift Serverless namespace properties listed in section Redshift Serverless Backup.
  • Veeam Data Cloud for AWS does not support restoring Amazon Redshift Serverless namespaces to provisioned clusters.
  • Veeam Data Cloud for AWS does not support restoring tables of Amazon Redshift Serverless namespaces.

EFS Restore

Veeam Data Cloud for AWS supports restoring EFS file systems only to the same AWS account to which the source file systems belong.

FSx Restore

When restoring FSx file systems, consider the following:

  • Veeam Data Cloud for AWS supports restoring FSx file systems only to the same AWS accounts to which the source file systems belong.
  • Veeam Data Cloud for AWS supports restoring only those FSx file system properties that are described in section FSx Backup.
  • Veeam Data Cloud for AWS does not support restoring Amazon FSx for Windows File Server file systems that use AWS Secrets Manager to store service account credentials when joined to a self-managed Microsoft Active Directory (AD).

 

View all results across Veeam Help Center
Back to document search