Limitations and Considerations

In this article

    When restoring Aurora DB clusters, mind the following limitations and considerations.

    IAM Roles and Users

    The IAM role and IAM user that you plan to use when restoring clusters must have permissions described in this Veeam KB article.

    Public Access

    To allow public access to a cluster, the security group which you plan to use for the restored cluster must allow public access.

    Restore Mode

    When you choose the restore mode at the Restore Mode step of the wizard, mind the following:

    • If you select the Restore to new location, or with different settings option, AWS Plug-in for Veeam Backup & Replication creates only the primary DB instance in the restored cluster. Additional writer DB instances (for an Aurora multi-master cluster) or Aurora Replicas (for an Aurora DB cluster 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.

    If you select the Restore to the original location option, AWS Plug-in for Veeam Backup & Replication restores the whole cluster infrastructure including the primary DB instance and Aurora Replicas (for an Aurora DB cluster with single-master replication) or writer and reader DB instances (for an Aurora multi-master cluster). After the restore process completes successfully, the source cluster will be automatically powered off and removed from Amazon RDS (the exception is global database).

    • [For global databases] AWS Plug-in for Veeam Backup & Replication restores only the primary Aurora DB cluster in the primary AWS Region. AWS Plug-in for Veeam Backup & Replication restores this cluster according to the rules described in the previous list item.

    If you select the Restore to new location, or with different settings option, you must select version that supports the global database feature at the Capacity type step of the wizard.

    If you select the Restore to the original location option, and the source cluster is still present in the AWS infrastructure, the primary DB cluster will be restored under veeam-temp-<cluster_name>-<guid> name. The source cluster will not be removed.

    After restore completes, you must create reader DB instances and secondary DB clusters manually in the AWS Management Console. For more information on Amazon Aurora global databases, see AWS Documentation.

    • The Restore to the original location option is disabled in the following cases:
    • If the IAM role that you specify for restore belongs to an AWS account other than the AWS account where the source cluster belongs.
    • If snapshots of clusters from which you restore are Amazon snapshots created in AWS without using Veeam Backup for AWS.
    • [For Aurora MySQL DB clusters with single-master replication] To be able to use Aurora MySQL parallel query feature when restoring cluster to a new location or with different settings, you must select the version that supports the parallel query feature at the Capacity type step of the wizard. Also, you must enable the aurora_parallel_query parameter in the DB cluster parameter group that you will specify at the Instance Configuration step of the wizard. For more information on Aurora MySQL parallel query, see AWS Documentation.
    • 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 another AWS account. To specify an AWS account in which the clusters will be restored, select an IAM role that belongs to the necessary account.

    Mind that restore of Aurora multi-master clusters using restore points of Amazon snapshots created in AWS without using Veeam Backup for AWS is supported only to the source region within the same AWS account.

    • For the Africa (Cape Town), Asia Pacific (Hong Kong), Europe (Milan), Middle East (Bahrain) regions, mind the following:
    • You cannot restore clusters to the listed regions if the source region differs from the target region specified for the restore operation.
    • You can restore clusters that reside in the listed regions only to the original location. This also includes restore to the original location but with different settings. To restore clusters with different settings, select the Restore to new location, or with different settings option, specify the original location of the processed clusters and change other settings as required.

    Capacity Types and Engine Versions

    When you choose capacity types and engine versions at the Cluster Capacity step of the wizard, mind the following:

    • You can change the capacity type of the restored cluster from provisioned to Aurora Serverless v1 only for the source provisioned DB clusters 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.
    • Aurora Serverless v2 is supported only for a limited list of DB engine versions. For more information, see AWS Documentation.
    • You cannot specify the capacity range for the restored Aurora Serverless v2 DB cluster. If the source DB cluster has the Serverless (db.serverless) instance class, AWS Plug-in for Veeam Backup & Replication restores the cluster with the backed-up capacity range. Otherwise, AWS Plug-in for Veeam Backup & Replication restores the Aurora Serverless v2 DB cluster with the default capacity range — 8-64 Aurora Capacity Units (ACUs).

    If you want to change capacity range for the restored cluster, you must do it manually in the AWS Management Console as described in AWS Documentation.

    Encryption

    When you configure encryption at the Capacity Type step of the wizard, mind the following:

    • KMS keys must be from the same AWS Region as that you will specify at the Data Center step of the wizard.
    • The IAM role or IAM user that will be used for restore must have permissions to access the KMS key.
    • If you plan to restore an unencrypted provisioned DB cluster to an Aurora Serverless DB cluster, and you select the Preserve the original encryption settings option, mind that Veeam Backup for AWS will encrypt the newly created Aurora Serverless DB cluster with the default KMS key in the target AWS Region. For more information on Aurora Serverless, see AWS Documentation.