Back-up problem

bradymiller wrote on Tuesday, October 13, 2009:

Tony,

Doesn’t the current openemr/interface/main/backup.php script just save the entire openemr web directory? I’d suggest keeping this format (ie. no need only saving certain directories), since this is what users are now expecting. Could always make an option to do a more minimal backup. Also, check out Rod’s very recent commit which introduces several options for saving/restoring some configuration tables. His modifications should be compatible with 3.1.0, so suggest making your stuff work with this most recent script.

-brady

tmccormi wrote on Wednesday, October 14, 2009:

Yes it does backup the whole tree, so we are good there.  I’ll look for a post on that from Rod, I assume there is one?
-Tony

sunsetsystems wrote on Wednesday, October 14, 2009:

No, sorry, have been kinda busy.  But I think it pretty much explains itself.  It’s mostly intended for configuring multiple installations without a lot of repetitive manual work.

Rod 
(http://www.sunsetsystems.com/)

tmccormi wrote on Wednesday, October 14, 2009:

Thanks, I took a look at it.   It really doesn’t seem like the kind of thing an end-user would use.  Do you mind if we make it a configurable option?   I really see the single click backup as the most simple of user backup options.   This option doesn’t really have much meaning in that context.
-Tony

sunsetsystems wrote on Wednesday, October 14, 2009:

Sure, I will plan to do that.

Rod 
(http://www.sunsetsystems.com/)

bradymiller wrote on Wednesday, October 14, 2009:

Joe,

Here’s a good page explaining the mysqldump command:

http://www.devarticles.com/c/a/MySQL/Backing-Up-Your-MySQL-Databases-With-MySQLDump/1/

(In Example 1, use the ‘root’ as user and the mysql root password as password and looks like this):

mysqldump –-user root –-password=password openemr > openemr.sql

to restore the database try:

mysql –-user root –-password=password openemr < openemr.sql

that’s it; huge amount of documentation of this stuff via google regarding these commands and parameter options. If your mysql root password is blank then wouldn’t need user or password parameters.

(of course, do this stuff on your test server first)

-brady

ideaman911 wrote on Thursday, October 15, 2009:

Tony et al;

Bandwidth concerns me, especially for remote connectivity with my wife’s stand-alone.  Can the multi-OS backup.php  be configured to backup ONLY the changeable, and ideally check for changed files so as to minimize the write times for files which already exist, like most of the documents will, with a repetitive backup, like XCOPY already allows?

Also, can that be configured to work as a batch which can be called from the Scheduler, so it can be automatic in the background?

Lastly, will it restore without needing to know the database passwords, etc., ie can it restore where another password exists?  That does work now with the XCOPY approach I have been using (my use of multiple setup approaches in my testing has resulted in many different passwords, and I have made no effort to know which is which.  That probably would be a good idea, though ;-)  And, of course, can you provide the steps for restore, ideally also as an automatic or batch process?  Thanks.

Joe Holzer    Idea Man    315-622-9241     im@holzerent.com
http://www.holzerent.com