You can configure SQL Server databases on an AWS EC2 instance. The configuration wizard guides you through the configuration process, which includes creating any new entities that are needed, such as a plan, an object storage client, and a content group.
Procedure
-
From the navigation pane, go to Protect > Databases.
The Overview page appears.
-
In the upper-right area of the page, click Add server.
The Select Database Type page appears.
-
Select SQL server.
The Select Your Database Environment page appears. -
Select Database running in the cloud VM.
-
From the Select vendor list, select Amazon Web Services.
An active trial or an active subscription is required.
-
Click Next.
The Backup Method page appears.
-
Review the information.
-
Click Next.
The Configure Permissions page appears.
-
Select any one of the authentication methods:
-
For IAM role, do the following:
-
From the Authentication method list, select IAM role.
-
Verify an existing MetallicRole IAM role or create a new MetallicRole IAM role:
-
If the MetallicRole IAM role was previously created for another AWS workload, do the following:
-
Verify that the IAM policies for the AWS workload are still attached to the MetallicRole IAM role.
-
At the bottom of the page, select the confirmation check box.
-
-
If the MetallicRole IAM role does not exist yet, create it in AWS.
-
-
-
For Access and secret key, do the following:
-
From the Authentication method list, select Access and secret key.
-
Verify an existing MetallicUserGroup IAM user group or create a new MetallicUserGroup IAM user group:
-
If the MetallicUserGroup IAM user group was previously created for another AWS workload, do the following:
-
Verify that the IAM policies for the AWS workload are still attached to the MetallicUserGroup IAM user group.
-
At the bottom of the page, select the confirmation check box.
-
-
If the MetallicUserGroup IAM user group does not exist yet, create it in AWS.
-
-
-
For STS Assume Role with IAM Policy, do the following:
-
From the Authentication method list, select STS assume role with IAM policy.
-
Verify an existing MetallicAdminRole IAM role or create a new MetallicAdminRole IAM role in the AWS admin account:
-
If the MetallicAdminRole IAM role was previously created for another AWS workload, do the following:
-
Verify that the MetallicAdminRole-STSAssumePolicy IAM policy for the AWS workload is attached to the MetallicAdminRole IAM role.
-
At the bottom of the page, select the confirmation check box.
-
-
If the MetallicAdminRole IAM role does not exist yet, create it in AWS.
-
-
-
-
Click Next.
The Region page of the configuration wizard appears.
-
Select the region that the cloud storage resides in.
-
Click Next.
The Backup Gateway page of the configuration wizard appears.
-
Select an existing backup gateway or create a new backup gateway.
-
Click Next.
The Cloud Storage page of the configuration wizard appears.
-
For the primary copy of the backup data, select an existing S3 storage bucket or create a new S3 storage bucket.
-
Decide whether to store a secondary copy of the backup data for long-term retention.
-
Click Next.
The Plan page of the configuration wizard appears.
-
Select an existing plan or create a new plan.
-
Click Next.
The Install Package page of the configuration wizard appears.
-
To perform a push installation, do the following:
-
Select Push installation.
-
select one or more database servers from the list at the bottom of the page, or add a new database server.
-
To add a new database server, click +, then complete the following in the Add database server page:
-
In the Host name box, enter the host name.
-
For OS Type, select the operating system of the database instance.
-
If you selected Windows, from the Credential list, select the credential.
-
If you selected Unix operating system, do the following:
-
From the Credential list, select the credential.
-
In the UNIX group box, enter the name of the Unix group.
-
In the SSH port number box, verify the port number.
-
If you want to use SSH instead of user credentials, move the Use SSH key toggle to the right, and then in the SSH key path box, enter the file path.
-
To use an SSH key file passphrase, move the Use SSH key file passphrase toggle key to the right, and the in the Passphrase box, enter the passphrase for the SSH key.
Steps to add a credential
-
Click +.
The Add Credential dialog box appears.
-
In the Credential name box, enter a unique name to access the credential.
-
In the User account box, enter the user account that access to the SQL server.
-
In the Password box, enter the password for the user account.
-
In the Description box, enter a brief description for the credential.
-
Click Save.
-
-
-
-
To perform an interactive installation, complete the following:
-
Select Interactive installation.
-
Download the SQL Server package, and then install it on the server you want to back up.
-
Copy the authcode, and then use it to authenticate the SQL Server package on the server.
-
In the Server name drop-down list, select the name of the server.
-
-
Click Next.
The Credentials page appears.
-
To use a saved credential, select the existing credential.
-
To create a new credential, do the following:
-
Click +.
The Add Credential dialog box appears.
-
In the Credential name box, enter a unique name to access the credential.
-
In the User account box, enter the user account that access to the SQL server.
-
In the Password box, enter the password for the user account.
-
In the Description box, enter a brief description for the credential.
-
Click Save.
Note
-
If you are installing the SQL Server on a Windows server, select the Windows account for SQL impersonation. A new credential is added as Windows account.
-
If you are installing the SQL Server on a Linux server, select the SQL account for SQL impersonation. A new credential is added as SQL account.
-
If a credential is not selected, the local system account will be used for impersonation. If a credential is selected, credentials for impersonation should be common between all selected servers. Once the installation is complete, credential will be available for modification at the server level.
-
If you have servers that are running on Windows and Linux, a common credential must not be used. Instead, leave the credential blank and set the impersonation on servers manually after the installation completed.
-
-
Click Next.
The Backup Content page appears.
-
All SQL Server instances that will be auto discovered and protected as per the plan that you selected.
-
Click Next.
-
Review the summary.
-
Click Finish.