So I did a full mysqldump over the weekend for a second time and this
time it is 220GB, no clue what happened last time, I should have
realized looking at the file size something was wrong, but since I got
no errors did not think about it, and this time I timed it, took 7
hours to do a complete mysqldump
Restoring it is not fun 18+ hours and counting, at this rate it will
be a week, there has to be a better way of doing this, and this is
only going form 5.0 to 5.1
I know some are saying don't need to do a mysqldump, but if i don't do
it, the upgrade errors out on 10 tables, and then gives me errors
about triggers
On Tue, Feb 19, 2013 at 6:34 PM, Reindl Harald <h.reindl@stripped> wrote:
>
>
> Am 19.02.2013 23:53, schrieb Divesh Kamra:
>> Hi Reindi
>>
>>
>> Thanks for solution .........
>>
>> Can u share complete steps ?
>
> which steps?
>
> * update
> * call "mysql_upgrade -u root -p"
>
> in doubt "mysqlcheck -h localhost --check-upgrade --all-databases --auto-repair
> --user=root -p"
>
> and if you do "mysql_upgrade -u root -p" and are always
> up-to-date that was it, no matter if you move your data
> from windows to MacOSX and finally to linux or whatever OS
>
>> On 20-Feb-2013, at 2:50, Reindl Harald <h.reindl@stripped> wrote:
>>
>>> surely
>>>
>>> * use "mysql_upgrade -u root -p" after EACH update
>>> * upgrade regulary
>>>
>>> we went from MySQL 3.x to 5.5.30 until know without
>>> any dump and here are around 5000 tables
>>>
>>> Am 19.02.2013 22:12, schrieb Divesh Kamra:
>>>> Is there any better way for grade MySQL version without taking backup
> with mysqldump
>>>>
>>>> Or if there any tool for this
>>>>
>>>> R's
>>>> DK
>>>>
>>>> On 16-Feb-2013, at 16:07, Reindl Harald <h.reindl@stripped>
> wrote:
>>>>>
>>>>> Am 16.02.2013 09:42, schrieb Manuel Arostegui:
>>>>>> 2013/2/15 Reindl Harald <h.reindl@stripped
> <mailto:h.reindl@stripped>>
>>>>>>
>>>>>> "our database is 400 GB, mysqldump is 600MB" was not a typo and
> you
>>>>>> honestly believed that you can import this dump to somewhat?
>>>>>>
>>>>>> WTF - as admin you should be able to see if the things in
> front
>>>>>> of you are theoretically possible before your start any action
>>>>>> and 1:400 is impossible, specially because mysql-dumps are
>>>>>> ALWAYS WAY LARGER then the databasses because they contain
>>>>>> sql-statements and not only data
>>>>>>
>>>>>> That's not completely true. If you have a poor maintained
> database or just tables with lot of writes and deletes
>>>>>> and you don't periodically optimize it - you can end up with lot
> of blank spaces in your tables which will use _a
>>>>>> lot_ of space. If you do a "du" or whatever to measure your
> database size...you can get really confused.
>>>>>> mysqldump obviously doesn't backup blank spaces and once you get
> rid of them, your database will use much less space.
>>>>>
>>>>> ok, normally i expect there is a admin and doing his job
>>>>> especially for large datasets
>>>
>
> --
>
> Reindl Harald
> the lounge interactive design GmbH
> A-1060 Vienna, Hofmühlgasse 17
> CTO / CISO / Software-Development
> p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
> icq: 154546673, http://www.thelounge.net/
>
> http://www.thelounge.net/signature.asc.what.htm
>
