Re: MySQL Administrator Backup Issue with InnoDB

Alfredo Kengi Kojima <[email protected]>
Newsgroups gmane.comp.db.mysql.mycc
Message-ID <[email protected]>
If you use the Single Transaction option, the previous method is going to 
be used.

-- 
Alfredo Kojima, GUI Developer
MySQL AB, www.mysql.com
Buenos Aires, Argentina

Are you MySQL certified?  www.mysql.com/certification

On Thu, 28 Apr 2005, Steve Crockett wrote:

>
>
> I'm not sure what I might be missing here, but I'm seeking advice on 
> resolving an issue I'm having with backups using MySQL Administrator 1.0.20 
> on a MySQL 4.0.20 DB...
>
> It appears to me that with Administrator 1.0.20 all the "backup execution 
> method" options that would appear to be appropriate for my use with my InnoDB 
> tables result in the invocation of the backup starting with "START 
> TRANSACTION WITH CONSISTENT SNAPSHOT".  The MySQL docs state that this 
> functionality didn't come about until MySQL 4.1.8.  As a result, my backup 
> don't run.
>
> Here are my thoughts on avenues I might pursue:
>
> Is this a bug or is this intended behavior (and running a version of MySQL 
> prior to 4.1.8 is my problem problem)?
>
> Are there backup options in MySQL Administrator that I can use to accomplish 
> a backup comparable to those I got before MySQL Administrator 1.0.20?  (I'm 
> currently attempting to use "Online with binlog pos" and "Complete backup".)
>
> Where can I download older versions of MySQL Administrator (they all worked 
> fine for me prior to 1.0.20)? 
> Thank you for your time and any advice would be appreciated.
>
> Steve
> ogretech @ yahoo.com
>
>
>
>
>
>
> -- 
> MySQL GUI Tools Mailing List
> For list archives: http://lists.mysql.com/gui-tools
> To unsubscribe:    http://lists.mysql.com/[email protected]
>

-- 
MySQL GUI Tools Mailing List
For list archives: http://lists.mysql.com/gui-tools
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.