|
Lines 50-57
Link Here
|
| 50 |
<body> |
50 |
<body> |
| 51 |
|
51 |
|
| 52 |
<p> |
52 |
<p> |
| 53 |
One of the fundamental works of every database administrator is ... to make |
53 |
One of the most important tasks that every database administrator has to perfom |
| 54 |
backup of the data. So proceed with one. |
54 |
is backing up data. Here we go: |
| 55 |
</p> |
55 |
</p> |
| 56 |
|
56 |
|
| 57 |
<pre caption="Dump of all databases"> |
57 |
<pre caption="Dump of all databases"> |
|
Lines 67-83
Link Here
|
| 67 |
<i>--hex-blob \</i> |
67 |
<i>--hex-blob \</i> |
| 68 |
<i>--master-data \</i> |
68 |
<i>--master-data \</i> |
| 69 |
<i>--max_allowed_packet=16M \</i> |
69 |
<i>--max_allowed_packet=16M \</i> |
|
|
70 |
<i>--quote-names</i> |
| 70 |
<i>--result-file=BACKUP_MYSQL_4.0.SQL</i> |
71 |
<i>--result-file=BACKUP_MYSQL_4.0.SQL</i> |
| 71 |
</pre> |
72 |
</pre> |
| 72 |
|
73 |
|
| 73 |
<p> |
74 |
<p> |
| 74 |
Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, this one can be |
75 |
Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, which later can |
| 75 |
used to recreate your data, the data is described in the MySQL dialect of SQL, |
76 |
be used to recreate your data. The data is described in the MySQL dialect of SQL, |
| 76 |
the Structured Query Language. |
77 |
the Structured Query Language. |
| 77 |
</p> |
78 |
</p> |
| 78 |
|
79 |
|
| 79 |
<p> |
80 |
<p> |
| 80 |
This would be a good time to see if the backup you have created is working. |
81 |
Now would also be a good time to see if the backup you have created is working. |
| 81 |
</p> |
82 |
</p> |
| 82 |
|
83 |
|
| 83 |
</body> |
84 |
</body> |
|
Lines 90-96
Link Here
|
| 90 |
<body> |
91 |
<body> |
| 91 |
|
92 |
|
| 92 |
<p> |
93 |
<p> |
| 93 |
If you have skipped step #1, you now have to create a backup package (the |
94 |
If you have skipped step #1, you now have to create a backup package (of the |
| 94 |
database server, not the data) of the currently installed version: |
95 |
database server, not the data) of the currently installed version: |
| 95 |
</p> |
96 |
</p> |
| 96 |
|
97 |
|
|
Lines 99-105
Link Here
|
| 99 |
</pre> |
100 |
</pre> |
| 100 |
|
101 |
|
| 101 |
<p> |
102 |
<p> |
| 102 |
Now it's time to clean out the current version and all it's data: |
103 |
Now it's time to clean out the current version and all of its data: |
| 103 |
</p> |
104 |
</p> |
| 104 |
|
105 |
|
| 105 |
<pre caption="Uninstall MySQL"> |
106 |
<pre caption="Uninstall MySQL"> |
|
Lines 111-120
Link Here
|
| 111 |
</pre> |
112 |
</pre> |
| 112 |
|
113 |
|
| 113 |
<note> |
114 |
<note> |
| 114 |
At this time two backup should exist, one portable between various MySQL |
115 |
Now twi different backups should exist: The SQL one, which is portable between |
| 115 |
versions, the SQL one. <br /> |
116 |
various versions of MySQL, and the other one that will allow you to quickly |
| 116 |
The other instead permit to restore quickly the system at this point. Later on |
117 |
restore your database. This will be covered later in this doc in more detail. |
| 117 |
this doc will be explain how to recover from this last one. |
|
|
| 118 |
</note> |
118 |
</note> |
| 119 |
|
119 |
|
| 120 |
<p> |
120 |
<p> |
|
Lines 180-187
Link Here
|
| 180 |
<body> |
180 |
<body> |
| 181 |
|
181 |
|
| 182 |
<p> |
182 |
<p> |
| 183 |
If the result is not fully satisfactory, it's possible to reinstall the old |
183 |
If you are not happy with MySQL 4.1, it's possible to go back to MySQL 4.0. |
| 184 |
MySQL 4.0 version. |
|
|
| 185 |
</p> |
184 |
</p> |
| 186 |
|
185 |
|
| 187 |
<pre caption="Back to the past"> |
186 |
<pre caption="Back to the past"> |
|
Lines 189-195
Link Here
|
| 189 |
# <i>emerge -C mysql</i> |
188 |
# <i>emerge -C mysql</i> |
| 190 |
# <i>rm -rf /var/lib/mysql/ /var/log/mysql</i> |
189 |
# <i>rm -rf /var/lib/mysql/ /var/log/mysql</i> |
| 191 |
# <i>emerge --usepkgonly "<mysql-4.1"</i> |
190 |
# <i>emerge --usepkgonly "<mysql-4.1"</i> |
| 192 |
# <i>tar -xjpvf mysql.[tag] -C/tmp</i> |
191 |
# <i>tar -xjpvf mysql.[tag] -C /</i> |
| 193 |
# <i>/etc/init.d/mysql start</i> |
192 |
# <i>/etc/init.d/mysql start</i> |
| 194 |
</pre> |
193 |
</pre> |
| 195 |
|
194 |
|
|
Lines 203-212
Link Here
|
| 203 |
<body> |
202 |
<body> |
| 204 |
|
203 |
|
| 205 |
<p> |
204 |
<p> |
| 206 |
Under particular conditions it's possible to upgrade directly to the next major |
205 |
Under certain conditions it's possible to directly upgrade to the next major |
| 207 |
version of MySQL.<br /> |
206 |
version of MySQL. If you know what you're doing and think that applies to your |
| 208 |
If you know that this is your case, with a little trick it's possible to upgrade |
207 |
case, here's a little trick that makes it possible to directly upgrade to |
| 209 |
straight to MySQL 4.1. |
208 |
MySQl 4.1. |
| 210 |
</p> |
209 |
</p> |
| 211 |
|
210 |
|
| 212 |
<pre caption="Straight upgrade"> |
211 |
<pre caption="Straight upgrade"> |
|
Lines 227-233
Link Here
|
| 227 |
</pre> |
226 |
</pre> |
| 228 |
|
227 |
|
| 229 |
<p> |
228 |
<p> |
| 230 |
Good luck and don't ask. |
229 |
Good luck and don't if something fails, don't say we didn't warn you! ;-) |
| 231 |
</p> |
230 |
</p> |
| 232 |
|
231 |
|
| 233 |
</body> |
232 |
</body> |
