Preparations

An auxiliary tenant is required to restore a table. Therefore, before you restore a table, you must create a resource pool for the auxiliary tenant in the cluster where the destination tenant resides.

OceanBase Database restores a specified table from backup data to an existing tenant. The tenant can be the tenant where the original table resides, or a tenant in the same cluster as the tenant where the original table resides, or even a tenant in a different cluster.

The following figure shows the overall table restore process. Specifically, data is restored to the specified point in time in the auxiliary tenant, the specified table is imported from the auxiliary tenant to the destination tenant, and then the auxiliary tenant is cleared. Like an auxiliary instance in Oracle databases, an auxiliary tenant consumes additional computing and storage resources during table restore.

Procedure

1. Log in as the root user to the sys tenant of the cluster where the destination tenant resides.

2. Create a resource unit.

   Here is an example:

   obclient [(none)]> CREATE RESOURCE UNIT box_16c96g MAX_CPU 16, MEMORY_SIZE = '5G', MAX_IOPS 10240, MIN_IOPS=10240;
   

   For more information about how to create a resource unit, see Create a tenant.

3. Create a resource pool.

   We recommend that you create a resource pool that is homogeneous with the resource pool of the source tenant, namely has the same number of resource units as the resource pool of the source tenant.

   Here is an example:

   obclient [(none)]> CREATE RESOURCE POOL restore_pool unit = 'box_16c96g', unit_num = 1, zone_list = ('z1','z2','z3');
   

   For more information about how to create a resource pool, see Create a tenant.

What to do next

Perform table restore