Author: paul
Date: 2008-02-29 22:02:51 +0100 (Fri, 29 Feb 2008)
New Revision: 10079
Log:
r29813@arctic: paul | 2008-02-29 15:01:20 -0600
Tweaks to backup chapter intro
Modified:
trunk/it/refman-5.1/backup.xml
trunk/pt/refman-5.1/backup.xml
trunk/refman-4.1/backup.xml
trunk/refman-5.0/backup.xml
trunk/refman-5.1/backup.xml
trunk/refman-6.0/backup.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29613
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29811
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29613
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29813
Modified: trunk/it/refman-5.1/backup.xml
===================================================================
--- trunk/it/refman-5.1/backup.xml 2008-02-29 19:57:48 UTC (rev 10078)
+++ trunk/it/refman-5.1/backup.xml 2008-02-29 21:02:51 UTC (rev 10079)
Changed blocks: 1, Lines Added: 64, Lines Deleted: 6; 3048 bytes
@@ -13,15 +13,73 @@
</remark>
<para>
+ It is important to back up your databases in case problems occur so
+ that you can recover your data and be up and running again. MySQL
+ offers a variety of backup techniques that you can choose from to
+ select the method that best suites the requirements for your
+ installation.
+ </para>
+
+ <para>
This chapter discusses how to make database backups (full and
- incremental) and how to perform table maintenance. The syntax of the
- SQL statements described here is given in
- <xref linkend="sql-syntax"/>. Much of the information here pertains
- primarily to <literal>MyISAM</literal> tables. Additional
- information about <literal>InnoDB</literal> backup procedures is
- given in <xref linkend="innodb-backup"/>.
+ incremental). The syntax of the SQL statements described here is
+ given in <xref linkend="sql-syntax"/>.
</para>
+ <para>
+ Data integrity can be compromised if tables become corrupt, so this
+ chapter also covers techniques for checking tables and repairing
+ them should problems be found. These techniques apply primarily to
+ <literal>MyISAM</literal> tables. See
+ <xref linkend="table-maintenance"/>.
+ </para>
+
+ <para>
+ Topics covered elsewhere in this manual that are related to backup
+ or to maintaining data availability include the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For additional information about <literal>InnoDB</literal>
+ backup procedures, see <xref linkend="innodb-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Replication enables you to maintain identical data on multiple
+ servers. This has several benefits, such as allowing client load
+ to be distributed over servers, availability of data even if a
+ given server is taken offline or fails, and the ability to make
+ backups using a slave server without affecting the master. See
+ <xref linkend="replication"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster provides a high-availability, high-redundancy
+ version of MySQL adapted for the distributed computing
+ environment. See <xref linkend="mysql-cluster"/>. For
+ information specifically about MySQL Cluster backup, see
+ <xref linkend="mysql-cluster-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Distributed Replicated Block Device (DRBD) is another
+ high-availability solution. It works by replicating a block
+ device from a primary server to a secondary server at the block
+ level. See <xref linkend="ha-overview"/>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<section id="backup">
<title>Database Backups</title>
Modified: trunk/pt/refman-5.1/backup.xml
===================================================================
--- trunk/pt/refman-5.1/backup.xml 2008-02-29 19:57:48 UTC (rev 10078)
+++ trunk/pt/refman-5.1/backup.xml 2008-02-29 21:02:51 UTC (rev 10079)
Changed blocks: 1, Lines Added: 64, Lines Deleted: 6; 3048 bytes
@@ -13,15 +13,73 @@
</remark>
<para>
+ It is important to back up your databases in case problems occur so
+ that you can recover your data and be up and running again. MySQL
+ offers a variety of backup techniques that you can choose from to
+ select the method that best suites the requirements for your
+ installation.
+ </para>
+
+ <para>
This chapter discusses how to make database backups (full and
- incremental) and how to perform table maintenance. The syntax of the
- SQL statements described here is given in
- <xref linkend="sql-syntax"/>. Much of the information here pertains
- primarily to <literal>MyISAM</literal> tables. Additional
- information about <literal>InnoDB</literal> backup procedures is
- given in <xref linkend="innodb-backup"/>.
+ incremental). The syntax of the SQL statements described here is
+ given in <xref linkend="sql-syntax"/>.
</para>
+ <para>
+ Data integrity can be compromised if tables become corrupt, so this
+ chapter also covers techniques for checking tables and repairing
+ them should problems be found. These techniques apply primarily to
+ <literal>MyISAM</literal> tables. See
+ <xref linkend="table-maintenance"/>.
+ </para>
+
+ <para>
+ Topics covered elsewhere in this manual that are related to backup
+ or to maintaining data availability include the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For additional information about <literal>InnoDB</literal>
+ backup procedures, see <xref linkend="innodb-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Replication enables you to maintain identical data on multiple
+ servers. This has several benefits, such as allowing client load
+ to be distributed over servers, availability of data even if a
+ given server is taken offline or fails, and the ability to make
+ backups using a slave server without affecting the master. See
+ <xref linkend="replication"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster provides a high-availability, high-redundancy
+ version of MySQL adapted for the distributed computing
+ environment. See <xref linkend="mysql-cluster"/>. For
+ information specifically about MySQL Cluster backup, see
+ <xref linkend="mysql-cluster-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Distributed Replicated Block Device (DRBD) is another
+ high-availability solution. It works by replicating a block
+ device from a primary server to a secondary server at the block
+ level. See <xref linkend="ha-overview"/>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<section id="backup">
<title>Database Backups</title>
Modified: trunk/refman-4.1/backup.xml
===================================================================
--- trunk/refman-4.1/backup.xml 2008-02-29 19:57:48 UTC (rev 10078)
+++ trunk/refman-4.1/backup.xml 2008-02-29 21:02:51 UTC (rev 10079)
Changed blocks: 1, Lines Added: 55, Lines Deleted: 6; 2757 bytes
@@ -13,15 +13,64 @@
</remark>
<para>
+ It is important to back up your databases in case problems occur so
+ that you can recover your data and be up and running again. MySQL
+ offers a variety of backup techniques that you can choose from to
+ select the method that best suites the requirements for your
+ installation.
+ </para>
+
+ <para>
This chapter discusses how to make database backups (full and
- incremental) and how to perform table maintenance. The syntax of the
- SQL statements described here is given in
- <xref linkend="sql-syntax"/>. Much of the information here pertains
- primarily to <literal>MyISAM</literal> tables. Additional
- information about <literal>InnoDB</literal> backup procedures is
- given in <xref linkend="innodb-backup"/>.
+ incremental). The syntax of the SQL statements described here is
+ given in <xref linkend="sql-syntax"/>.
</para>
+ <para>
+ Data integrity can be compromised if tables become corrupt, so this
+ chapter also covers techniques for checking tables and repairing
+ them should problems be found. These techniques apply primarily to
+ <literal>MyISAM</literal> and <literal>ISAM</literal> tables. See
+ <xref linkend="table-maintenance"/>.
+ </para>
+
+ <para>
+ Topics covered elsewhere in this manual that are related to backup
+ or to maintaining data availability include the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For additional information about <literal>InnoDB</literal>
+ backup procedures, see <xref linkend="innodb-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Replication enables you to maintain identical data on multiple
+ servers. This has several benefits, such as allowing client load
+ to be distributed over servers, availability of data even if a
+ given server is taken offline or fails, and the ability to make
+ backups using a slave server without affecting the master. See
+ <xref linkend="replication"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster provides a high-availability, high-redundancy
+ version of MySQL adapted for the distributed computing
+ environment. See <xref linkend="mysql-cluster"/>. For
+ information specifically about MySQL Cluster backup, see
+ <xref linkend="mysql-cluster-backup"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<section id="backup">
<title>Database Backups</title>
Modified: trunk/refman-5.0/backup.xml
===================================================================
--- trunk/refman-5.0/backup.xml 2008-02-29 19:57:48 UTC (rev 10078)
+++ trunk/refman-5.0/backup.xml 2008-02-29 21:02:51 UTC (rev 10079)
Changed blocks: 1, Lines Added: 55, Lines Deleted: 6; 2729 bytes
@@ -13,15 +13,64 @@
</remark>
<para>
+ It is important to back up your databases in case problems occur so
+ that you can recover your data and be up and running again. MySQL
+ offers a variety of backup techniques that you can choose from to
+ select the method that best suites the requirements for your
+ installation.
+ </para>
+
+ <para>
This chapter discusses how to make database backups (full and
- incremental) and how to perform table maintenance. The syntax of the
- SQL statements described here is given in
- <xref linkend="sql-syntax"/>. Much of the information here pertains
- primarily to <literal>MyISAM</literal> tables. Additional
- information about <literal>InnoDB</literal> backup procedures is
- given in <xref linkend="innodb-backup"/>.
+ incremental). The syntax of the SQL statements described here is
+ given in <xref linkend="sql-syntax"/>.
</para>
+ <para>
+ Data integrity can be compromised if tables become corrupt, so this
+ chapter also covers techniques for checking tables and repairing
+ them should problems be found. These techniques apply primarily to
+ <literal>MyISAM</literal> tables. See
+ <xref linkend="table-maintenance"/>.
+ </para>
+
+ <para>
+ Topics covered elsewhere in this manual that are related to backup
+ or to maintaining data availability include the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For additional information about <literal>InnoDB</literal>
+ backup procedures, see <xref linkend="innodb-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Replication enables you to maintain identical data on multiple
+ servers. This has several benefits, such as allowing client load
+ to be distributed over servers, availability of data even if a
+ given server is taken offline or fails, and the ability to make
+ backups using a slave server without affecting the master. See
+ <xref linkend="replication"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster provides a high-availability, high-redundancy
+ version of MySQL adapted for the distributed computing
+ environment. See <xref linkend="mysql-cluster"/>. For
+ information specifically about MySQL Cluster backup, see
+ <xref linkend="mysql-cluster-backup"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<section id="backup">
<title>Database Backups</title>
Modified: trunk/refman-5.1/backup.xml
===================================================================
--- trunk/refman-5.1/backup.xml 2008-02-29 19:57:48 UTC (rev 10078)
+++ trunk/refman-5.1/backup.xml 2008-02-29 21:02:51 UTC (rev 10079)
Changed blocks: 1, Lines Added: 64, Lines Deleted: 6; 3039 bytes
@@ -13,15 +13,73 @@
</remark>
<para>
+ It is important to back up your databases in case problems occur so
+ that you can recover your data and be up and running again. MySQL
+ offers a variety of backup techniques that you can choose from to
+ select the method that best suites the requirements for your
+ installation.
+ </para>
+
+ <para>
This chapter discusses how to make database backups (full and
- incremental) and how to perform table maintenance. The syntax of the
- SQL statements described here is given in
- <xref linkend="sql-syntax"/>. Much of the information here pertains
- primarily to <literal>MyISAM</literal> tables. Additional
- information about <literal>InnoDB</literal> backup procedures is
- given in <xref linkend="innodb-backup"/>.
+ incremental). The syntax of the SQL statements described here is
+ given in <xref linkend="sql-syntax"/>.
</para>
+ <para>
+ Data integrity can be compromised if tables become corrupt, so this
+ chapter also covers techniques for checking tables and repairing
+ them should problems be found. These techniques apply primarily to
+ <literal>MyISAM</literal> tables. See
+ <xref linkend="table-maintenance"/>.
+ </para>
+
+ <para>
+ Topics covered elsewhere in this manual that are related to backup
+ or to maintaining data availability include the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For additional information about <literal>InnoDB</literal>
+ backup procedures, see <xref linkend="innodb-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Replication enables you to maintain identical data on multiple
+ servers. This has several benefits, such as allowing client load
+ to be distributed over servers, availability of data even if a
+ given server is taken offline or fails, and the ability to make
+ backups using a slave server without affecting the master. See
+ <xref linkend="replication"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster provides a high-availability, high-redundancy
+ version of MySQL adapted for the distributed computing
+ environment. See <xref linkend="mysql-cluster"/>. For
+ information specifically about MySQL Cluster backup, see
+ <xref linkend="mysql-cluster-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Distributed Replicated Block Device (DRBD) is another
+ high-availability solution. It works by replicating a block
+ device from a primary server to a secondary server at the block
+ level. See <xref linkend="ha-overview"/>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<section id="backup">
<title>Database Backups</title>
Modified: trunk/refman-6.0/backup.xml
===================================================================
--- trunk/refman-6.0/backup.xml 2008-02-29 19:57:48 UTC (rev 10078)
+++ trunk/refman-6.0/backup.xml 2008-02-29 21:02:51 UTC (rev 10079)
Changed blocks: 1, Lines Added: 64, Lines Deleted: 6; 3039 bytes
@@ -13,15 +13,73 @@
</remark>
<para>
+ It is important to back up your databases in case problems occur so
+ that you can recover your data and be up and running again. MySQL
+ offers a variety of backup techniques that you can choose from to
+ select the method that best suites the requirements for your
+ installation.
+ </para>
+
+ <para>
This chapter discusses how to make database backups (full and
- incremental) and how to perform table maintenance. The syntax of the
- SQL statements described here is given in
- <xref linkend="sql-syntax"/>. Much of the information here pertains
- primarily to <literal>MyISAM</literal> tables. Additional
- information about <literal>InnoDB</literal> backup procedures is
- given in <xref linkend="innodb-backup"/>.
+ incremental). The syntax of the SQL statements described here is
+ given in <xref linkend="sql-syntax"/>.
</para>
+ <para>
+ Data integrity can be compromised if tables become corrupt, so this
+ chapter also covers techniques for checking tables and repairing
+ them should problems be found. These techniques apply primarily to
+ <literal>MyISAM</literal> tables. See
+ <xref linkend="table-maintenance"/>.
+ </para>
+
+ <para>
+ Topics covered elsewhere in this manual that are related to backup
+ or to maintaining data availability include the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For additional information about <literal>InnoDB</literal>
+ backup procedures, see <xref linkend="innodb-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Replication enables you to maintain identical data on multiple
+ servers. This has several benefits, such as allowing client load
+ to be distributed over servers, availability of data even if a
+ given server is taken offline or fails, and the ability to make
+ backups using a slave server without affecting the master. See
+ <xref linkend="replication"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster provides a high-availability, high-redundancy
+ version of MySQL adapted for the distributed computing
+ environment. See <xref linkend="mysql-cluster"/>. For
+ information specifically about MySQL Cluster backup, see
+ <xref linkend="mysql-cluster-backup"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Distributed Replicated Block Device (DRBD) is another
+ high-availability solution. It works by replicating a block
+ device from a primary server to a secondary server at the block
+ level. See <xref linkend="ha-overview"/>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<section id="backup">
<title>Database Backups</title>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10079 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 29 Feb |
