Support

My cron job backup had not been finishing due to a 2 minute limit by the hosting site that I can't change. I split the backup into three parts: images, other files, and database only (with the stuff needed to do a arestore). That solved the problem for a while, but the database backup eventually got too big.

I looked at table sizes and pruned all of the no longer needed history stuff I could find (some of it quite large), and that solved the problem. I'm now around 1:40 for the DB backup.

But I'm concerned that I might go over the limit at some point and have to do something else. I've attached a log file of a DB backup.

Is there anything I can do if this happens, other than split the DB backup into several sections, based on tables?

Thanks.

There really is not much we can do to get the backup elapsed time under two minutes. Especially when you're hitting that with the database dump alone.

It would be much easier to trigger a front end backup via webcron.com. This is not a free service, but it will cost you a fraction of a cent per backup. You are right, at some point you will go over the time limit again.

Thanks. I have tested webcron, and it does what I need and costs next to nothing, as you said.

You're welcome! I'm glad webcron.com worked for you.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.