Limitations and Considerations
When restoring Aurora DB clusters, keep in mind the following limitations and considerations.
IAM Roles and Users
An IAM role and IAM user that you plan to use to perform the restore operation must have permissions described in section RDS Restore IAM Permissions.
The security group associated with the restored Aurora DB cluster must allow inbound internet access from both the backup server and a local machine that you plan to use to work with Veeam Backup for AWS.
Before you choose the restore mode, consider the following limitations:
- Restore of Aurora DB clusters to the original location is not supported if the IAM role specified for the restore operation belongs to an AWS account that differs from the AWS account where the source cluster belongs.
- Restore of Aurora DB clusters to the original location is not supported using restore points of the AWS Snapshot type — you can restore these resources only to a new location.
- Restore of Aurora multi-master clusters is not supported if the source region differs from the target region specified for the restore operation. However, you can restore these clusters to the source region in the same or in the another AWS account. To specify an AWS account to which the cluster will be restored, select an IAM role that belongs to the necessary account at step 3 of the Restore Amazon RDS Cluster wizard.
Note that restore of Aurora multi-master clusters using restore points of the AWS Snapshot type is supported only to the source region within the same AWS account.
- When restoring to a new location, Veeam Backup & Replication creates only the primary DB instances in the restored clusters. Additional writer DB instances (for Aurora multi-master clusters) and Aurora Replicas (for Aurora DB clusters with single-master replication) must be added manually in the AWS after the restore operation completes.
To learn how to add DB instances to Amazon Aurora DB clusters, see AWS Documentation.
- When restoring Aurora global databases, Veeam Backup & Replication restores only primary Aurora DB clusters in the primary AWS Regions; secondary clusters must be created manually in the AWS after the restore operation completes. If source clusters are still present in AWS, primary DB clusters will be restored with the veeam-temp-<cluster_name>-<guid> name pattern; the source clusters will not be removed automatically.
For more information on Amazon Aurora global databases, see AWS Documentation.
Before you choose a capacity type for the restored cluster, consider the following limitations:
- You can restore an Aurora Serverless DB cluster either as an Aurora Serverless DB cluster or as an Aurora provisioned DB cluster. However, you cannot restore an Aurora provisioned DB cluster as an Aurora Serverless DB cluster unless the source cluster is running the following DB engine versions: MySQL 5.6.10a, MySQL 2.07.1, PostgreSQL 10.12 and PostgreSQL 10.14.
- Aurora Serverless v1 is supported for a limited list of AWS Regions and specific DB engine versions. For more information, see AWS Documentation.