4.x site cloning snag

jason0 wrote on Friday, August 26, 2011:

Hello,

Yesterday, I tried to clone one of our sites using the setup tool.  I believe I ran into the php timeout limit. 

The database size is about 500megabytes, the documents folder for this site is around four gigabytes.  I watched the initial database dump, and file copy.  It even looked like it mostly built the new database, but after that, it would hang. 

I believe there was still some sort of session between my browser and apache, because if I clicked “reload”, or “back”, mysql would “back out” the new database, by removing it.

This was an older v4.0 development version of openemr, so I am not terribly concerned the clone didn’t work: I did it by hand…

Question: is there a means for php to return an exception saying the timeout has been reached?  If so, perhaps a message to the browser client that openemr took too long, so the user is less confused?  (Contact your admin…“I AM the admin!”)

Or, should there be some sort of rule of thumb that says “above a certain size, cloning can’t be done?” 

Should we also have some extra choices in the cloning process?  “clone db only but NOT the files!”

-jason

penguin8r wrote on Monday, August 29, 2011:

Isn’t there still a 512MB file size limit inherent to PHP5?  That could be the issue, I’ve always had better luck copying/moving a system manually.  It’s pretty simple to just dump/reload the database & copy over the directories.  You’re right though, if there’s going to be an automated tool for the process it needs to work, or at least give an error message when it doesn’t.