HP OSMS Blueprint: Database Server on HP Server Platforms with MySQL and RHEL5

NOTE: To identify the type of storage engine used for a particular table, use the following
command:
mysql> show table status from osmdb like 'customer';
4. Restart the slave replication thread after the database has been dumped by entering the
following command:
mysql> START SLAVE SQL_THREAD;
To Integrate Data Protector
1. Add the secondary storage, which is used to hold the backup data, as a device in Data
Protector.
2. Add a Blank Filesystem Backup on the Data Protector cell server, and then back up the
following data to the secondary storage device:
• The data file (/tmp/customer.sql) that you dumped in step 2
• The binary log files located in the /var/lib/mysql directory on the slave server
• The relay-log.info and master.info files located in the /var/lib/mysql
directory on the slave server
Figure 9 Back Up the Slave Server
3. Start the backup either manually or at a scheduled time.
4. After the backup is complete, restart replication between the master server and slave servers.
For an incremental backup of a MySQL server, the dumped data file needs to be backed up in
its entirety only once, the first time a backup is run. In all subsequent backup jobs, only the binary
log files, master.info and relay-log.info, should be backed up. Restoration of all data in
the event of a disaster is achieved by first restoring the full data backup, and then restoring all
the binary log updates, which are used to recover the database to the point of the binary log
flush.
Backing Up Your Database 31