On Feb 13, 2008, at 3:06 PM, Wanda Prather wrote:

In that case mysql provides a perl script you can implement that
will create
copies of the mysql files in another directory, then TSM can back up
those
flat files.

This is not true when using InnoDB, the transactional version of MySQL
storage.

I have a relatively large MySQL server that we back up to TSM.  I
originally was using adsmpipe but the pipe would randomly shut down
and break my backups.

The current regime is that we have mysqlbackup generate a SQL dump of
all databases on the 1st and 15th of every month, which is stored on
disk.  TSM picks that up as part of the backup.  In addition, we run
with MySQL binary logging enabled, and back up the log files nightly.
We've restored from this as a point-in-time SQL restore (recover the
last mysqlbackup dump, then replay the binary log up to the mistaken
transaction).

I'm disappointed with a lack of a real TSM MySQL client; I think the
arguments that MySQL is a mediocre database are long in the tooth, and
there are a lot of real commercial operations that are backed by
MySQL.  No it's not Oracle.  But it is sufficient for 80% of
applications.

--Jim