2025-03-27
Renamed GaussDB(for MySQL) to TaurusDB.
Querying and Downloading Binlogs (OBT)
+Binlogs record all DDL and DML statements (except data query statements). You can download binlogs to a local PC for further analysis.
+This section describes how to enable binlog, and then query and download binlogs on the TaurusDB console.
+Billing
Binlogs are stored in OBS buckets.
+Prerequisites
- Binlog can only be enabled when the following conditions are met:
- If the kernel version of your DB instance is earlier than 2.0.45.230900, the value of log-bin must be ON. To view and modify the parameter value, see Modifying a Parameter Template.
- If the kernel version of your DB instance is 2.0.45.230900 or later, the value of rds_global_sql_log_bin must be ON.
- Before viewing and downloading binlogs, you need to enable binlog by referring to Enabling Binlog.
Constraints
To use binlogs, set the log-bin or rds_global_sql_log_bin parameter to ON.
+Enabling Binlog
- Log in to the management console.
- Click
in the upper left corner and select a region and a project. - Click Service List. Under Databases, click TaurusDB.
- On the Instances page, click the instance name.
- In the navigation pane, choose Logs.
- Click the Binlog tab.
- Click Configure Binlog. In the displayed dialog box, enable Binlog and set Retention Period.+
- The retention period ranges from 1 to 180 days.
- After binlog is disabled, the generated logs will be automatically deleted after the retention period expires. Deleted logs cannot be restored. Exercise caution when disabling binlog.
Querying and Downloading Binlogs
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click TaurusDB.
- On the Instances page, click the instance name.
- In the navigation pane, choose Logs.
- Click the Binlog tab. +
+
+
diff --git a/docs/taurusdb/umn/gaussdb_03_0016.html b/docs/taurusdb/umn/gaussdb_03_0016.html
index d130b9f60..45a5fd75b 100644
--- a/docs/taurusdb/umn/gaussdb_03_0016.html
+++ b/docs/taurusdb/umn/gaussdb_03_0016.html
@@ -12,6 +12,8 @@
+
+Parent topic: Logs
++
diff --git a/docs/taurusdb/umn/gaussdb_05_2265.html b/docs/taurusdb/umn/gaussdb_05_2265.html
index 9db40e5c7..ecc81eb09 100644
--- a/docs/taurusdb/umn/gaussdb_05_2265.html
+++ b/docs/taurusdb/umn/gaussdb_05_2265.html
@@ -1,11 +1,84 @@
-
-
+
+
+
+
+
Upgrading the Minor Version of a DB Instance
-Scenarios
You can manually upgrade minor versions of your instances to improve performance, add new functions, and fix bugs.
+Scenarios
You can upgrade the minor version of your DB instance to improve performance, optimize functions, and fix bugs.
Precautions
- The upgrade will cause the instance to reboot and interrupt services intermittently. To limit the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your applications support automatic reconnection.
- If an instance contains a large number of table partitions (more than 1 million), it may take more than 2 hours to reboot the instance.
- If the primary node and read replicas of an instance are deployed in the same AZ, a minor version upgrade will trigger a failover. If they are in different AZs, a minor version upgrade will trigger two failovers. A failover means that the system fails over to a read replica in case the primary node is unavailable.
- When you upgrade a minor version of an instance, minor versions of read replicas (if any) will also be upgraded automatically. Minor versions of read replicas cannot be upgraded separately. A minor version upgrade cannot be rolled back after the upgrade is complete.
- DDL operations, such as CREATE EVENT, DROP EVENT, and ALTER EVENT, are not allowed during a minor version upgrade.
Upgrade Scenarios
+Upgrade Information + |
+Upgrade Scenario + |
+Description + |
+
|---|---|---|
Kernel version + |
+There are three scenarios for upgrading a minor version based on different kernel versions: +
|
+
|
+
Upgrade time + |
+There are two ways to upgrade a minor version based on different upgrade times. +
|
+If the kernel version of your instance has potential risks or major defects, has expired, or has been brought offline, the system will notify you by SMS message or email and deliver an upgrade task during the maintenance window. + |
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click TaurusDB.
- On the Instances page, click the target instance to go to the Basic Information page.
- In the DB Instance Information area, click Upgrade in the DB Engine Version field.
- In the displayed dialog box, select a scheduled time and click OK.
Upon submission: The system upgrades the minor version immediately after your submission of the upgrade request. After the operation is complete, in the Task Center page, click Instant Tasks and view the information about the upgrade task.
+
Constraints
+Phase + |
+Constraint + |
+
|---|---|
Before the upgrade + |
+
|
+
During the upgrade + |
+
|
+
After the upgrade + |
+
|
+
Upgrading the Minor Version of a Single DB Instance
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click TaurusDB.
- On the Instances page, click the instance name to go to the Basic Information page.
- In the DB Instance Information area, click Upgrade in the Kernel Version field.
+
Alternatively, go to the Instances page and click Upgrade in the DB Engine Version column.
+ + - In the displayed dialog box, set Scheduled Time and click OK.
+
- Upon submission: The system upgrades the minor version immediately after your submission of the upgrade request. On the Task Center page, click Instant Tasks and view the task progress.
- In maintenance window: The system upgrades the minor version during the maintenance window you have specified. After the operation is complete, go to the Task Center page, click Scheduled Tasks, and view the upgrade task details.
- The system will automatically conduct a pre-upgrade check.
In the displayed dialog box, read the message carefully and click OK to proceed with the upgrade.
+ + - After the pre-upgrade is complete, the instance status becomes Pre-upgrade completed, which means no other operations are allowed. On the Basic Information page, click Upgrade in the Kernel Version field again. +
- In the displayed dialog box, click OK. The system will automatically conduct a pre-upgrade check. +
- Confirm the check results and click OK.
- After the upgrade is complete, the instance status becomes Kernel version upgrade to be confirmed, which means no other operations are allowed. To make the instance available again, go to the Basic Information page and click Apply Upgrade in the Kernel Version field. + +
Upgrading the Minor Versions of Multiple DB Instances at Once
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click TaurusDB.
- On the Instances page, select the desired DB instances and click Upgrade in the upper left corner of the list.
++
A maximum of 100 DB instances can be selected at once.
+ - In the displayed dialog box, confirm the information about the DB instances to be upgraded and set Scheduled Time.
+
- Upon submission: The system upgrades the minor version immediately after your submission of the upgrade request. On the Task Center page, click Instant Tasks and view the task progress.
- In maintenance window: The system upgrades the minor version during the maintenance window you have specified. After the operation is complete, go to the Task Center page, click Scheduled Tasks, and view the upgrade task details.
- Confirm the information, enter YES in the text box as prompted, and click OK.
- Wait for 2 to 5 minutes and check whether the upgrade has been started for the DB instance. If the upgrade has not been started, check whether the value of rds_global_sql_log_bin is ON and the value of binlog_expire_logs_seconds is at least 86400. If the parameters are not correctly configured, the upgrade cannot be performed.
- If the parameters are correctly configured but the upgrade has not started, it could be due to that the value of rds_sql_log_bin_inconsistent_count is not 0. Wait until this value becomes 0 before proceeding with the upgrade.