Backup: backup and restore the database

[Joachim Müller]

Rolled the suggested changes into a new version - please test and report.

[François Keller]

tested on my local gallery without problems (but not tested with minicms plugin tables)
attached updated french.php file

[AlexL]

cant test at this time - i test asap and call back

[su_ict]

Downloaded and installed 2.2 .
Minor things :

• CHANGELOG needs to be update to 2.2
• README.TXT - more language files than only english and french are present !

More testing in process 

[AlexL]

Hello

Now tested

After Backup message "Sicherung komplett" but 0% is shown
After Restore message "Wiederherstellung komplett" but 78% is shown
No error messages from cms or others.
What's the truth 78% or completed?
I've take a phpmyAdmin Backup before and after this action and then I've compared this files with Winmerge - all ok

An extra BackupRestore.php for restores with corrupt db's or PlugInConfigs is very helpfull - i hope next version come with this.
But if reachable from public internet then a password questioning is needed - to prevent the everybody from restore my db to an old version

[su_ict]

Testing - in Select table to process form i saw that my Table Prefix is cpg1410 but my release is 1412 - oopsie - whats going on    Checked - contra checked - read dump php files - checked again - pfoe.
At last i found out :
  Nothing to be concerned about : See thread - http://forum.coppermine-gallery.net/index.php?topic=45230.0 - table prefix is not updated to 1412 - works as designed !

Thought is was best to put it here before anyone else stumbles upon this 

[su_ict]

But if reachable from public internet then a password questioning is needed - to prevent the everybody from restore my db to an old version

You mean an extra check besides the fact that user is Admin ? If so - i second this request !

[Joachim Müller]

But if reachable from public internet then a password questioning is needed - to prevent the everybody from restore my db to an old version

You mean an extra check besides the fact that user is Admin ? If so - i second this request !

And what password are you going to check? Coppermine's admin password that is being stored in the database? Obviously not, as you're trying to restore a crashed database, so you can't check for the admin password.
I'm aware that there needs to be some method of authentification before a restore could possibly be performed:

I'm not sure though if this will go into the plugin (because I'm not sure how to accomplish this permissions-wise)

In my opinion I have the following options to accomplish authentification:

• Add a die-statement to the very first line of the standalone-restore file that a user deliberatly has to delete or comment out if he wants to perform a restore.
• Prompt the user for the mysql access data (mysql username and password)

Both options have drawbacks.

An extra BackupRestore.php for restores with corrupt db's or PlugInConfigs is very helpfull - i hope next version come with this.

I doubt that the next version will contain a standalone restore - I already said so:

I'm not sure though [...] when I will have the time to look into this, so don't expect such a file in the near future.

You're welcome to come up with a suggestion if you have the time.

Testing - in Select table to process form i saw that my Table Prefix is cpg1410 but my release is 1412 - oopsie - whats going on    Checked - contra checked - read dump php files - checked again - pfoe.
At last i found out :
  Nothing to be concerned about : See thread - http://forum.coppermine-gallery.net/index.php?topic=45230.0 - table prefix is not updated to 1412 - works as designed !

Thought is was best to put it here before anyone else stumbles upon this 

As suggested in the thread you refered to: the prefix is just a name that you deliberately chose when installing Coppermine in the first place. Yours is a PEBCAK issue, sorry. Your remark is in no way related to this thread. Please keep the discussion about the table prefix to the thread you refered to - don't cross-post.

Joachim

[AlexL]

Hello Joachim

I know that you have already pointed to the permission problem - I only have loud think about this problem, to animate the others to bring ideas. The Die-Statment you think to change per ftp? And the risk to leave it on after restore? The mysql access - maybe the Coppermine-Admin don't have the password, because the hoster make all this things for him? But for vulnerability it may be the better way to use this existing way, because the mysql team keeps this sure.

You're welcome to come up with a suggestion if you have the time.

To come with suggestions - I do my very best
But to realize this - is for me not a time problem rather then a problem of knowledge. Sorry but I can't code anything. And if I find time then I had to do a translation - you know.

But back to this PlugIn - what do you think about the 78% - is this a depiction problem btw. a problem with calculation? Or do the PlugIns Restore realy don't work to 100% - and then in case of disaster the restore isn't usefully?

[AlexL]

A new little confusion found - the files created from the PlugIn - I can't chmod this files with ftp - but i can delete this.
Is this a unix permission problem - because the files are php-created and the owner is the php-script?
Has my hoster to change anything on the server therefore?

[Joachim Müller]

Not related to the plugin, but a matter of server setup (ownership!)

[AlexL]

Ok - then I have think correct.
But what about the 78% - any Ideas

[cyberboy]

great tool..

installed ..

thx 

[twist]

works like a charm on my gallery but i've a question:
there is a way to automate the backup process? i tried to launch a lynx process and pass the form variabiles but it doesnt work, since checks if the user logged in.
And i'm not skilled enough to perform changes into sources :/
maybe any1 done something similar?

[AlexL]

Maybe better to use the phpmyadmin or other tools to make this on serverside

[twist]

Maybe better to use the phpmyadmin or other tools to make this on serverside

Sure but i cant cronjob that work with phpmyadmin
And other free tools around doenst work on php safe_mode /

[Joachim Müller]

phpMyAdmin is not an option for huge galleries, as it may time out. Additionally, making backups using other tools than this plugin is not the subject of this thread. Discussion about those other tools should not be lead here.
If you need a tool that will not time out and that can be set up to use cronjobs, then take a look at the free Tools recommended by the devs > mySqlDumper, but don't discuss it on this thread.
This plugin has not been made for users who have full control over their server (and that's the privilege level you need to run cronjobs): if you actually have the power to create cronjobs, you probably have shell access. You can easily come up with a script that takes advantages of the shell and use the mysqldump command available there.
Anyway, 99% of all users don't have the permission to do this and don't have the skills needed to come up with such a shell script. That's why this plugin has been created: you only need the skills needed to maintain coppermine in the first place to be able to use this plugin. It was designed for ease of use.

All discussions on alternative backup methods should be lead somewhere else (not in this thread).

Joachim

[mentalist3d]

Hi

just installed your plug-in and it works a charm, I've tried other plug-ins sometimes with negative effects so I was a bit hesitant, however using PHPmyAdmin was a bit daunting and this plug-in was just what I needed for a quick backup worry free, thanks :-)

PS - Will coppermine add this as standard to their software as it was always an option that I felt was missing from the main package.

Thanks again :-)

art.concepts.org.uk: register for free and begin displaying art with your free 100Mb of gallery space

[Joachim Müller]

Will coppermine add this as standard to their software as it was always an option that I felt was missing from the main package.

This is currently being discussed on the dev-only board. My vote is "yes".

[AlexL]

My vote is yes too. But with the extension of a separate php site (password protected) for restore in worstcase, if db corrupted and admin page don't work.