Step 4. Configure Target Instance Settings

At the Instance step of the wizard, choose the target DB instance. For an instance to be displayed in the list of available instances, it must reside in the selected AWS Region and belong to the AWS account specified at step 3 of the wizard.

Note

If the specified DB instance is the same instance that hosted the source databases, the next run of the backup policy protecting the source DB instance will take more time to complete in case the restore operation completes successfully. This is the expected behavior caused by AWS technical limitations.

You must also specify credentials of a database account that Veeam Data Cloud for AWS will use to connect to the target DB instance. To do that, click the link next to the Credentials field. In the Configure credentials window, choose whether you want to provide temporary credentials or select an existing database account. Keep in mind that the specified account will become the owner of all restored databases.

For an account to be displayed in the list of available accounts, it must be added to Veeam Data Cloud for AWS as described in section Adding Database Accounts. If you have not added the necessary account beforehand, click Add and complete the Add Account wizard.

Tip

By default, Veeam Data Cloud for AWS restores each database with the same name as the original database. If a database with this name already exists in the production infrastructure, a default suffix is added to the database name automatically. You can also specify a new name for each restored database manually — to do that, select the database in the Database settings section and click Rename.

Considerations and Limitations

When you restore databases, consider the following:

Make sure that the specified database account exists on the target DB instance. Otherwise, the restore operation will fail to complete successfully.
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 to Microsoft SQL Server DB instances] 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.
[Applies only to Microsoft SQL Server DB instances] Make sure that the target DB instance is set to the same time zone as the source DB instance. Otherwise, your applications may encounter data consistency issues.
[Applies only to Microsoft SQL Server DB instances] Make sure that the target DB instance runs the same or a later engine version as the source DB instance. Otherwise, the restore operation will fail to complete successfully.

As Veeam Data Cloud for AWS uses public access for communication between components, the public IPv4 addressing attribute must be enabled at least for one subnet in the Availability Zone where the DB instance resides and the VPC network to which the subnet belongs must have an internet gateway attached. VPC network and subnet route tables must have routes that direct internet-bound traffic to this internet gateway.

If the DB instances hosting databases added to the restore session operate in a private network (that is, connected to subnets with auto-assignment of public IPv4 addresses disabled), configure VPC interface endpoints as described in section How to Configure Endpoints in AWS.