# MySQL backup function acting wonky **URL:** \ **Category:** Get Help\ **Created:** [January 29, 2025, 8:05pm UTC](https://speciforum.org/t/mysql-backup-function-acting-wonky/2305 "2025-01-29T20:05:19Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Leslie](https://avatars.discourse-cdn.com/v4/letter/l/ba8739/32.png) [@Leslie](https://speciforum.org/u/Leslie)\ **Post date:** [January 29, 2025, 8:05pm UTC](https://speciforum.org/t/mysql-backup-function-acting-wonky/2305/1 "2025-01-29T20:05:19Z")
> [@On another topic](https://speciforum.org/t/2258/1): > > I was having some problems with my computer and had to reinstall Specify 6.8.03. After I reinstalled it, I wanted to run a backup. I try to run backups weekly and have a good backup from the end of December. In the new installation, I went to Preferences - MySQL and filled in the three paths that are needed to run a backup. The backup runs (for all of about 3 seconds) and then the notice goes away. That time frame is way too short to backup my database. I went out to our server and looked at the folder where the backups are stored. The last backup, from December is there with ~788,000KB and a Stat file of 5KB. The newest backup has 0KB and a Stat file of 5KB. My IT guy tried the same method and also came up with 0KB. He then ran a backup through a command box (I think) and the backup showed up with an ~800,000KB file size. So, the MySQL function is recognizing the database and is performing the backup, but it doesn’t seem to recognize any of the data in the database. I have not been able to get the backup to function properly and have to have my IT guy run my weekly backup for me. Any special setting or other esoteric thing that may have been affected by the fresh install? Any help appreciated. --Leslie ---
**Author:** ![Grant](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/grant/32/4255_2.png) [@Grant](https://speciforum.org/u/Grant)\ **Post date:** [February 17, 2025, 3:13pm UTC](https://speciforum.org/t/mysql-backup-function-acting-wonky/2305/2 "2025-02-17T15:13:43Z")
Hi @Leslie, Thank you for your question! At this time, we do not recommend that users rely solely on the Specify 6 SpBackupRestore utility for performing their backups due to the issue described here: [**Important: Specify Database Backups Can Fail**](https://speciforum.org/t/important-specify-database-backups-can-fail/927) From this write-up, the following remedy has been recommended: > [@](#): > > ## Remedy > > Because the backups fail due to a Data Set whose size that exceeds the default parameter value in MySQL/MariaDB that constrains how much data can be transmitted in a single network packet, a short term solution is to increase the maximum amount of information that can be transmitted. This MySQL documentation page describes how to change the value of maximum allowed packet size parameter: > > [https://dev.mysql.com/doc/refman/5.7/en/packet-too-large.html](https://dev.mysql.com/doc/refman/5.7/en/packet-too-large.html) > > We recommend changing the max\_allowed\_packet size value to 1024M. It is important to note that both the client and the server have their own [max\_allowed\_packet](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_max_allowed_packet) variable, and that the parameter’s value must be changed in both places. > > You can edit the MySQL configuration file to include the following under the [mysqld] header to enable the maximum allowed packet size: > > ```auto > [mysqld] > > innodb_buffer_pool_size=100MB > max_allowed_packet=1024MB > net_read_timeout=3600 > net_write_timeout=3600 > > ``` Most importantly, the server’s MariaDB environment should be configured to have the `max_allowed_packet` variable set to `1024MB` to make sure the backup can complete properly. Once that is adjusted, please try making the backup again and let us know if you still encounter any issues! We have also found it useful for an IT staff member to set up an automatic process (in addition to any regular request) that creates a backup via the command line on a set schedule. This ensures that a copy is accessible to you whenever needed and that it is being dumped in its entirety. At KU, we regularly perform backups. We keep daily backups for a week, weekly backups for a month, monthly backups for a year, and yearly backups indefinitely. ---
**Author:** ![Leslie](https://avatars.discourse-cdn.com/v4/letter/l/ba8739/32.png) [@Leslie](https://speciforum.org/u/Leslie)\ **Post date:** [February 18, 2025, 4:24pm UTC](https://speciforum.org/t/mysql-backup-function-acting-wonky/2305/3 "2025-02-18T16:24:35Z")
Thanks Grant, I forwarded your reply to our IT guy, Brian Gollands. I will see what he can do. –Leslie ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex029/uploads/specifysoftware/original/2X/1/18a843c97bc32b40e8ad0e035755bc88ffaacaf7.svg) [@system](https://speciforum.org/u/system)\ **Post date:** [July 23, 2025, 5:50pm UTC](https://speciforum.org/t/mysql-backup-function-acting-wonky/2305/4 "2025-07-23T17:50:22Z")
Closed on July 23, 2025, 5:50pm UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.