Backup MySQL Database

[torvista]

You have a memory limit set of 128M.

My db is 25MB and it fails immediately on a restore until I have 448M or above.

You could increase the memory limit globally or just stick these at the start of the file and experiment uncommenting one at a time to see what you need:

/** for phpStorm
 * @var queryFactoryResult $db
 * @var messageStack $messageStack
 */
ini_set('memory_limit', '256M');
//ini_set('memory_limit', '320M');
//ini_set('memory_limit', '384M');
//ini_set('memory_limit', '448M');
//ini_set('memory_limit', '512M');

[NWCE]

Thanks for your reply and help Steve!

I did add this in to the file and commented out the first line with 256M and uncommented the last line with 512M.

I then tried Restore again and this was my error:

[31-Jan-2025 16:54:08 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 455454064 bytes) in C:\wamp64\www\new2121\zc_plugins\BackupMySQL\v2.0.0\admin\backup_mysql.php on line 626
[31-Jan-2025 16:54:08 UTC] PHP Stack trace:
[31-Jan-2025 16:54:08 UTC] PHP 1. {main}() C:\wamp64\www\new2121\admin\index.php:0
[31-Jan-2025 16:54:08 UTC] PHP 2. require() C:\wamp64\www\new2121\admin\index.php:28
[31-Jan-2025 16:54:08 UTC] PHP 3. str_replace($search = '/*M!999999\\- enable the sandbox mode */', $replace = '', $subject = '/*M!999999\\- enable the sandbox mode */ \n-- MariaDB dump 10.19 Distrib 10.6.19-MariaDB, for Linux (x86_64)\n--\n-- Host: localhost Database: v_158\n-- ------------------------------------------------------\n-- Server version\t10.6.19-MariaDB\n\n/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;\n/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;\n/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;\n/*!40101 SET NAMES utf8mb4 */;\n/*!40103 SET @OLD_TIME_ZONE=@'..., $count = 0) C:\wamp64\www\new2121\zc_plugins\BackupMySQL\v2.0.0\admin\backup_mysql.php:626

[31-Jan-2025 16:54:08 UTC] Request URI: /new2121/admin/index.php?cmd=backup_mysql&file=db_v_158-20250127071022.sql.gz&action=restorenow, IP address: 127.0.0.1
--> PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 455454064 bytes) in C:\wamp64\www\new2121\zc_plugins\BackupMySQL\v2.0.0\admin\backup_mysql.php on line 626.

[31-Jan-2025 16:54:08 UTC] Request URI: /new2121/admin/index.php?cmd=backup_mysql&file=db_v_158-20250127071022.sql.gz&action=restorenow, IP address: 127.0.0.1
--> PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 455454064 bytes) in C:\wamp64\www\new2121\zc_plugins\BackupMySQL\v2.0.0\admin\backup_mysql.php on line 626.

The first bit of the error almost looks as if there are old fragments that it doesn't like. I had run the zc_install after inserting this database in to update it and I have also run the database converter tool. I then ran the Restore and this (above was my error).

It still seems to have memory errors.....

Any ideas??

[torvista]

Is it the same problem if it is zip or gzip?

Have you manually extracted the file to have a look at it/check it is not corrupted in some way?

[NWCE]

I am backing up on my live site using this plugin (v.3) as my live site is Zen Cart v.1.5.8

This plugin at that version only gives the option of No Compression or gzip

As for it being corrupt....I have tested everything else on my development site both on the site and Admin and the only 2 plugins (I have about a dozen installed) that I am having errors with is this one and Instant Search....so I wouldn't think it was corrupted. I will check though.

Is it possible that there is a file with a memory_limit such as in Admin/includes/functions/general.php (calling it) that is setting the memory limit??

I have run a backup in my development site using this plugin as a .zip rather than gzip. I then used this backup and used Restore. All worked fine, I received the green messages in the Admin panel top detailing that it was successful....I then took a look around the site and clicked on products, Add to Cart, etc. and the development site works perfectly (except Instant Search still...Undefined Constant)

Do you think this was coincidence that the Restore worked as a zip because I was restoring the exact, unchanged database??

So it seems that if the database is saved as a zip it works....as a gzip it throws the memory limit error. Any other thoughts as to what this could be???

[torvista]

>so I wouldn't think it was corrupted.
I mean the file you are trying to restore: un-gzip it and look with a text editor that all looks above board.

[NWCE]

Hi Steve....

Makes sense to check...

I have now done this and viewing it in Notepad ++ everything is there and legible....No corruption.

Do you have any other thoughts on why it works as zip file rather than a gzip??

I guess I can move on as I can import my database as a zip file and by pass the gzip option.

Thank you for your help with this plugin and I will subscribe to the thread to watch for further developments!

Thanks again!

[torvista]

What is the database version?

[torvista]

...on each server.

[NWCE]

My database that I have copied in from my live site is V.1.5.8 and I then have run the zc_installer to update the database to v.2.1

The database goes back awhile as we've had our store since 2006....not sure if that's important or not....so we've been through all of the upgrades since then.

I have also run the database converter plugin to insure that it corrects everything. The db_charset in my config files is utf8mb4 on both my live and development sites. Again...not sure if this provides any clues....just trying to give the full picture.

Thanks for your help!

[torvista]

No. I meant the database server..MySQL/Maria and their versions.