# MySQL Server Instance Configuration File # ---------------------------------------------------------------------- # Generated by the MySQL Server Instance Configuration Wizard # # # Installation Instructions # ---------------------------------------------------------------------- # # On Linux you can copy this file to /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options # (@localstatedir@ for this installation) or to # ~/.my.cnf to set user-specific options. # # On Windows you should keep this file in the installation directory # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To # make sure the server reads the config file use the startup option # "--defaults-file". # # To run run the server from the command line, execute this in a # command line shell, e.g. # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini" # # To install the server as a Windows service manually, execute this in a # command line shell, e.g. # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini" # # And then execute this in a command line shell to start the server, e.g. # net start MySQLXY # # # Guildlines for editing this file # ---------------------------------------------------------------------- # # In this file, you can use all long options that the program supports. # If you want to know the options a program supports, start the program # with the "--help" option. # # More detailed information about the individual options can also be # found in the manual. # # # CLIENT SECTION # ---------------------------------------------------------------------- # # The following options will be read by MySQL client applications. # Note that only client applications shipped by MySQL are guaranteed # to read this section. If you want your own MySQL client program to # honor these values, you need to specify it as an option during the # MySQL client library initialization. # [client]port=3306[mysql] default-character-set=latin1 # SERVER SECTION # ---------------------------------------------------------------------- # # The following options will be read by the MySQL Server. Make sure that # you have installed the server correctly (see above) so it reads this # file. # [mysqld]# The TCP/IP Port the MySQL Server will listen on port=3306 #Path to installation directory. All paths are usually resolved relative to this. basedir="C:/Program Files/MySQL/MySQL Server 5.5/"#Path to the database root datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"# The default character set that will be used when a new schema or table is # created and no character set is defined character-set-server=latin1# The default storage engine that will be used when create new tables when default-storage-engine=INNODB# Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"# The maximum amount of concurrent sessions the MySQL server will # allow. One of these connections will be reserved for a user with # SUPER privileges to allow the administrator to login even if the # connection limit has been reached. max_connections=100# Query cache is used to cache SELECT results and later return them # without actual executing the same query once again. Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely changing tables. See the # "Qcache_lowmem_prunes" status variable to check if the current value # is high enough for your load. # Note: In case your tables change very often or if your queries are # textually different every time, the query cache may result in a # slowdown instead of a performance improvement. query_cache_size=0# The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe] table_cache=1024# Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them. tmp_table_size=5120M# How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before. This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.) thread_cache_size=8#*** MyISAM Specific options# The maximum size of the temporary file MySQL is allowed to use while # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE. # If the file-size would be bigger than this, the index will be created # through the key cache (which is slower). myisam_max_sort_file_size=100G# If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method. This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_sort_buffer_size=33M# Size of the Key Buffer, used to cache index blocks for MyISAM tables. # Do not set it larger than 30% of your available memory, as some memory # is also required by the OS to cache rows. Even if you're not using # MyISAM tables, you should still set it to 8-64M as it will also be # used for internal temporary disk tables. key_buffer_size=24M# Size of the buffer used for doing full table scans of MyISAM tables. # Allocated per thread, if a full scan is needed. read_buffer_size=64K read_rnd_buffer_size=256K# This buffer is allocated when MySQL needs to rebuild the index in # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE # into an empty table. It is allocated per thread so be careful with # large settings. sort_buffer_size=256K #*** INNODB Specific options *** # Use this option if you have a MySQL server with InnoDB support enabled # but you do not plan to use it. This will save memory and disk space # and speed up some things. #skip-innodb# Additional memory pool that is used by InnoDB to store metadata # information. If InnoDB requires more memory for this purpose it will # start to allocate it from the OS. As this is fast enough on most # recent operating systems, you normally do not need to change this # value. SHOW INNODB STATUS will display the current amount used. innodb_additional_mem_pool_size=2M# If set to 1, InnoDB will flush (fsync) the transaction logs to the # disk at each commit, which offers full ACID behavior. If you are # willing to compromise this safety, and you are running small # transactions, you may set this to 0 or 2 to reduce disk I/O to the # logs. Value 0 means that the log is only written to the log file and # the log file flushed to disk approximately once per second. Value 2 # means the log is written to the log file at each commit, but the log # file is only flushed to disk approximately once per second. innodb_flush_log_at_trx_commit=1# The size of the buffer InnoDB uses for buffering log data. As soon as # it is full, InnoDB will have to flush it to disk. As it is flushed # once per second anyway, it does not make sense to have it very large # (even with long transactions). innodb_log_buffer_size=1M# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and # row data. The bigger you set this the less disk I/O is needed to # access data in tables. On a dedicated database server you may set this # parameter up to 80% of the machine physical memory size. Do not set it # too large, though, because competition of the physical memory may # cause paging in the operating system. Note that on 32bit systems you # might be limited to 2-3.5G of user level memory per process, so do not # set it too high. innodb_buffer_pool_size=45M# Size of each log file in a log group. You should set the combined size # of log files to about 25%-100% of your buffer pool size to avoid # unneeded buffer pool flush activity on log file overwrite. However, # note that a larger logfile size will increase the time needed for the # recovery process. innodb_log_file_size=23M# Number of threads allowed inside the InnoDB kernel. The optimal value # depends highly on the application, hardware as well as the OS # scheduler properties. A too high value may lead to thread thrashing. innodb_thread_concurrency=10max_heap_table_size=10240Minnodb_data_file_path = ibdata1:10M:autoextend:max:20480M server-id=1 log-bin=c:\log-bin.log binlog-do-db=sasadb
server-id=3
master-host=192.168.1.68
master-port=3306
master-user=backup
master-password=1234
master-connect-retry=60 在从服务器上加入这话，mysql服务重启不了
转：
为了数据的安全，客户有两台机器作为互相备份，当一台机器出现故障时，自动切换到另外一台服务器。大部分的软件我们是通过LifeKeeper来实现的，但是MySQL的双机备份在LifeKeeper里没有实现，看来，只有我手动来实现MySQL的双机备份了哦。
先说说环境QUOTE:操作系统：windows 2003 server
MySQL版本：v4.1
互备数据库：bbs
Server1：10.2.2.3
Server2：10.2.2.4其实，MySQL的双机备份有一个很简单的第三方软件可以实现，那就是SQLyog （http://www.webyog.com/），他有一个功能叫sja（SQLyog Job Agent ，http://www.webyog.com/sqlyog/sja.html），可以轻松实现，但是却有一个不足，那就是MySQL表里必须有一个primary key，如果没有，则此表不能用sja来实现。我查看了一下，我们需要互备的数据中就有两三个表没有primary key，看来要放弃这个方法了。第二种方法就是用MySQL自身的Replication机制来实现了。据说MySQL 3.23以上的版本都有此功能。下面来说说具体的步骤。1）先在每台服务器上各安装好mysql，保证正常运行，在Mysql的安装目录里各建立一个目录logs，如F:\Mysql4.1\logs，供后面步骤使用。2）将要互备的初始化数据在每台服务器上各导入一份，且保持两台服务器要互备的初始化数据一致。这个步骤很重要。3）在每个server上各增加一个备份用户，且赋予一定的权限。3.1）在Server1上QUOTE:GRANT REPLICATION SLAVE,RELOAD,SUPER ON *.* TO backup@'10.2.2.4' IDENTIFIED BY '123456';之后立即在Server2上用如下命令来测试backup用户是否能连接上Server1QUOTE:F:\Mysql4.1\bin\mysql.exe -h10.2.2.3 -ubackup -p123456如果能连接上，表明互备帐户增加OK！3.2）重复上述动作，在Server2上QUOTE:GRANT REPLICATION SLAVE,RELOAD,SUPER ON *.* TO backup@'10.2.2.3' IDENTIFIED BY '123456';之后立即在Server1上用如下命令来测试backup用户是否能连接上Server2QUOTE:F:\Mysql4.1\bin\mysql.exe -h10.2.2.4 -ubackup -p123456如果能连接上，表明互备帐户增加OK！4）修改mysql配置文件，增加互备参数配置。4.1）停掉server1的mysql，修改my.ini，在[mysqld]区域内增加如下信息：QUOTE:#####################################################
#MySQL的双机备份,by longware,2006-05-26server-id=1
log-bin=F:/MySQL4.1/logs/syncmaster-host=10.2.2.4
master-user=backup
master-password=123456
master-port=3306
master-connect-retry=60
replicate-do-db=bbs
#####################################################保存并关闭my.ini文件，重启mysql服务，观察logs目录下面有没有类似sync.000001、sync.index的文件生成，观察data目录里有没有*.info、*-relay-bin.000001、*-relay-bin.index的文件生成，如果两个目录都有，说明互备参数配置正确。4.2）停掉server2的mysql，修改my.ini，在[mysqld]区域内增加如下信息：QUOTE:#####################################################
#MySQL的双机备份,by longware,2006-05-26server-id=2
log-bin=F:/MySQL4.1/logs/syncmaster-host=10.2.2.3
master-user=backup
master-password=123456
master-port=3306
master-connect-retry=60
replicate-do-db=bbs
#####################################################保存并关闭my.ini文件，重启mysql服务，观察logs目录下面有没有类似sync.000001、sync.index的文件生成，观察data目录里有没有*.info、*-relay-bin.000001、*-relay-bin.index的文件生成，如果两个目录都有，说明互备参数配置正确。4.3）如果没有看到上步中说的文件，说明配置文件没有起作用，请检查mysql配置文件的位置，很可能在c:\windows\下面，也可能在C:\Documents and Settings\Administrator\windows下面，还可能在F:\Mysql4.1\下面，具体要看您的mysql服务的启动参数，您可以去windows的“开始－控制面板－管理工具－服务”中，双击mysql的服务名称，查看”可执行文件的路径“项的值，如果是QUOTE:F:/mysql4.1/bin/mysqld-nt.exe则my.ini可能就在c:\windows\下面，如果是QUOTE:"F:\MySQL4.1\bin\mysqld-nt" --defaults-file="F:\MySQL4.1\my.ini" MySQL则my.ini就在F:\MySQL4.1下面。我的一个朋友就因为没有搞清楚my.ini的位置，折腾了大半天也每搞定。5）分别停掉两台机器的mysql服务，再次确保两台机器的要互备的初始化数据一致，删除logs下面的文件，删除data下面的非目录文件，确保网络畅通，再分别启动server1和server2的mysql服务，mysql双机互备成功了。6）互备测试，在server1里的bbs数据库里建一张表，插几条数据，再登陆到server2里，看看数据是否存在，存在表明OK。7）注意：两台机器的mysql互备的初始化数据要相同。如果要单向备份，将其中的一台服务器的my.ini的互备配置注释掉重启即可。
http://guoh.org/lifelog/2011/08/mysql-master-slave-replication/
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]port=3306[mysql]
default-character-set=latin1
# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]# The TCP/IP Port the MySQL Server will listen on
port=3306
#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 5.5/"#Path to the database root
datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"# The default character set that will be used when a new schema or table is
# created and no character set is defined
character-set-server=latin1# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=1024# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=5120M# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8#*** MyISAM Specific options# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=33M# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=24M# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=45M# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=23M# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=10max_heap_table_size=10240Minnodb_data_file_path = ibdata1:10M:autoextend:max:20480M
server-id=1
log-bin=c:\log-bin.log
binlog-do-db=sasadb
http://guoh.org/lifelog/2011/08/mysql-master-slave-replication/