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 DEBIAN

grass-mesql

grass-mesql(1grass)						Grass User's Manual					       grass-mesql(1grass)

NAME

       grass-mesql - MySQL embedded driver

       MySQL  embedded	driver	MySQL  embedded  driver  in GRASS MySQL database driver in GRASS enables GRASS to store vector attributes in MySQL
       embedded database without necessity to run MySQL server.

Driver and database name
       GRASS modules require 2 parameters to connect to a database.  Those parameters are 'driver' and 'database'. For MySQL embedded  driver  the
       parameter  'driver'  should  be	set  to value 'mesql'.	The parameter 'database' is a full path to the directory where database tables are
       stored. The best place is a directory in the mapset. The directory must be created before use of the driver. In the name of database it	is
       possible to use 3 variables:

		      $GISDBASE - path to current GISBASE

		      $LOCATION_NAME - name of current location

		      $MAPSET - name of current mapset

       Examples of connection parameters:
	 db.connect driver=mesql database='$GISDBASE/$LOCATION_NAME/$MAPSET/mysql'
	 db.connect driver=mesql database=/home/user1/db

Data types, indexes
       For more informations about supported data types and indexes see the documentation for MySQL (mysql) driver

Database type
       Because	database  closing  was	found  very  slow if InnoDB was used, the InnoDB storage is disabled by default (hardcoded '--skip-innodb'
       server option).

Note
       The embedded server is started with hardcoded '--bootstrap' option to avoid warning about missing mysql.time_zone_leap_second  table.  This
       can be fixed in future.

SEE ALSO

	db.connect, SQL support in GRASS GIS

Credits
       Development of the driver was sponsored by Faunalia (Italy) as part of a project for ATAC.

AUTHOR

       Radim Blazek

       Last changed: $Date: 2011-02-07 18:59:50 +0100 (Mon, 07 Feb 2011) $
       Help Index

GRASS 6.4.2														       grass-mesql(1grass)