The sandbox feature provided by Database Backup (DBS) allows you to create new databases from backup sets and make your backup data available in seconds. This means your backup data achieves a recovery time objective (RTO) of a few seconds. Read and write operations performed within multiple sandbox instances are isolated between sandbox instances and do not affect source databases. This topic describes how to use the DBS sandbox feature to create and use sandbox instances.

Prerequisites

Background information

The DBS sandbox feature uses data deduplication and storage virtualization to solve the problems of increasing storage and use costs of traditional database backup services. Data deduplication and incremental merge allow you to keep full backup data available on the server. Storage virtualization can provide replicas of full backup data for read and write operations without the need to first copy data. For more information about the benefits, scenarios, billing, and limits of the sandbox feature, see Overview.

Procedure

To use the DBS sandbox feature, perform the following operations:
  1. Step 1: Enable the sandbox feature.
  2. Step 2: Create a sandbox instance.
  3. Step 3: Connect to a sandbox instance.
    Note Read and write operations performed within sandbox instances do not affect source databases. You can perform a variety of operations in sandbox instances, such as analysis, testing, verification, and emergency disaster recovery.

Step 1: Enable the sandbox feature

  1. Log on to the DBS console.
  2. In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
    Select a region
  3. On the Backup Schedules page, click Manage in the Actions column corresponding to a backup schedule.
  4. On the Configure Task page, click Set sandbox function in the Task Running Information section.
  5. In the Set sandbox function dialog box, enable Sandbox function.
  6. Configure the following parameters.
    Set sandbox function dialog box
    Note
    • Pay mode: the billing method of the sandbox feature. Only Commercial Capacity Edition is supported. For more information, see DBS sandbox fees.
    • Retention days: the retention period of sandbox instances. Unit: days. Default value: 7.
  7. Click OK.
    After you enable the sandbox feature, the Sandbox instance time range parameter is automatically set to Data preparing. Sandbox data being preparedThe following table describes the values of the Sandbox instance time range parameter.
    Sandbox status Description
    Sandbox feature disabled The Sandbox instance time range parameter is automatically set to Unopened.
    Preparation after you enable the sandbox feature The Sandbox instance time range parameter is automatically set to Data preparing.
    Preparation completed The Sandbox instance time range parameter is automatically set to a time range during which sandbox instances can be created.
    Note The displayed time range is within the start time of the earliest backup set and the end time of the latest backup set.

Step 2: Create a sandbox instance

  1. Log on to the DBS console.
  2. In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
  3. On the Backup Schedules page, click Manage in the Actions column corresponding to a backup schedule.
  4. On the Configure Task page, click Create a sandbox instance in the upper-right corner.
  5. On the Create a sandbox instance task page, configure the following parameters.
    Create a sandbox instance task
    Section Parameter Description
    N/A Task Name The name of the restoration task. DBS generates a task name. We recommend that you set a descriptive name that makes it easy to identify. Task names do not have to be unique.
    Set Time Restored To Time Range Available to Restore The time range available to restore the source instance. DBS displays the available time range.
    Restore To The point in time to which you want to restore the source instance. The value must be within the time range that is specified by the Time Range Available to Restore parameter.
    Sandbox instance information settings DB InstanceClass The specifications of the instance to be created. The following specifications are supported:
    • 1 CPU core and 1 GB of memory
    • 1 CPU core and 2 GB of memory
    • 2 CPU cores and 4 GB of memory
    • 2 CPU cores and 8 GB of memory
    • 4 CPU cores and 8 GB of memory
    • 4 CPU cores and 16 GB of memory
    • 8 CPU cores and 32 GB of memory

    For more information about sandbox instance fees of different specifications, see Sandbox instance fees.

    Instance Region The region where the sandbox instance is deployed.
    Peer VPC The VPC to which the sandbox instance belongs.
    Peer VSwitch The vSwitch to which the sandbox instance belongs.
  6. Click Recover immediately.
    The system performs prechecks and goes to the Sandbox Instance Tasks page.

Step 3: Connect to a sandbox instance

You can obtain the endpoint of the sandbox instance in the DBS console and connect to the endpoint by using the corresponding database client. You can also connect to the sandbox instance by using Data Management (DMS) or Database Autonomy Service (DAS). For more information, see Data management and What is DAS?

  1. Log on to the DBS console.
  2. In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
  3. On the Backup Schedules page, click Manage in the Actions column corresponding to a backup schedule.
  4. In the left-side navigation pane, click Sandbox tasks. On the page that appears, view the endpoint of the sandbox instance.
    Sandbox endpoint
  5. Connect to the sandbox instance from your client.

    You can obtain the endpoint of the sandbox instance in the DBS console and connect to the endpoint by using the corresponding database client. You can also connect to the sandbox instance by using DMS or DAS. For more information, see Data management and What is DAS?

    Note
    • The client that you use to connect to the sandbox instance, such as an ECS instance, must be deployed in the same VPC as the sandbox instance.
    • The account, password, and all configurations of the sandbox instance must be consistent with those of the source database.