MyOOS [Dumper] based on MySQLDumper 1.24.4

About this project

MyOOS [Dumper] is an improved version of MySQLDumper 1.24.4 (January 24, 2011). This enhancement takes into account the development of PHP.

Most of all stability, security and handling are the main focus of MyOOS [Dumper]. But also an attractive template is included, which can be edited and adapted to your own needs.

MyOOS [Dumper] is a backup program for MySQL databases, written in PHP and Perl. With it, backup copies of the data (store, blog, etc.) can be created and restored if necessary. Especially for web space without shell access, MyOOS [Dumper] is a useful alternative.

The idea for MySQLDumper came from Daniel Schlichtholz. He opened the MySQLDumper forum in 2004, whereupon programmers wrote new scripts and extended existing ones.

Wish List / Future Attractions

Do you have any suggestions for improvements? Feel free to contact the development team via the forum https://foren.myoos.de/viewforum.php?f=41.

Contribute

If you would like to help us improve the MyOOS project, we welcome your pull requests via GitHub here.

https://github.com/r23/MyOOS-Dumper/

Financial Support

You can use PayPal Me
. https://www.paypal.com/paypalme/r23de?locale.x=de_DE

or via the QR code
. Financial support for MyOOS [Dumper]

Send money to the MyOOS project.

We hope you enjoy this project.

The MyOOS [Dumper] Team

MyOOS [Dumper] Help

Download

You can always get the latest versions via GitHub
. https://github.com/r23/MyOOS-Dumper/releases

System requirement

The script works on any server (Windows, Linux, ...)
with PHP >= version 7.4 with GZip support, MySQL (version 4.1 or higher), JavaScript (must be enabled)

Copy the mod folder from the MyOOS archive to a separate working folder.

Installation

. The installation process is straightforward.

From the MyOOS archive, copy the mod folder into any folder.
Upload all the files from the mod folder to your web server. (For example, to the lowest level in [server web directory/]mod)
... done!
You can now call MyOOS [Dumper] in your web browser by "https://example.com/mod/",
to complete the installation. Just follow the instructions.

Note:
If on your server the script is not allowed to create directories,
you have to do this manually, because MyOOS [Dumper] stores the data ordered in directories.
The script aborts with an appropriate statement!
After you have created the directories (according to the hint), it runs normally and without restrictions.

Perl script instructions

. Most have a cgi-bin directory where perl can be run.
This is usually accessible by browser via http://www.example.com/cgi-bin/.

For this case, please perform the following steps:

. 1. call the Backup page in MyOOS [Dumper] and click on "Backup Perl".
2. copy the path that is behind entry in crondump.pl for $absolute_path_of_configdir:.
3. open the file "crondump.pl" in the editor.
4. enter the copied path there at absolute_path_of_configdir (no spaces).
5. save crondump.pl .
6. copy crondump.pl, as well as perltest.pl and simpletest.pl into the cgi-bin directory (ascii mode in FTP).
7. give the files the permissions 755.
7b. If the ending cgi is desired, change the ending of all 3 files from pl -> cgi (rename).
8. call the configuration in MyOOS [Dumper].
9. select the page Cronscript.
10. change perl execution path to /cgi-bin/ .
10b. If the scripts have .pl, change the file extension to .cgi .
11.Save the configuration.

Done, the scripts can now be called from the backup page.

. For those who can run Perl in all directories, the following steps will suffice:

. 1. call in the MyOOS [Dumper] the page Backup.
2. copy the path that is behind entry in crondump.pl for $absolute_path_of_configdir:.
3. open the file "crondump.pl" in the editor.
4. enter the copied path there at absolute_path_of_configdir (no spaces).
5. save crondump.pl .
6. give the files the permissions 755.
6b. If the extension cgi is desired, change the extension of all 3 files from pl -> cgi (rename).
(ev. 10b+11 from above)

Windowsuser have to change the first line of all scripts, there is the path of Perl. Example:
instead of: #!/usr/bin/perl -w
now: #!C:_usr/bin/perl.exe -w

Operation

Home

Configuration

Configured databases: the listing of configured databases. The active database is listed in bold.
Table prefix: here you can specify (for each database) a prefix. This is a filter that will take into account for dumps only the tables that start with this prefix (for example, all tables that start with "phpBB_"). If you want all tables in this database to be saved, just leave the field empty.
GZip compression: Here you can enable compression. It is recommended to enable it, because the files will be much smaller after all and disk space is always scarce.
Email with Dumpfile: If this option is enabled, an email with the dump as an attachment will be sent after the backup is complete (caution, compression should absolutely be on, otherwise the attachment will be too large and may not be sent!).
Email address: Recipient address for the email.
Sender of the email: this address appears as the sender in the email.
FTP Transfer: If this option is enabled, the backup file will be sent via FTP after the backup is completed.
FTP Server: The address of the FTP server (e.g. ftp.mybackups.com).
FTP Server Port: The port of the FTP server (usually 21).
FTP User: The username of the FTP account.
FTP Password: The password of the FTP account.
FTP Upload Folder: The directory where the backup file should go (upload permissions must exist!).
Automatic deletion of backups: If this option is enabled, older backups will be deleted automatically according to the following rules.
Number of backup files: A value > 0 deletes all backup files except for the number specified here.
Language: here you specify the language for the interface.

Administration

Restore: This will update the database with the selected backup file.
Delete: This lets you delete the selected backup file.
Start new backup: Here you start a new backup (dump) according to the parameters set in the configuration.