After a backup is performed, you can view the settings of the data backup-related parameters.
View the data backup parameters of a user tenant in the sys tenant
Log in to the
systenant of the cluster as therootuser.Execute the following statements to query the parameter settings related to backup.
Query the current number of worker threads for high availability tasks with low priority, such as backup and backup cleanup.
Example:
obclient(root@sys)[(none)]> SHOW PARAMETERS LIKE '%ha_low_thread_score%'\GThe query result is as follows:
*************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 172.xx.xxx.xxx svr_port: 2882 name: ha_low_thread_score data_type: INT value: 0 info: the current work thread score of high availability low thread. Range: [0,100] in integer. Especially, 0 means default value section: OBSERVER scope: TENANT source: DEFAULT edit_level: DYNAMIC_EFFECTIVE default_value: 0 isdefault: 1 1 row in setThe tenant-level configuration item
ha_low_thread_scorespecifies the current number of worker threads for high availability tasks with low priority, such as backup and backup cleanup. The default value is0. If you find that the data backup task is running too slowly, you can appropriately increase the value of theha_low_thread_scoreconfiguration item. We recommend that you double the value each time. For more information about theha_low_thread_scoreconfiguration item, see ha_low_thread_score.The following example shows how to set the number of concurrent writes to the file system when performing a backup:
obclient(root@sys)[(none)]> ALTER SYSTEM SET ha_low_thread_score = 4 TENANT = mysql_tenant;In this example, the value of the
ha_low_thread_scoreconfiguration item is set to4, which specifies the number of worker threads for backup tasks in the tenant (mysql_tenant).Query the backup parameters of a tenant (excluding the source configuration).
The
oceanbase.CDB_OB_BACKUP_PARAMETERview records the backup parameters configured for all tenants in the current cluster.obclient(root@sys)[oceanbase]> SELECT * FROM oceanbase.CDB_OB_BACKUP_PARAMETER\GThe query result is as follows:
*************************** 1. row *************************** TENANT_ID: 1004 NAME: data_backup_dest VALUE: S3://oceanbase-test-bucket/backup/data/?host=xxx.aliyun-inc.com&access_id=xxx&access_key=xxx&delete_mode=delete&checksum_type=md5&enable_worm=true 1 row in setIn this example, the data backup path (
data_backup_dest) for the tenant withTENANT_IDof1004isS3://oceanbase-test-bucket/backup/data/?host=xxx.aliyun-inc.com&access_id=xxx&access_key=xxx, and its backup file cleanup mode (delete_mode) isdelete. Thedelete_modeparameter can take the following two values:deletemode: the cleanup mode is to directly delete the eligible backup files.In this mode, when you clean up backup files, the system directly deletes the files that meet the cleanup criteria.
taggingmode: the cleanup mode is to set tags for the eligible backup files. The backup files are retained.In this mode, when you clean up backup files, the system sets tags for the files that meet the cleanup criteria. The tag
keyis"delete_mode", and the tagvalueis"tagging", so that you can manage the lifecycle of these files on AWS S3 by using the tags.
In addition, in the parameters of the backup path for the tenant,
checksum_type=md5indicates that the MD5 algorithm is used to verify the integrity of backup files, andenable_worm=truespecifies that OceanBase AI Database performs write and delete operations on the path according to the WORM policy.View information related to the backup path of a tenant (including the source configuration).
The
CDB_OB_BACKUP_STORAGE_INFOview records information about the backup or archive paths for all tenants.obclient(root@sys)[oceanbase]> SELECT TENANT_ID, PATH, DEST_TYPE, EXTENSION, MAX_IOPS, MAX_BANDWIDTH, MAX_BANDWIDTH_DISPLAY FROM oceanbase.CDB_OB_BACKUP_STORAGE_INFO WHERE DEST_TYPE='backup_data';The query result is as follows:
+-----------+---------------------------------------------+-------------+-----------------------------------------------+----------+---------------+-----------------------+ | TENANT_ID | PATH | DEST_TYPE | EXTENSION | MAX_IOPS | MAX_BANDWIDTH | MAX_BANDWIDTH_DISPLAY | +-----------+---------------------------------------------+-------------+-----------------------------------------------+----------+---------------+-----------------------+ | 1004 | S3://oceanbase-test-bucket/backup/data | backup_data | checksum_type=md5&enable_worm=true&zone=zone1 | 1000 | 0 | UNLIMITED | +-----------+---------------------------------------------+-------------+-----------------------------------------------+----------+---------------+-----------------------+ 1 row in setIn the query result, for the tenant with ID
1004, the backup path isS3://oceanbase-test-bucket/backup/data. Thechecksum_type=md5indicates that the MD5 algorithm is used to verify the integrity of backup files, andenable_worm=truespecifies that OceanBase AI Database performs write and delete operations on the path according to the WORM policy. The source configuration iszone=zone1, which means that only the nodes inzone1can access the path. In terms of I/O throttling,MAX_IOPSis1000, which means that the current backup path allows at most about 1000 I/O requests per second.MAX_BANDWIDTH_DISPLAYisUNLIMITED, which means that the bandwidth is not limited.
View the data backup parameters of the current tenant in a user tenant
Log in to the database as a tenant administrator.
Note
The administrator user for a user tenant is the
rootuser.Execute the following statements to query the parameter settings related to backup.
Query the current number of worker threads for high availability tasks with low priority, such as backup and backup cleanup.
Example:
obclient(root@mysql001)[(none)]> SHOW PARAMETERS LIKE '%ha_low_thread_score%'\GThe query result is as follows:
*************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 172.xx.xxx.xxx svr_port: 2882 name: ha_low_thread_score data_type: INT value: 0 info: the current work thread score of high availability low thread. Range: [0,100] in integer. Especially, 0 means default value section: OBSERVER scope: TENANT source: DEFAULT edit_level: DYNAMIC_EFFECTIVE default_value: 0 isdefault: 1 1 row in setThe tenant-level configuration item
ha_low_thread_scorespecifies the current number of worker threads for high availability tasks with low priority, such as backup and backup cleanup. The default value is0. If you find that the data backup task is running too slowly, you can appropriately increase the value of theha_low_thread_scoreconfiguration item. We recommend that you double the value each time. For more information about theha_low_thread_scoreconfiguration item, see ha_low_thread_score.The following example shows how a user tenant sets the number of concurrent writes to the file system when performing a backup:
obclient(root@mysql001)[(none)]> ALTER SYSTEM SET ha_low_thread_score = 4;In this example, the value of the
ha_low_thread_scoreconfiguration item is set to4, which specifies the number of worker threads for backup tasks in the current tenant.Query the backup parameters of the current tenant (excluding the source configuration).
A user tenant can query the backup parameters configured for the current tenant by using the
oceanbase.DBA_OB_BACKUP_PARAMETERview.obclient(root@mysql001)[oceanbase]> SELECT * FROM oceanbase.DBA_OB_BACKUP_PARAMETER;The query result is as follows:
+------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ | NAME | VALUE | +------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ | data_backup_dest | S3://oceanbase-test-bucket/backup/data/?host=xxx.aliyun-inc.com&access_id=xxx&access_key=xxx&delete_mode=delete&checksum_type=md5&enable_worm=true | +------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in setAccording to the query result, in the parameters of the backup path for the current tenant,
checksum_type=md5indicates that the MD5 algorithm is used to verify the integrity of backup files, andenable_worm=truespecifies that OceanBase AI Database performs write and delete operations on the path according to the WORM policy.View information related to the backup path of the current tenant (including the source configuration).
A user tenant can query the information about the backup or archive paths of the current tenant by using the
oceanbase.DBA_OB_BACKUP_STORAGE_INFOview.obclient(root@mysql001)[oceanbase]> SELECT PATH, DEST_TYPE, EXTENSION, MAX_IOPS, MAX_BANDWIDTH, MAX_BANDWIDTH_DISPLAY FROM oceanbase.DBA_OB_BACKUP_STORAGE_INFO WHERE DEST_TYPE='backup_data';The query result is as follows:
+---------------------------------------------+-------------+-----------------------------------------------+----------+---------------+-----------------------+ | PATH | DEST_TYPE | EXTENSION | MAX_IOPS | MAX_BANDWIDTH | MAX_BANDWIDTH_DISPLAY | +---------------------------------------------+-------------+-----------------------------------------------+----------+---------------+-----------------------+ | S3://oceanbase-test-bucket/backup/data | backup_data | checksum_type=md5&enable_worm=true&zone=zone1 | 1000 | 0 | UNLIMITED | +---------------------------------------------+-------------+-----------------------------------------------+----------+---------------+-----------------------+ 1 row in setIn the query result, the backup path of the current tenant is
S3://oceanbase-test-bucket/backup/data. Thechecksum_type=md5indicates that the MD5 algorithm is used to verify the integrity of backup files, andenable_worm=truespecifies that OceanBase AI Database performs write and delete operations on the path according to the WORM policy. The source configuration iszone=zone1, which means that only the nodes inzone1can access the path. In terms of I/O throttling,MAX_IOPSis1000, which means that the current backup path allows at most about 1000 I/O requests per second.MAX_BANDWIDTH_DISPLAYisUNLIMITED, which means that the bandwidth is not limited.