Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Zmanda Recovery Manager for MySQL 2.0 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Zmanda Recovery Manager for MySQL 2.0 (Default branch)
# 1  
Old 04-05-2008
Zmanda Recovery Manager for MySQL 2.0 (Default branch)
Zmanda Recovery Manager (ZRM) for MySQL simplifieslife of a database administrator who needs an easyto use yet flexible and robust backup and recoverysolution for MySQL server. With ZRM for MySQL, youcan schedule full and incremental logical or rawbackups of your local or remote MySQL database,perform a backup that is the best match for yourstorage engine and your MySQL configuration, getencrypted and compressed backups, get emailnotification about the status of your backups(including RSS feeds), monitor and get backupreports, and recover a database easily to anypoint in time or to any particular transaction.License: GNU General Public License (GPL)Changes:
This release has support for Solaris and for backups using ZFS snapshots (in addition to LVM snapshots).Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. AIX

IBM FastT600 SAN - RAID 5 Storage Manager Client v08.33.G5.03 - Recovery?

To summarize the problem: The "IBM FastT Storage Manager Client v8" shows that our Disk Farm is arranged into 6 logical drives each in a RAID 5 configuration. This software also shows that 5 of the 6 logical drives (from Disk Farm) are in a error state: "Failed Logical Drive - Drive Failure".... (1 Reply)
Discussion started by: aix-olympics
1 Replies
Login or Register to Ask a Question

LEARN ABOUT SUSE

apache::session::lock::mysql

Session::Lock::MySQL(3) 				User Contributed Perl Documentation				   Session::Lock::MySQL(3)

NAME

       Apache::Session::Lock::MySQL - Provides mutual exclusion using MySQL

SYNOPSIS

	use Apache::Session::Lock::MySQL;

	my $locker = Apache::Session::Lock::MySQL->new();

	$locker->acquire_read_lock($ref);
	$locker->acquire_write_lock($ref);
	$locker->release_read_lock($ref);
	$locker->release_write_lock($ref);
	$locker->release_all_locks($ref);

DESCRIPTION

       Apache::Session::Lock::MySQL fulfills the locking interface of Apache::Session.	Mutual exclusion is achieved through the use of MySQL's
       GET_LOCK and RELEASE_LOCK functions.  MySQL does not support the notion of read and write locks, so this module only supports exclusive
       locks.  When you request a shared read lock, it is instead promoted to an exclusive write lock.

CONFIGURATION

       The module must know how to connect to your MySQL database to acquire locks.  You must provide a datasource name, a user name, and a
       password.  These options are passed in the usual Apache::Session style, and are very similar to the options for
       Apache::Session::Store::MySQL.  Example:

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockDataSource => 'dbi:mysql:database',
	    LockUserName   => 'database_user',
	    LockPassword   => 'K00l'
	};

       Instead, you may pass in an already opened DBI handle to your database.

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockHandle => $dbh
	};

AUTHOR

       This module was written by Jeffrey William Baker <jwbaker@acm.org>.

SEE ALSO

       Apache::Session

perl v5.12.1							    2008-01-08						   Session::Lock::MySQL(3)