[Klug-general] Restoring sql backups not all rows restoring

[Karl Buckland]

Hi,

Nathan's suggestion does assume (I think!) that you're using the same
version of MySQL on both servers and that you are happy losing any other
existing databases on the target server.

Karl


On 13 August 2014 09:13, Nathan Friend <nathan.friend at gmail.com> wrote:

> If your having trouble with the import just copy the files from on the
> source server.  Shutdown MySQL first then tar up /var/lib/mysql directory.
>
> On the destination server, move the old mysql directory out of /var/lib
> and untar your source file.  Set the ownership to the mysql user and group
> and start the MySQL service.
>
> Much quicker than recreating the tables
>
> Cheers,
>
> Nathan.
>
>
> On Tue, Aug 12, 2014 at 5:12 PM, Laurence Southon <laurence at southon.uk.net
> > wrote:
>
>> On 12/08/14 16:59, Dan Attwood wrote:
>> > innodb
>> >
>>
>> Are you SQL'ing in externally, eg 'mysql dbname < dbname_dump.sql' ?
>>
>> Does it make a difference if you do it from the MySQL console, eg
>>
>> mysql> create database dbname;
>> mysql> use dbname:
>> mysql> source /path/to/dbname_dump.sql;
>>
>> That gives output in the console as it writes, so maybe will show a
>> problem?
>>
>> LS
>> --
>> Laurence Southon
>> Tiger Computing, Bexley
>> www.tiger-computing.co.uk
>>
>> _______________________________________________
>> Kent mailing list
>> Kent at mailman.lug.org.uk
>> https://mailman.lug.org.uk/mailman/listinfo/kent
>>
>
>
> _______________________________________________
> Kent mailing list
> Kent at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/kent
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/kent/attachments/20140813/ba84de7d/attachment-0001.html>