After you run a backup task, you can query the settings of backup parameters.
Procedure
Log on to the
systenant as therootuser.Execute specific statements to query the settings of backup parameters.
Query the backup destination.
Example:
obclient> SHOW PARAMETERS LIKE 'backup_dest'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: backup_dest data_type: NULL value: file:///data/nfs/backup info: backup dest section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor more information about how to set the backup destination, see Preparations for backup.
Query the backup zones.
Example:
obclient> SHOW PARAMETERS LIKE 'backup_zone'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: backup_zone data_type: NULL value: zone1 info: user suggest backup zone, format like z1,z2;z3,z4;z5 section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor information about how to set one or more backup zones, see Set backup_zone.
Query the concurrency of data writes to the file system during backup.
The file system writing concurrency during a backup plays a role in the backup speed and background resource consumption. A higher concurrency leads to more background resource consumption and higher backup efficiency.
Example:
obclient> SHOW PARAMETERS LIKE 'backup_concurrency'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: backup_concurrency data_type: NULL value: 1 info: backup concurrency limit. Range: [0, 100] in integer section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setQuery the backup settings specified by backup_dest_option.
obclient> SHOW PARAMETERS LIKE 'backup_dest_option'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: backup_dest_option data_type: NULL value: log_archive_checkpoint_interval=2m&recovery_window=7d&auto_delete_obsolete_backup=true&log_archive_piece_switch_interval=1d info: backup_dest_option section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor information about how to configure backup settings, see Preparations for backup.
View the secondary backup destination.
Example:
obclient> SHOW PARAMETERS LIKE 'backup_backup_dest'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: backup_backup_dest data_type: NULL value: file:///data/nfs/backup_backup info: backup backup dest section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor information about how to configure the secondary backup destination, see Preparations for secondary backup.
Query the secondary backup settings specified by backup_backup_dest_option.
Example:
obclient> SHOW PARAMETERS LIKE 'backup_backup_dest_option'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: backup_backup_dest_option data_type: NULL value: log_archive_checkpoint_interval=1h&recovery_window=14d&auto_delete_obsolete_backup=true info: backup_backup_dest_option section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor more information about how to configure secondary backup settings, see Preparations for secondary backup.
Query the log backup mode and compression algorithm.
Example:
obclient> SHOW PARAMETERS LIKE 'backup_log_archive_option'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: backup_log_archive_option data_type: NULL value: mandatory compression= lz4_1.0 info: backup log archive option, support MANDATORY/OPTIONAL, COMPRESSION section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor more information about how to set the log backup mode and compression algorithm, see Initiate a log backup.
Query the log archiving concurrency.
The log archiving concurrency plays a role in the log archiving speed and background resource consumption. A higher concurrency leads to more background resource consumption and higher log archiving efficiency.
Example:
obclient> SHOW PARAMETERS LIKE 'log_archive_concurrency'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: log_archive_concurrency data_type: NULL value: 0 info: concurrency for log_archive_sender and log_archive_spiterRange: [0, ] in integer section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor more information about the
log_archive_concurrencyparameter, see log_archive_concurrency.Query the maximum memory for log archiving on a single server.
Example:
obclient> SHOW PARAMETERS LIKE 'log_archive_batch_buffer_limit'\G *************************** 1. row *************************** zone: zone1 svr_type: observer svr_ip: 10.10.10.1 svr_port: 2882 name: log_archive_batch_buffer_limit data_type: NULL value: 1G info: batch buffer limit for log archive, capacity smaller than 1G only for mini mode, Range: [4M, max) section: OBSERVER scope: CLUSTER source: DEFAULT edit_level: DYNAMIC_EFFECTIVE 1 row in setFor more information about the
log_archive_batch_buffer_limitparameter, see log_archive_batch_buffer_limit.