Use replication as your fail over and why not percona's xtrabackup or lvm type backup if
you need a backup?
Sabika
On Feb 19, 2013, at 1:20 PM, 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
>
