I would like to change Backup mySQL

[DrByte]

I'm not sure I understand what the "issue" is. The files are already named with a prescribed naming convention. Is THAT what you don't like?
Or is it simply that the activity-log backups are also in that folder, and causing you some confusion?

Or is this an issue of your own making because you're constantly needing to restore from backup because you're doing dev work and breaking things frequently? .... and such problem will be rare in the normal course of operating a live site.

[torvista]

For my part there is no issue....I use automated backups and the naming doesn't matter.
However I back up manually before doing any db changes or imports and it would be nice to be able to name it on the page at the time rather than remotely.
Not really important for me, hence I have not bothered to change it....but seems important to help the monkeys the OP works for.

I restore from backup loads of times...repeatedly on my dev site, for example while trying to get mod sql scripts to work 100% in the SQL patch page.
I also move the db around between laptops depending where I have to work, and to have a current db to dry-run large imports on.

Its an essential mod for me, I wouldn't leave home without it.

[Feznizzle]

Ditto to everything Torvista said, precisely as said.

What got me motivated was that a client added a Newsletter page the other day, something that gets coded by a wysiwyg editor on a ConstantContact type CRM site. Whatever they did caused the site to disappear and they freaked out. When I came to sort it out, apparently they had backed up a few times as they were adding other stuff, w/o noticing they had already killed the site.

So it took me a minute to sort it out. If there was a naming gui, would have been much easier.

DrByte, your mod is awesome and I love it. I realize the thought of making even minor changes is sacrilege, I really don't mean to offend!

Renaming the files (w/o adding a gui) is for the lest tech savvy (clients). When my client restored on their own, they restored the wrong files, thought they had lost a number of pages. I think they could have figured out the right file had they paid attention to the center column instead of looking at file names.

I have helped them to understand it better, don't think these guys will have a problem again. But they are not my only clients.

Adding a gui would be a convenience for all, but really not necessary for developer (though it would be nice). That would be best solution for monkeys, though. And it would be a convenience for me, as well

[DrByte]

Ha! I'm not worried about sacrilege! But I'm flattered by the thought. Lol.

While I'm not opposed to the idea of a naming GUI, I am also mindful that the uninformed will similarly misname things and not have a clue which file to pick when they do a restore anyway. I'm not convinced it will completely eliminate the stated problem.

Adding a dialog to ask for a filename is doable ... just remember you'll need to sanitize inputs to be sure that no unacceptable characters are passed on to the actual backup process, else you'll get errors that there isn't currently any error-handling code for.

Renaming after-the-fact could be added easily with an ajax script. Still needs validation of acceptable characters. But happening after-the-fact could mean the file gets lost amidst a long list, and thus might be skipped by the newb.

[lhungil]

Instead of changing the naming convention... how about allowing the end user to embed a "comment"? This could be embeded in the SQL file... This way both archived and current backups would include the "comment". Although parsing them all to display in admin would be a little extra work...

Not something I personally need, but just another way to save "Why did the last backup occur?"

[Feznizzle]

DrByte,

I really hope you do get some satisfaction from the fact that we all look up to you as much as we do. For every one person you help directly by replying to questions in this forum, a dozen or more will stumble in and find the solutions you give. Everyone knows that solutions you give can pretty much be taken as the Word of God!

And the mods you have provided are spectacular. It must be neat to know that right at this very moment somewhere in Asia or S Dakota or the UK, there are people using things you created!

Backup MySQL, in particular, was a real stroke of genius!

That's why I'm embarrassed to even suggest that an improvement could be made. But I can't help it, I just think the way the files are named are bit messy.

This is what I did. I found the code for naming files in admin/backup_mysql.php (this line):

$backup_file = 'db_' . DB_DATABASE . '-' . ($tables_to_export != '' ? 'limited-' : '' ) . date('YmdHis') . '.sql';

And then I restructured it a bit:

$backup_file = '00-Date_' . date('Y') . '-' . date('m') . '-' . date('d') . '__Time-' . date('H') . '-' . date('i') . '-' . date('s')  . '.sql';

The resulting file names (see attached image):
• have the db info removed
• clearly state the date and time
• match (within a few seconds) the date/time given in center column
• appear above the Admin Activity Archives

DrByte, if you see any error in my restructuring, please let me know.

While I would greatly prefer a naming GUI, I don't trust my abilities enough to do it myself. If anybody wants to do it, I will be happy to beta!

[Feznizzle]

Woah! Adding a comment would be great!!!

I was trying to avoid sql changes... but if you were going to the effort to allow file naming, adding a comment would be a very worthy use of time!

[torvista]

A comment in a g/zipped sql file my be difficult to extract automatically on a windows server, certainly my default xampp install cannot do gzip.
I think being able to optionally append some text to the default/improved date-time filename would be the most user/code friendly: it would still keep them in chronological order in the backup folder.