Complete the Databases Guided Setup for Azure Table Storage

Updated

The Azure Table storage database guided setup takes you through the process of creating a server plan, adding a cloud instance, and then performing a test backup and restore.

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.

    If you already completed the guided setup, select Go to app from more options on the tile to go to the Instances page.

Create a Server Plan That You Can Use for Azure Table Storage

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

  1. On the Create server backup plan page, specify the settings for a server plan that you can use for the Azure Table storage.

Settings

Steps

Plan name

  1. Fill in the following plan information:

    1. Choose whether to create a new plan or use a base plan.

    2. If you selected Create a new plan, in the Plan name, enter a name for the server plan.

    3. If you selected Use existing base plan, specify the plan name and select a base plan.

Backup destinations

  1. Click Add copy.

    The Add copy 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.

    You can use the MRR cool storage class (Metallic Recovery Reserve) for creating secondary copies, but not for creating primary copies.

  4. To specify the start time for backups on a specific date and later, move the Backups On and After toggle key to the right.

  5. For Retention rules, enter the amount of time to retain the backups.

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

  7. Click Save.

  8. To add additional regions to the backup destination, move the Multi-region toggle key to the right, and then select the regions.

    You can also add more regions and associate the storage copy to the region.

RPO

  1. For Backup frequency, click Add.

    The Add backup frequency dialog box appears.

    1. From the Backup type list, select the backup type, and from the for list, select All agents or Databases.

    2. Specify the frequency of the backup.

    3. To specify the client time zone or to add exceptions, move the Advanced toggle key to the right.

      • From the time zone list, select the time zone according to which the backups must run.

      • To add exceptions when backups must not run, click Exceptions and add exceptions for any day or week of a month.

        These exceptions will repeat every month.

  2. For Backup window (if incremental and differential backups are supported for the workload), specify when you want incremental and differential backups to run.

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

Folders to back up

These settings do not apply to Azure Table Storage.

Snapshot options

These settings do not apply to Azure Table Storage.

Database options

These settings do not apply to Azure Table Storage.

Override restrictions

  • Leave the Allow plan to be overridden check box cleared.

  1. Click Save.

Create a Cloud Database Instance for Azure Table Storage

  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 Table storage.

  4. From the Cloud account list, select the Azure account that you want to use for the instance.

  5. If the cloud account that you selected uses an access node that includes only the Virtual Server package, then in the Access node list, select an access node that has both the Virtual Server and Cloud Apps packages installed.

  6. From the Plan list, select the server plan to use for the instance.

  7. To filter the content that is backed up, click Edit, and then select or clear the tables.

  8. Click Finish.

    Result: A table group is created for the instance. You can create more table groups to meet different backup requirements.