Mysql backups

[john_rsd]

I have seen a few threads around the board about errors with incomplete or eranous .sql files when using phpmyadmin to make database backups.

I experienced this today when a .sql backup I made was unable to be restored and it was only 12mB. Tried it many times. It is mostly attachments, only has 60 or so posts and 40 users.

As I cannot get telnet/ssh access (host does not allow it) what is the server configuration parameters that causes this problem?

The host is prepared to do the backups / restores for me but I don't like that idea so they are prepared to adjust the server configuration within reason if I let them know what the issues are.

My last option would be to ask for a cron to fill a mirror folder of my mysql folder in my domain root below public level.

Any insight would be appreciated.

php4.3.2/mysql4.0.15-std/Linux

[eva2000]

your host would have to grant you ssh telnet access with your a/cs username

that grant privileges on your mysqlusername/password so that you can run mysqldump yourself

the host of yours should know how to do this :)

[john_rsd]

Thanks Eva

The host refuses completely to give me telnet/ssh access. They are prepared to handle the restores for me if need be because of this.

But the backups are then under their control, not mine and the regular backups are what concerns me.

If there was some obvious settings within mysql or php that causes the time out (packet sizes, transfer time-outs...) issues and results in my incomplete .sql file when using myphpadmin I would have asked them to change these parameters so the phpmyadmin tool or their own backup tool through vDeck would work.

They also offered to set up a cron to dump the contents daily into my account root folder but I think they are going back on the idea now ... :mad:

Thanks again

[Steve Machol]

Setting up a cron job to make a daily backup of your database takes approximately one minute. If they are unwilling to do this, then you really should consider finding another host.