Complete the Databases Guided Setup for Microsoft Azure for MySQL

The Databases guided setup guides you through creating a backup plan and adding a Azure Database for MySQL.

To complete the guided setup, you need the following information:

• The server name

• The host name

• The credentials that you use to access the server

Procedure

1. From the navigation pane, go to Guided setup.

   The Welcome page appears.

2. In the Databases tile, click Configure.

3. On Configure Database Server page, select Database running in the cloud (PaaS).

4. Select Microsoft Azure, and then click Next.

5. On the Configure Azure Database page, select MySQL, and then click Next.

   The Configure Azure Database - MySQL page appears.

6. In the Plan section, either select an existing backup plan to use for the instance or add a new plan, and then click Next.

7. From the Cloud account list, either select an existing cloud account or add a new cloud account, and then click Next.

   Steps to add new cloud account

   1. Beside the Cloud account list, click +.

      The Add cloud account dialog box appears.

   2. In the Name box, type the name for the account.

   3. Enter the information about the subscription:

      • For the traditional authentication method of deployment, enter the following information:

        • Subscription ID: Enter the subscription ID for the Azure account.

        • Credential: select a saved credential or add a new credential.

      • For the managed identity authentication method of deployment, configure the following settings:

        • Connect using managed identities for Azure resources: Move the toggle key to the right.

        • Subscription ID: Enter the subscription ID for the Azure account.

   4. From the Access node list, select access nodes that have both the Virtual Server and Cloud Apps packages installed.

      Note: If you configure this cloud account to use managed identity authentication, select only Azure access nodes that use managed identity authentication so that backups and restores will be successful. The access node must be an Azure virtual machine in the same subscription that contains the Cosmos DB account that you want to back up.

   5. Click SAVE.

8. Click Next.

   The Backup Content page appears. On this page you can either configure rule criteria for automatically discovering instances to back up, or you can manually select an instance to back up.

9. If you proceed with Rule based discovery, do the following:

   1. From the Access node list, select an access node which runs the discovery job.

      Note

      All the access nodes must have VSA package installed for MySQL and cloud applications.

   2. Click Add.

      The Add rule group dialog box appears.

   3. To specify the type of Match rule, select all or any. The rules for the match are as follows:

      • all: All rules that you configure for the rule group must be satisfied for a database instance to be discovered.

      • any: Any rule that you define that is satisfied will result in the matching database being discovered.

   4. From the list of rule types, select the type of rule to create, and then specify the rule:

      • Instance name: Select instances based on their names. For example, to select instances that have a name that includes "east", enter Instance name | Contains | east.

      • Tag name: Select instances based on the names of tags that are assigned to them. Enter the tag name in the regiontag_name format. For example, to select instances in the eastern US Region that are for a department, enter Tag name | Equals | us-east-1department.

      • Tag value: Select instances based on the values of tags that are assigned to them. Enter the tag value in the regiontag_nametag_value format. For example, to select instances in the eastern US Region for the human resources department, enter Tag value | Equals | us-east-1departmentHR.

   5. Click Save.

   6. Click Preview to see the instances that you selected for the group.

   7. From the Credential list, select a saved credential or add a new credential.

      Steps to add a new credential

      1. From the Credential Vault list, select a credential vault to store credentials for different types of accounts.

      2. In the Credential name box, enter a name for the credential.

      3. Under the Azure AD/AWS IAM Authentication section, enter the following details:

         • In the Username box, enter the user name to access the Azure Database for MySQL application.

         • In the Password box, enter the password to access the Azure Database for MySQL application.

           Note

           If you move the Azure AD/AWS IAM Authentication toggle to right, you only need to enter the user name detail.

      4. The SSL certificate toggle key is unselected by default. By moving the toggle key to right, you can perform the following actions:

         • In the SSL CA file field, provide the SSL CA file path on the proxy computer.

         • In the SSL Cert file field, provide the SSL certificate file path on the proxy computer.

         • In the SSL Key file field, provide the SSL key file path on the proxy computer.

      5. In the Description box, enter the details of the credential.

      6. Click Save.

10. If you proceed without rule based discovery, do the following:

    1. Instance name: Select instances based on their names.

    2. Under the Connection details section, from the Credential list, either select a saved credential or add a new credential.

    3. In the Maintenance DB box, type the name of the system database that is used as the maintenance database.

    4. In the Endpoint box, type the name of the endpoint to connect to the database instance.

11. Click Next.

    Tip

    For Azure Single servers, enter the user name in the syntax username@hostname.

12. On the Summary page, review the summary, and then click Finish.