Re: Back-up Plan for Large Database

2010-12-28 Thread Brent Clark

On 27/12/2010 19:14, Wagner Bianchi wrote:

*You have no guarantee the data on the slave matches the master 100%.*
*
*
Try it with *semi-synchronous* replication.

Best regards.
--
Wagner Bianchi



Hiya

Thats why you nagios monitor replication of your slaves (I do master 
master replication monitoring)


I use mylvmbackup. Works like a bomb.

HTH
Brent

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



Re: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !

2010-12-28 Thread Yves Goergen
On 21.12.2010 11:27 CE(S)T, 杨涛涛 wrote:
 Maybe you should give a password to MySQL's root. And I think this note will
 disappear.

I would be extremely dumb not to set any password on MySQL's root
account at all! Of course (I hope I made that clear before) a password
has been set while installing the MySQL package. The point is that this
message is plain wrong and should be removed altogether until it works
as it claims.

-- 
Yves Goergen LonelyPixel nospam.l...@unclassified.de
Visit my web laboratory at http://beta.unclassified.de

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



Re: Another replication question

2010-12-28 Thread 杨涛涛
Ok, I'll not post any more!  Just reading!


David Yeung, In China, Beijing.
My First Blog:http://yueliangdao0608.cublog.cn
My Second Blog:http://yueliangdao0608.blog.51cto.com
My Msn: yueliangdao0...@gmail.com



在 2010年12月23日 下午8:14,Johan De Meersman vegiv...@tuxera.be写道:

 Glad to hear I'm not the only one annoyed :-) I've plonked him in the
 meantime.

 2010/12/23 Jorg W Young jorgwyoung...@gmail.comjorgwyoung%2...@gmail.com
 jorgwyoung%2...@gmail.com jorgwyoung%252...@gmail.com
 

  This guy has been saying nothing meaningful on this list, but
  advertise his blog everywhere.
  Just be shame. He should be kicked out from the list.
 
  Jorg.
 
  2010/12/23 杨涛涛 david.y...@actionsky.com:
   This way is very well,  but it has to do lots of human work.
   David Yeung, In China, Beijing.
   My First Blog:http://yueliangdao0608.cublog.cn
   My Second Blog:http://yueliangdao0608.blog.51cto.com
   My Msn: yueliangdao0...@gmail.com
  
  
 
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:http://lists.mysql.com/mysql?unsub=vegiv...@tuxera.be
 
 


 --
 Bier met grenadyn
 Is als mosterd by den wyn
 Sy die't drinkt, is eene kwezel
 Hy die't drinkt, is ras een ezel



Re: MySQL upgrade from 5.0.51a to 5.1.53

2010-12-28 Thread 杨涛涛
Hi all,
I did a upgrade from 5.0 to 5.1 yesterday. And I paste some of my steps
on the following.
1. Use mysqldump to dump all the data to the disk.
2. Backup all the data including mysql system files to a safe place.
3. Remove all the file related to mysql.
4. Install the new 5.1 version.
5. Import the exist  data into the new version.
   I don't know whether the above is fit for you or not.

David Yeung, In China, Beijing.
My Msn: yueliangdao0...@gmail.com



2010/11/30 Machiel Richards machi...@rdc.co.za

 Hi

   Thank you for the response, after reading a bit more about this, I
 suspect you are right.

From what I can gather I need to do the following in order to use
 this installation method:

-   create a full backup of the old database and put in a safe
 place.
-   create a backup of the my.cnf file in a seperate directory
 (in order to have access to the configuration to replicate details to
 new database config).
- use package-manager (apt-get in this case) to remove current
 version of MySQL that is running as well as all config files
 and /etc/mysql dir
- setup new mysql version using the tar file
- start the new server and restore the backup.
- run mysql_upgrade in order to ensure all tables are well as
 well as privilege tables.

Does this seem right to you guys?

 Machiel

 -Original Message-
 From: Johan De Meersman vegiv...@tuxera.be
 To: Machiel Richards machi...@rdc.co.za
 Cc: mysql mailing list mysql@lists.mysql.com
 Subject: Re: MySQL upgrade from 5.0.51a to 5.1.53
 Date: Tue, 30 Nov 2010 11:29:29 +0100

 I suspect you need to have the new version running instead of the old
 one, for the mysql_upgrade script to work.

 On Tue, Nov 30, 2010 at 11:23 AM, Machiel Richards machi...@rdc.co.za
 wrote:

HI Guys

 I found some info regarding a method to upgrade mysql
databases.

   Currently the version is at mysql-5.0.51a (as installed
via the
ubuntu-8.0.4 respository).

I downloaded the only version available from the web
(5.1.53)
that will work on ubuntu [except for source]. This is the binary
package
that need to be untarred into a directory and then the database
to be
initialized.

   The option was was looking at was to do the following
(according
to some reccomendations)


   - untar new version into seperate directory.
   -  keep the current version running.
   - cd to /path/to/new/directory/bin
   - ./mysql_upgrade -u root -p


   Running this I get a couple of errors / warnings
though and
I am hoping that someone can provide me with some answers or
otherwise a
better way to do the upgrade.


   Errors received:


   Enter password:
Looking for 'mysql' as: ./mysql
Looking for 'mysqlcheck' as: ./mysqlcheck
Running 'mysqlcheck' with connection arguments: '--port=3306'
'--socket=/var/run/mysqld/mysqld.sock'
Running 'mysqlcheck' with connection arguments: '--port=3306'
'--socket=/var/run/mysqld/mysqld.sock'
machiel.test1  OK
machiel.test2  OK
mysql.columns_priv OK
mysql.db   OK
mysql.eventOK
mysql.func OK
mysql.help_categoryOK
mysql.help_keyword OK
mysql.help_relationOK
mysql.help_topic   OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin   OK
mysql.proc OK
mysql.procs_priv   OK
mysql.servers  OK
mysql.tables_priv  OK
mysql.time_zoneOK
mysql.time_zone_leap_secondOK
mysql.time_zone_name   OK
mysql.time_zone_transition OK
mysql.time_zone_transition_typeOK
mysql.user OK
Running 'mysql_fix_privilege_tables'...
ERROR 1193 (HY000) at line 69: Unknown system variable
'have_csv'
ERROR 1064 (42000) at line 71: You have an error in your SQL
syntax;
check the manual