Mysql White Paper Maintenance Guide

Mysql White Paper Maintenance Guide test recovery tools and processes, including restoring data from backup. Follow the minimum permission principle to keep the system clean and tidy. Use good names and Organization conventions to avoid confusion. For example, whether the server is used for development or for production environments, carefully arrange to upgrade the database server before the upgrade, use tools such as pt-upgrade in Percona Toolkit to carefully check the system's use of InnoDB and make appropriate configurations to ensure that InnoDB is the default storage engine. If the storage engine is disabled, the server cannot be started. Check whether the server configurations are correct. Use skip_name_resolve to disable DNS. The query cache is disabled unless it proves to be valid. Avoid using complex features, such as copy filtering and triggers unless necessary. Monitors important components and functions, especially key items such as disk space and RAID volume status, but also avoids false positives. Only when a problem occurs does it send an alarm. Record the server status and Performance Index as much as possible, and save as long as possible. Check the replication integrity on a regular basis. Set the slave database to read-only. Do not enable replication automatically. Audit query statements on a regular basis. Archive and clear unnecessary data. Reserve some space for the file system. In GNU/Linux, you can use the-m option to reserve space for the file system itself. You can also leave some free space in the LVM volume group. Alternatively, you can simply create a large empty file and delete it when the file system is full. Develop habits, evaluate and manage system changes, statuses, and performance information.