Before backing up a particular database server for the first time, gather some information and use it to make some planning decisions, as outlined in the following table.
Table 4.1 Information Needed to Back Up a Database
Information to Gather | Where to Find It | How to Use It |
|---|---|---|
Path to MySQL configuration file | Default system locations, hardcoded application default locations, or from the | The preferred way to convey database configuration information tomysqlbackup is to use the |
MySQL port | MySQL configuration file ormysqld startup script. | Used to connect to the database instance during backup operations. Specified via the |
Path to MySQL data directory | MySQL configuration file ormysqld startup script. | Used to retrieve files from the database instance during backup operations, and to copy files back to the database instance during restore operations. Automatically retrieved from database connection. |
ID and password of privileged MySQL user | You record this during installation of your own databases, or get it from the DBA when backing up databases you do not own. | Specified via the |
Path under which to store backup data or metadata, temporarily or permanently | You choose this. SeeSection 4.1.3, “Designate a Location for the Backup Directory” for details. | In general, this directory has to be empty formysqlbackup to write data into it. |
Owner and permission information for backed-up files (for Linux, Unix, and OS X systems) | In the MySQL data directory. | If you perform the backup and restore using a different OS user than the one who runs the server, this information might become important. SeeSection 4.2.1, “OS User for Running mysqlbackup” for details. |
Rate at which redo data is generated | Calculated from the values of the InnoDBlogical sequence number at different points in time. Use the technique explained inCreating Incremental Backups Using Only the Redo Log. | Only needed if you perform incremental backups using the |