You can use Hybrid Backup Recovery (HBR) to back up SQL Server databases deployed in a local Internet data center (IDC). This topic describes the preparations that you need to make before backing up data.

Background

When you use HBR to back up SQL Server databases deployed in local IDCs, note the following points:

  • Currently, you can use HBR to back up and restore SQL Server databases deployed in local IDCs in the following regions: China (Beijing), China (Shanghai), China (Shenzhen), China (Hangzhou), China (Zhangjiakou), China (Hohhot), China (Hong Kong), Singapore, US (Silicon Valley), Indonesia (Jakarta), Malaysia (Kuala Lumpur), Australia (Sydney), Germany (Frankfurt) and Japan (Tokyo). The services will be available in more regions soon.
  • Make sure that .NET Framework 4.5 or later is installed.
  • HBR supports the following SQL Server versions: SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017. For more information, seeLimits.
  • You can also back up SQL Server databases deployed on Alibaba Cloud Elastic Compute Service (ECS) instances. For more information, seeBack up SQL Server databases in ECS.
  • SQL Server databases cannot be installed in a file system where compression is enabled. For more information about limits on SQL Server installation, seeFile Locations for Default and Named Instances of SQL Server.

(Recommended) Prepare an AccessKey for a RAM user

Resource Access Management (RAM) is an Alibaba Cloud service that helps you manage user identities and access to your cloud resources. RAM allows you to create and manage multiple identities under an Alibaba Cloud account, and grant diverse permissions to a single identity or a group of identities. In this way, you can authorize different identities to access different Alibaba Cloud resources.

An AccessKey is required when you activate a backup client. If the AccessKey of an Alibaba Cloud account is leaked, all cloud resources under the account may be exposed to risk. Therefore, we recommend that you use the AccessKey of a RAM user to activate backup clients. Before you back up data, make sure that a RAM user is created and an AccessKey is created for the RAM user. For more information, seeCreate a RAM userandCreate an AccessKey pair for a RAM user.

Step 1: Register an SQL Server instance

After an SQL Server instance is registered, you can install a file backup client on each node of the SQL Server instance. You can use the file backup client to run backup and restore jobs. To register an SQL Server instance, follow these steps:

  1. Log on to theHBR console.
  2. Select the region where you want to store the backup data.
  3. In the left-side navigation pane, chooseBackup & Recovery > On-Premises Backup. On the On-Premises Backup page, selectSQL Server.
  4. On theSQL Server Instancetab that appears, clickRegister SQL Server Instancein the upper-right corner.
  5. In theRegister SQL Server Instancepane that appears, set the parameters as described in the following steps.
    • Configure an instance
      1. Set the parameters for configuring an instance, as described in the following table.
        Parameter Description
        Vault Name The name of the backup vault. A backup vault is a repository used by HBR to store backup data in the cloud. You can back up data from multiple backup clients to the same vault. Backup vaults reside in different regions. You can only select or create backup vaults in the current region.
        • If you have created backup vaults, set Backup Vault Config toSelect Vaultand select a backup vault from theVault Namedrop-down list.
        • If you have not created any backup vaults, set Backup Vault Config toCreate Vaultand setVault Nameto create a backup vault. The vault name can be a maximum of 64 characters in length.
        Server Name The server name and instance name of the SQL Server instance, in the format of Server name\Instance name. For example, you can enter localhost\MSSQLSERVER. You do not need to enter the instance name for a default instance.
        Authentication The authentication method used to connect to the SQL Server instance.
        • If you selectWindows Login, enter the username used to log on to the SQL Server instance in Windows in theWindows Login Namefield.
        • If you selectSQL Server Login, enter the username used to log on to the SQL Server instance in theSQL Server Userfield.
        Password The password used to log on to the SQL Server instance. Set the password based on the selected authentication method.
      2. ClickNext.
    • Create a client
      1. Set the parameters for creating a file backup client, as described in the following table.
        Table 1. Create a client
        Parameter Description
        Source Client
        • New Client: Select this option if no file backup client is installed and activated on the server from which you want to back up data.
        • Select Activated Client: Select this option if a file backup client has been installed and activated on the server from which you want to back up data. Then, select the file backup client that has been activated.
        Client Name The name of the backup client. The client name can be a maximum of 64 characters in length.
        Software Platform The operating system that is running on the server from which you want to back up data. Valid values:
        • Window 32-bit
        • Window 64-bit
        Network Type
        • Virtual Private Cloud (VPC): Select this option when the server from which you want to back up data resides in a VPC and is in the same region as the backup vault.
        • Public Network: Select this option when VPCs are unavailable.
        Transmit Data On HTTPS Specifies whether to enable HTTPS-encrypted transmission. Your data will be encrypted and stored in a backup vault. You can choose whether to use HTTPS to encrypt the data during transmission. Note that using HTTPS will degrade the data transmission performance. If you modify this configuration, the modification takes effect when the next backup or restore job starts.
      2. ClickCreate. TheDownload Clientbutton appears.
    • Install the client
      1. ClickDownload Client.
      2. Save the downloaded installation package of the file backup client.
      3. Log on to the server where SQL Server is installed and install the file backup client.
        Note Make sure that enough space is available in the installation directory because operational logs and an executable file are all stored in the installation directory.
    • Activate the client
      1. After the file backup client is installed, activate the client. Go to the HBR console. In the Create Client step of theRegister SQL Server Instancepane, clickNextand set the parameters as described in the following table to activate the client.
        Parameter Description
        Client IP Address The IP address of the server or virtual machine where the file backup client is installed.
        Note The IP address must be reachable from your current browser.
        AccessKey Id The AccessKey ID and AccessKey secret of the RAM user used to access HBR. You can obtain the AccessKey ID and AccessKey secret of a RAM user under your Alibaba Cloud account for which HBR is activated. For more information, seeCreate an AccessKey for a RAM user.
        AccessKey Secret
        Create Client Password The password used to log on to the file backup client. The password must be at least six characters in length.
      2. ClickActivate Client.
        • After the file backup client is installed and activated, you can view the installation status of the client on the node of the SQL Server instance. To delete the file backup client from the node, find the target client and clickDeletein the Actions column.
        • After the SQL Server instance is registered, you can view the registration information and status of the instance on theSQL Server Instancetab of theOn-Premises Backuppage. To modify the connection information of the instance, chooseMore > Edit Instancein the Actions column.

Step 2: Install a client on a new node

If a node is added to the SQL Server cluster after the SQL Server instance is registered, you can install a file backup client on the new node. To install a file backup client, follow these steps:

Note Currently, you can add only one backup client for an SQL Server instance.
  1. On the SQL Server Instance tab, find the target SQL Server instance. Click the instance name or ID, or chooseMore > View Detailsin theActionscolumn. The SQL Server Instance page appears.
  2. On theSQL Server Instancepage, click theClienttab. On this tab, clickCreate Clientin the upper-right corner.
  3. In the Create Client pane that appears, set parameters as required and clickCreate. TheDownload Clientbutton appears. For more information about the parameters, see the table inCreate a client.
  4. If the installation package of a file backup client is not downloaded to the target node, copy the downloaded installation package to the target node and install the client.
  5. Log on to the HBR console and find the client. ChooseMore > Activate Clientin the Actions column. In the pane that appears, set parameters as required. For more information about the parameters, see the table inActivate the client.
  6. ClickActivate Clientto activate the client on the new node.

Step 3: Create a database group to be backed up

Before you back up data, you must group databases by backup plan. To create a database group, follow these steps:

Note If you want to back up a database separately, create a group exclusively for this database.
  1. Log on to theHBR console.
  2. In the left-side navigation pane, chooseBackup & Recovery > On-Premises Backup. On the On-Premises Backup page, selectSQL Server.
  3. On the page that appears, click theDatabase Grouptab. On the Database Group tab, clickCreate Database Groupin the upper-right corner.
  4. In theCreate Database Grouppane that appears, setGroup NameandDescription. Then, select one or more databases and add them to the group.
  5. ClickOK.

(Recommended) Limit the memory usage for an SQL Server instance

By default, SQL Server instances occupy as much system memory as possible. This may affect normal backup. Therefore, we recommend that you follow these steps to limit the memory usage of an SQL Server instance:

  1. Start SQL Server Management Studio and connect to the target SQL Server instance.
  2. Right-click the instance name and selectProperties.
  3. In the dialog box that appears, clickMemoryin the left-side navigation pane. On the Memory tab, setMaximum server memory.
    Note We recommend that you reserve at least 2 GB memory for backup and other system services. For example, if the system memory is 16 GB, the recommended value of Maximum server memory is14336for the SQL Server instance.