List:General Discussion« Previous MessageNext Message »
From:Mogens Melander Date:April 11 2007 7:31pm
Subject:Re: database backup problem, since database over 60mb
View as plain text  
Hi,

Maybe you will have better luck with a command like:

mysqldump -u user -ppassword databasename > backup_date.sql

Regarding phpmyadmin, my guess would be, the script is longer
than the permitted time to finish.

Defaults in php.ini is something like:

max_execution_time = 30  ; Maximum execution time of each script,
                         ; in seconds
max_input_time = 60      ; Maximum amount of time each script may spend
                         ; parsing request data
memory_limit = 8M        ; Maximum amount of memory a script may
                         ; consume (8MB)

-- 
Later

Mogens Melander
+45 40 85 71 38
+66 870 133 224


On Wed, April 11, 2007 21:11, Richard wrote:
> Hello, I've got a problem with mysql 5 on my debian server.
>
> I've got a forum on this server and untill the database reached about 60
> Mo I could dump the database with either phpmyadmin or with the command :
>
> mysql -u user -p'password' databasename > backup_date.sql
>
> My last backup that worked was about 56Mb, but now since I've gone over
> the 60mb my backup files with phpmyadmin and mysqldump are only around
> 46Mb and therefore don't contain everything and also when I do a
> mysql -u user -p'password' databasename > backup_date.sql
>
> it never finishes, and even if I wait for two hours the bacup_date.sql
> file is 0Mb ...
>
> The forum runs well and I use no compression I save the file in simple
> .sql text format.
>
> Any ideas as to why it does this or how I can fix it would be great !
> I've gone through my my.cnf file and I can't see any setting that seems
> to block this. If you need any further information please let me know
>
> Thanks in advance,
>
> Richard
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql?unsub=1
>
>
> --
> This message has been scanned for viruses and
> dangerous content by OpenProtect(http://www.openprotect.com), and is
> believed to be clean.
>



-- 
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.

Thread
database backup problem, since database over 60mbRichard11 Apr
  • Re: database backup problem, since database over 60mbDan Buettner11 Apr
  • Re: database backup problem, since database over 60mbMogens Melander11 Apr