database backup limits

Permalink
Hi- If anyone could take the time for this simple question I'd be grateful.

I get this message when I try to backup before upgrade to 5.6.3.4

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 2883552 bytes) in /web/stephenscott.ca/httpdocs/updates/concrete5.6.3.3/concrete/core/libraries/backup.php on line 143

I had a look at the line but need a bit of guidance to correct this issue.

Anyone? Thanks.

Stephen

Eulalia
 
JohntheFish replied on at Permalink Best Answer Reply
JohntheFish
The most likely reason is that your database has grown bigger than you hosting account can cope with.

Do you have logging and page stats enabled? If so, these are often the culprit. My Extreme Clean job can be used to slim a database down, but does carry a chicken and egg risk because its always best to backup a database before cleaning it that extremely.

You can also backup from your hosting service control panel, outside of php and hence outside of the limits.

Another solution is my Backup Voodoo addon, that breaks a backup into slices that can be completed within a php web page.
Eulalia replied on at Permalink Reply
Eulalia
Hi John- Sorry to be so long replying- busy with things but also auto notification of replies to my thread did not work (and hasn't for a while).

Thanks for the tips- I'll work with what you told me- although my hosting is supposedly unlimited data, I think you're right, I can download the backups there.

I don't have anything else enabled, just plain old C5. If you mean by stats, webstats, I use clicky. Don't think my site carries a lot of data, but I do upload a lot of images, so maybe that has something to do with it.

Anyway I'll have a go. Thanks.

Stephen

PS- A question about use of the forum- is there a code of behaviour or usage that I should be aware of? I mean I am learning over time the ins and outs of building with this platform, and I haven't spent a lot of time answering others' questions as I by profession am not a web builder, just an artist trying to make a useful site.
JohntheFish replied on at Permalink Reply
JohntheFish
Statistics
- index.php/dashboard/system/seo/statistics/
if enabled, you will have an ever growing table called PageStatistics in the database. in phpMyAdmin you can 'Truncate' that table (but never delete it)

Logs
- index.php/dashboard/reports/logs/
Simply click the button to clear the log

Extreme Clean will do both of the above and also some other hidden log tables for downloads and jobs.

w.r.t the forums, its always helpful to answer where you can, but don't worry too much.
With questions the main thing is to be clear and include all the relevant information, so others can answer easily.
Eulalia replied on at Permalink Reply
Eulalia
Cool. It is enabled.
There is nothing posted past september last year in the log. Seemed quite detailed previous to that (logged every action).

S
Eulalia replied on at Permalink Reply
Eulalia
Issue is resolved John and Mason303. Contacted host and they increased the maximum memory my PHP scripts are allowed to allocate. Smooth. Thanks a lot.
mason203 replied on at Permalink Reply
As long as a database snapshot exists, the following limitations exist on the snapshot's source database:

The database cannot be dropped, detached, or restored. For information on how to delete a snapshot, see Dropping a Database Snapshot.
Performance is reduced, due to increased I/O on the source database resulting from a copy-on-write operation to the snapshot every time a page is updated.

Files cannot be dropped from the source database or from any snapshots.

The source database must be online, unless the database is a mirror database within a database mirroring session.
The source database cannot be configured as a scalable shared database.

To create a database snapshot on a mirror database, the database must be in the synchronized mirroring state