Archive for December, 2006

Backup and recovery of the remote MySQL server with ZRM

Thursday, December 21st, 2006

We just published a technical document about what to consider for backup and recovery of the remote MySQL server, for example, when your online forums and wiki are located at managed hosting service provider.

For any database backup the primary considerations are the consistency of the backup and impact on users and applications. A backup of the remote MySQL, however, has extra challenges related to:

  • network usage
  • security, and
  • flexibility of recoverability of MySQL data to a different host.

We discuss the trade-offs to consider, and describe how to use Zmanda Recovery Manager (ZRM) for several common scenarios. For example, we provide HOWTO for a use case when you want to ensure security of backup data on the wire and at rest.

ZRM for MySQL 1.1.3 released

Tuesday, December 19th, 2006

Version 1.1.3 of Zmanda Recovery Manager (ZRM) for MySQL, an enterprise solution for backup and recovery of MySQL databases is available for download at Zmanda downloads page.

Changes since 1.1.2 release:
* Supports Ubuntu Edgy (6.10) release
* Works with MySQL enterprise 5.0
* User configuration for custom plugins
* Bug fixes

Documentation is available in ZRM for MySQL wiki. Please use forums to provide feedback on the release.

Thanks to all users for providing valuable feedback as well as finding bugs in earlier
releases :-)

Webinar on configuring Zmanda Recovery Manager [ZRM] for MySQL

Monday, December 11th, 2006

Last month, Paddy gave a great webinar on ZRM for MySQL. The playback is available as part of documentation in Zmanda Network, at no cost. You can register to Zmanda Network here. As a follow-up, we will be hosting a very hands on webinar on configuring ZRM for MySQL this Thursday, the 14th of Decemeber at 10.00 am PST. You can register for this webinar here.

Detecting malicious database activity

Wednesday, December 6th, 2006

I was talking to a customer yesterday and the customer was surprised that database backups can be used to detect malicious database activity from legitimate users and hackers.

ZRM for MySQL stores MySQL binary logs as part of the database backups. The binary logs provide a good audit trail of all database activity. ZRM for MySQL binary log parsing capability, usually used for selective point in time recovery, can also be used to detect malicious database activity using SQL inspection.

ZRM for MySQL plugin interface allows DBAs to write log parser plugin scripts to track the database activity that they are interested in. For example: the following script can be used to detect deletion of data from the PRODUCTS table in the database. This script prints all instances of deletion from PRODUCTS table.

@fields = split ( / \| /, $ARGV[0] );

my $SQL_VERB=”DELETE”;
my $TABLE_NAME=”PRODUCTS”;

if (($fields[3] == “Query”) && \
( $fields[4] =~ /$SQL_VERB *FROM.*`$TABLE_NAME`/ )) {
print “$fields[2] $fields[4]\n”;
}

The mysql-zrm command can be used to run the customized plugin script for all backups or a specific backup image. The following command looks for deletion from PRODUCTS table on a backup image dated Dec 5, 2006.

# mysql-zrm –action parse-binlogs \
–source-directory /var/lib/mysql-zrm/pricebook/20061205142103 \
–parse-binlogs-plugin /usr/share/mysql-zrm/plugins/detect_deletion.pl

The output of the command will contain valid deletions as well as malicious database deletions.

Yet another use for ZRM of MySQL.

Amanda in IPv6 environment

Friday, December 1st, 2006

Amanda now works in IPv6 environment. All IPv6 changes are part of latest Amanda community builds - 2.5.2alpha. We would like to get community’s help in testing Amanda 2.5.2 alpha in IPv6 and mixed IPv4 and IPv6 enviroments.

Source tar ball is available in Community builds page.

Changes required to run Amanda in IPv6 environment are documented in Amanda wiki.