Product terminology White list Allow access to the IP source of the cloud database instance. Read write separation The primary instance handles database write requests, while the read-only instance handles database read requests. Master node The node in the primary instance that provides users with read and write request services will automatically switch to the standby node when the primary instance fails, thus ensuring the high availability of the cloud database. Standby node The node in the primary instance is used to ensure service reliability. The standby node is synchronized with the primary node through asynchronous replication. The standby node is invisible to users. Data synchronization Real time data synchronization between two data sources. Data synchronization is applicable to local disaster recovery or remote disaster recovery scenarios. Backup Storage It is used to persist the underlying storage resources for database data or log backups. Database storage The underlying storage resource used to persist database data and logs. QPS Queries Per Second is a measure of how much traffic a specific query server handles in a specified time. Hot Backup Backup when the database is working normally. Cold backup Backup when the database is down or under maintenance. Database migration With business changes, databases need to be migrated from one environment to another. Such as migrating from the local IDC to the cloud, or from one cloud to another. Database account Before using the database, you need to create an account in the cloud database instance. The database account consists of lowercase letters, numbers, and underscores. It starts with a letter, ends with a letter, or ends with a number. The maximum length is 16 characters. Automatic backup The cloud database automatically backs up the backup set once a day. The cloud database supports setting custom backup cycles to fully meet users' different backup needs, thus reducing the burden of user self operation and maintenance. Manual backup ApsaraDB supports users to manually back up database instances. Logical backup Logical backup, also known as "export", is to export data from the database and save it in a file that can be parsed by MySQL. The file format is either SQL or text separated by some symbol. The logical backup file can only be used for logical recovery of the database, that is, data import, rather than physical recovery according to the original storage characteristics of the database. Physical backup The backup process of copying the original files that actually make up the database from one place to another. |
