I want to transfer my DB (3MB) from my Apache development server to the live one.

The problem is that the Max. file size B&M accepts is different in the live server even though I have installed the same version of the module; 5.x-1.2.

The messages I get when I start the restoring are different as well:

Upload a backup file created by this version of this module. For other database backups please use another tool for import. Max file size: 16 MB => Development server
Upload a backup file created by this version of this module. For other database backups please use another tool for import. Max file size: 2 MB => Live server

I assumed first the module looks at the php.ini file to determine the allowed memory size and execution time and based on that calculates the Max. file size but I verified and
there is no difference between both servers.

How are the values of 2 and 16MB defined? Could you give me a hint where to look for ? tks a lot

Comments

alexo007’s picture

Assigned: Unassigned » alexo007

I found the issue:

The B&M module takes the Max. allowed file size from the site's Max upload file size (Configurable at: Home » Administer » Site configuration » File uploads).
The restriction to the site's Max. size is given by the PHP settings.

I found that the Max. allowed upload size is the minimun value of:
post_max_size =
upload_max_filesize =

in the php.ini configuration file.

By increasing both to 32M, B&M allows me now in theory to restore databases as big as 32M.
Because I have root access to the php.ini, I am able to increase as well
max_execution_time =
max_input_time =
memory_limit =

Now I only wonder if there is any other limitation why I should not use the great benefits of B&M to back up and restore big databases (??)

ronan’s picture

Status: Active » Fixed

Theoretically if you can up those limits you should be able to use this module with any size dbs, but it's not tested with or designed for really big databases, so proceed with caution. Let me know if you have any other issues.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

chaloalvarezj’s picture

Does this mean that this module depends on the optional core module: upload ??