Zmanda hooks Tivoli cop into MySQL
Open source backup glue
Open source vendor Zmanda is adding hooks into its MySQL database backup software for shops using IBM's Tivoli Storage Manager to mastermind the policies.
The company on Monday unfurled a new feature for Zmanda Recovery Manager called — get ready for some unwieldily precision here —Tivoli Storage Manager Option for Zmanda Recovery Manager for MySQL.
Let's parse that out: Zmanda Recovery Manger (ZRM) is a Perl-based utility that does backup and recovery of live MySQL databases to on-premise storage or Amazon's S3 cloud service.
Zmanda's new ZRM-TSM option lets users have their MySQL data protection policies managed by Tivoli Storage Manager.
"If an IBM shop running Tivoli management software wants to integrate MySQL into their infrastructure, that has not been very easy because Tivoli doesn't support MySQL," Zmanda's CEO, Chander Kant, explains to El Reg. "We are filling that gap."
Kant told us that the Tivoli option comes after nine months of development and testing at the behest of its customers — in particular, one key retailer (who he couldnbame) that essentially funded the software's creation by paying for an early version of the product. TRM-TSM also earned the "Ready for IBM Tivoli" software validation seal over at Big Blue.
The option lets admins schedule full and incremental backups of MySQL, based on system resources and backup policies using either the schedule for TSM or ZRM. It supports all MySQL Storage Engines, including InnoDB and MyISAM, according to Zmanda.
Kant said he expects the typical ZRM-TSM will be mid-sized to enterprise shops getting their feet wet with web applications.
"Organizations who are running IBM hardware and software for their data center operations are now bringing quote unquote enterprise 2.0-style applications inside the data center, which are typical powered by MySQL," he said.
Kant added that after tackling Zmanda's Tivoli-control option, the company is next considering making similar ties to Symantec or HP Data Center.
ZRM-TSM requires a subscription for ZRM server (ranging from $300 to $750 per MySQL server annually). Adding the option itself to ZRM 3.1 costs $1000 per Tivoli server annually for standard support or $1500 for premium. A subscription comparison chart is viewable here. ®
if a shop is running "IBM hardware and software", wouldn't they likely be using some version of a real database like, oh I dunno, maybe DB/2, as opposed to MySQL? I mean, I like MySQL for light to medium stuff, but if I've got a room full of IBM iron, well, it's gonna be DB/2.
follow these instructions: http://www.redbooks.ibm.com/abstracts/redp3980.html?Open
I've not personally tried it, your mileage may vary etc.