Complete the Databases Guided Setup for Azure SQL Managed Instance

The Databases guided setup guides you through creating a server plan and adding a SQL database server.

Go to the Databases Guided Setup

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

    The Welcome page appears.

  2. On the Protect tab, click the Databases tile.

    The Databases guided setup appears.

Create a Server Plan That You Can Use for the Azure SQL Managed Instances

The server plan defines how often the software backs up the database and the log files, and where it stores the backups.

If you already have a server plan that you can use, you can skip this step.

Before You Begin

To create a server plan, you must have the Plan Creator Role assigned to your user account.

Procedure

  1. On the Create server backup plan page, click Create a new plan, and then specify the settings for a server plan that you can use for the SQL Server instance.

  2. Settings

    Steps

    Plan name

    1. Enter a name for the server plan.

    Click Next.

    Backup destinations

    1. Click Add.

      The Add backup destination dialog box appears.

    2. In Name, enter a name for the backup destination.

    3. From the Storage list, select the storage to use for the backups.

      If you selected storage that uses Distributed Storages, the Optimize for instant clone toggle key appears.

      By default, this setting is turned on to allow the associated Distributed Storage to optimize backups for clones, using Copy Data Management. To turn off the setting, move the Optimize for instant clone toggle key to the left.

      The setting does not apply to Hyperscale solutions that use Distributed Storage.

    4. For Retention period, enter the amount of time to retain the backups.

    5. To specify additional backups, such as weekly full backups, move the Extended retention rules toggle key to the right, and then add rules.

    6. Click Save.

    RPO

    1. For Backup, specify how often and when to run incremental backups.

    2. To run full backups, move the Add full backup toggle key to the right, and then specify how often and when to run full backups.

    3. For Backup window, specify when you want incremental backups to run.

    4. For Full backup window, specify when you want full backups to run.

    Folders to back up

    1. To back up only some content, in Content to back up, enter the content to back up.

      By default, all content is backed up.

    2. To exclude folders or files from the backup, in Exclude - files/folders/patterns, enter the content to exclude.

    3. Specify whether to include the system state in backups:

      • To include the system state in all backups, select the Back up system state check box.

      • To include the system state only in full backups, select the Back up system state check box and the Only with full backup check box.

      • To use VSS (Volume Snapshot Service, also called Shadow Copy) to back up the system state, select the Use VSS for system state check box.

    Snapshot options

    1. Specify how to retain snapshots:

      • To specify a number of jobs to retain on a snapshot copy, select Number of snap recovery points, and then enter the number of jobs to retain.

      • To specify a retention period, select Retention period, and then enter the amount of time to retain the jobs.

    2. If you don't want to create backup copies, move the Enable backup copy toggle key to the left to turn it off.

    3. For Backup copy frequency, enter how often to run backup copy jobs.

    Database options

    1. For Log backup RPO, enter how often to run log backups.

    2. To use the disk cache of the logs to the MediaAgent for backups, do the following:

      1. Move the Use disk cache for log backups toggle key to the right.

      2. For Commit every, enter how often to commit the logs to the CommServe computer.

        Disk caching of database logs applies to the following agents: Informix, Microsoft SQL Server on Windows, Oracle, Oracle RAC, and SAP HANA.

    Override restrictions

    Leave the Allow plan to be overridden check box cleared.

  3. Click Save.

Add a Database Server for Azure SQL Managed Instance

  1. On the Add database servers page, from the Application type list, select Cloud DB.

  2. From the Select vendor list, select Microsoft Azure.

  3. From the Database service list, select SQL server.

  4. Beside Cloud account, click Add.

    The Add cloud account dialog box appears.

  5. In the Name box, enter a name for the new cloud account.

  6. To connect to the Azure account using managed identities, move the Connect using managed identities for Azure resources toggle key to the right.

    For more information about setting up managed identities for Azure, see Setting up Managed Identity Authentication for Azure Resource Manager.

  7. In the Subscription ID, Tenant ID, Application ID, and Application password boxes, enter the details that you need to access data on the Azure cloud.

    For instructions about accessing this information from the Azure portal, see SQL Server Azure Cloud Connection Properties.

    Note

    If you enabled connecting to the Azure account using managed identities, you need only the subscription ID.

  8. From the Access nodes list, select the access nodes to use for the managed instance.

    You can add multiple access nodes to discover instances and databases. The Commvault software uses only the first proxy server in the list.

  9. Under Connection details, enter the following information:

    1. In the Storage Connection String box, enter the string that you use to access data in the Azure storage account.

    2. In the User name, Password, and Confirm password boxes, enter the credentials of a Windows user account that has permission to perform all operations, including backup, restore, and browse operations.

  10. Click Save.

Loading...