Configuring Settings for Aurora DB Clusters

A number of settings that you can configure for a restored cluster depends on the capacity type that you plan to choose for the cluster. AWS supports Aurora DB clusters of 2 different capacity types:

  • Aurora provisioned DB cluster — a cluster whose capacity is managed manually by creating DB instances: a single primary DB instance (writer) and multiple Aurora Replicas (readers) in Aurora DB clusters with single-master replication, and multiple DB instances (writers) in Aurora multi-master clusters. For more information on provisioned DB clusters, see AWS Documentation.
  • Aurora Serverless DB cluster  — a clusters whose capacity is scaled automatically according to the specified minimum and maximum capacity values. For more information on Aurora Serverless, see AWS Documentation.

Before you choose a capacity type for the restored cluster, consider the following limitations:

  • Aurora Serverless is supported only for a limited list of AWS Regions and specific DB engine versions. For more information, see AWS Documentation.
  • 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.

Configuring Settings for Provisioned Cluster

To specify settings for a restored Aurora DB cluster, at the Settings step of the wizard, select the necessary cluster and click Edit. In the opened window, do the following:

  1. In the Instance specifications section, specify configuration settings for the restored Aurora DB cluster:
  1. From the Capacity type drop-down list, select Provisioned.

Note

You cannot change replication settings for restored Aurora DB clusters. Veeam Backup for AWS restores the clusters with the same replication settings configured for the source clusters.

  1. [This step applies only to Aurora MySQL DB clusters with single-master replication and Aurora PostgreSQL DB clusters] Set the Use global database toggle to On if you plan that the restored cluster will have secondary DB clusters in a number of AWS Regions. In this case, the Version list will be filtered to show only Aurora database versions that support this feature. However, Veeam Backup for AWS will still create only a primary cluster in the AWS Region selected at step 4; secondary clusters must be created manually in the AWS Management Console after the restore operation completes.

For more information on Amazon Aurora global databases, see AWS Documentation.

  1. [This step applies only to Aurora MySQL DB clusters with single-master replication] Set the Use parallel query toggle to On if you plan to use the Aurora MySQL parallel query feature to improve I/O performance and to reduce network traffic in the restored cluster. In this case, the Version list will be filtered to show only Aurora database versions that support this feature. Keep in mind that to be able to use the feature, you must enable the aurora_parallel_query parameter in the DB cluster parameter group that you will specify in the Instance options section.

For more information on Aurora MySQL parallel query, see AWS Documentation.

  1. From the Version drop-down list, select an Aurora database engine version for the restored cluster. The list shows only DB engine versions supported in the target AWS Region, and is filtered based on the DB engine type and DB engine version of the source Aurora DB cluster. The number of versions displayed in the list also depends on the source cluster replication settings and options that you have selected at steps 1b and 1c.

For more information on Amazon Aurora database engine versions, see AWS Documentation.

Note

If you restore Aurora PostgreSQL DB clusters and plan to use the Babelfish feature to allow the restored clusters to accept database connections from Microsoft SQL Server clients, mind that this feature is supported only for Aurora PostgreSQL 13.4 and later engine versions.

  1. In the Cluster identifier field, specify an identifier for the restored cluster. Consider the following limitations:
  • The cluster identifier must be unique for each AWS Region within one AWS Account.
  • The cluster identifier can contain only lowercase Latin letters and hyphens, but cannot contain two consecutive hyphens.
  • The first character of the cluster identifier must be a letter. The last character of the identifier must not be a hyphen.
  • The maximum length of the cluster identifier is 63 characters.

For more information on limitations for Aurora DB cluster identifiers, see AWS Documentation.

  1. From the Instance class drop-down list, select a DB instance class that Veeam Backup for AWS will use to create the primary DB instance in the restored cluster.

For the list of all supported DB instance classes, see AWS Documentation.

Note

Veeam Backup for AWS supports Aurora Serverless v2. To restore the primary DB instance of the provisioned cluster as an Aurora Serverless v2 DB instance, select  db.serverless from the Instance class drop-down list.

Mind the following limitations:

  • Aurora Serverless v2 is supported only for a limited list of DB engine versions. For more information, see AWS Documentation.
  • You cannot specify a capacity range for the restored Aurora Serverless v2 DB instance. If the source DB instance had the same instance class, Veeam Backup for AWS will restore the instance with the backed-up capacity range. Otherwise, Veeam Backup for AWS will restore the Aurora Serverless v2 DB instance with the default capacity range — 8-64 Aurora Capacity Units (ACUs).
  1. In the Instance identifier field, specify an identifier for the primary DB instance in the restored cluster. Consider the following limitations:
  • The instance identifier must be unique for each AWS Region within one AWS Account.
  • The instance identifier can contain only lowercase Latin letters and hyphens, but cannot contain two consecutive hyphens.
  • The first character of the instance identifier must be a letter. The last character of the identifier must not be a hyphen.
  • The maximum length of the instance identifier is 63 characters.

For more information on limitations for DB instance identifiers, see AWS Documentation.

  1. In the Instance options section, specify a DB cluster parameter group that will be associated with the restored cluster and a DB parameter group that will be associated with the primary DB instance:
  1. From the Cluster parameter group drop-down list, select the DB cluster parameter group containing database engine configuration values that will be applied to every DB instance launched in the restored cluster.

For a DB cluster parameter group to be displayed in the list, the group must be created beforehand as described in AWS Documentation.

  1. From the Parameter group drop-down list, select the DB parameter group containing database engine configuration values that will be applied to the primary DB instance in the restored cluster.

For a DB parameter group to be displayed in the list, the group must be created beforehand as described in AWS Documentation.

Note

If Veeam Backup for AWS cannot find any parameter groups in the target AWS Region, the Use default group option will be displayed. Use this option to associate the restored DB cluster and the primary DB instance with the default parameter groups that will be automatically created by AWS during the restore operation.

  1. Click Apply.

Restoring RDS Resources

Configuring Settings for Serverless Cluster

To specify settings for a restored Aurora DB cluster, at the Settings step of the wizard, select the necessary cluster and click Edit. In the opened window, do the following:

  1. In the Instance specifications section, specify configuration settings for the restored Aurora DB cluster:
  1. From the Capacity type drop-down list, select Serverless.
  2. From the Version drop-down list, select an Aurora database engine version for the restored cluster. The list shows only DB engine versions supported in the target AWS Region, and is filtered based on the DB engine type and DB engine version of the source Aurora DB cluster.

For more information on Amazon Aurora database engine versions, see AWS Documentation.

  1. In the Cluster identifier field, specify an identifier for the restored cluster. Consider the following limitations:
  • The cluster identifier must be unique for each AWS Region within one AWS Account.
  • The cluster identifier can contain only lowercase Latin letters and hyphens, but cannot contain two consecutive hyphens.
  • The first character of the cluster identifier must be a letter. The last character of the identifier must not be a hyphen.
  • The maximum length of the cluster identifier is 63 characters.

For more information on limitations for Aurora DB cluster identifiers, see AWS Documentation.

  1. Use the Minimum capacity unit and Maximum capacity unit fields to specify a range of capacity units that will be used to create scaling rules for the restored cluster. These rules define thresholds for CPU utilization, connections and available memory.

For more information on capacity units and scaling rules, see AWS Documentation.

  1. In the Instance options section, specify a DB cluster parameter group containing database engine configuration values that will be applied to the restored cluster.

For a DB cluster parameter group to be displayed in the Cluster parameter group list, the group must be created beforehand as described in AWS Documentation.

Note

If Veeam Backup for AWS cannot find any parameter groups in the target AWS Region, the Use default group option will be displayed. Use this option to associate the restored DB cluster with the default DB parameter group that will be automatically created by AWS during the restore operation.

  1. Click Apply.

Restoring RDS Resources