Allows you to optimize database, repair database, backup database, restore database, delete backup database , drop\/empty tables and run selected queries. Supports automatic scheduling of backing up, optimizing and repairing of database.<\/p>\n\n
WP-DBManager<\/code> Plugin<\/li>\n- The script will automatically create a folder called
backup-db<\/code> in the wp-content folder if that folder is writable. If it is not created, please create the folder and ensure that the folder is writable<\/li>\n- Go to
WP-Admin -> Database -> DB Options<\/code> to configure the database options<\/li>\n- Secure the backup folder, see below<\/li>\n
- Go to
WP-Admin -> Database -> Backup DB<\/code>, which checks whether the folder is actually reachable over HTTP and tells you if it is<\/li>\n<\/ol>\n\nSecuring The Backup Folder<\/h3>\n\n
A database backup contains everything, including your users table. Anyone who can guess a backup file name can download the lot, so the folder must not be served over HTTP.<\/p>\n\n
The reliable option, on any server:<\/strong> set Path To Backup<\/code> under WP-Admin -> Database -> DB Options<\/code> to a folder outside your web root, for example \/var\/www\/example.com\/backup-db<\/code> when WordPress lives in \/var\/www\/example.com\/public_html<\/code>. Nothing served, nothing to configure.<\/p>\n\nIf the folder has to stay inside the web root:<\/p>\n\n
\n- Apache<\/strong> \u2014 move
htaccess.txt<\/code> from Folder: wp-content\/plugins\/wp-dbmanager<\/code> to Folder: wp-content\/backup-db\/.htaccess<\/code><\/li>\n- IIS<\/strong> \u2014 move
Web.config.txt<\/code> from Folder: wp-content\/plugins\/wp-dbmanager<\/code> to Folder: wp-content\/backup-db\/Web.config<\/code><\/li>\n- nginx<\/strong> \u2014 nginx does not read
.htaccess<\/code> files, so the file above does nothing. Add this to your server block and reload nginx:<\/li>\n<\/ul>\n\nlocation ^~ \/wp-content\/backup-db\/ { deny all; }\n<\/code><\/pre>\n\nMove index.php<\/code> from Folder: wp-content\/plugins\/wp-dbmanager<\/code> to Folder: wp-content\/backup-db\/index.php<\/code> as well, so the folder cannot be listed.<\/p>\n\nThe Backup DB<\/code> page requests a file from the folder and reports what the server actually returns, so you can confirm the folder is closed rather than assume it.<\/p>\n\nDevelopment<\/h3>\n\n\n- https:\/\/github.com\/lesterchan\/wp-dbmanager<\/a><\/li>\n<\/ul>\n\n
Credits<\/h3>\n\n\n- Plugin icon by Freepik<\/a> from Flaticon<\/a><\/li>\n<\/ul>\n\n
Donations<\/h3>\n\n\n- I spent most of my free time creating, updating, maintaining and supporting these plugins, if you really love my plugins and could spare me a couple of bucks, I will really appreciate it. If not feel free to use it without any obligations.<\/li>\n<\/ul>\n\n\n
\nMy database is not backed up \/ My backup file is 0Kb<\/h3><\/dt>\n\n- Ensure that your host allows you to access mysqldump. You can try to narrow the problem by Debugging via SSH:<\/li>\n<\/ul>\n\n
\n- In
wp-dbmanager.php<\/code><\/li>\n- Find
check_backup_files();<\/code> on line 246<\/li>\n- Add below it
echo $command;<\/code><\/li>\n- Go to
WP-Admin -> Database -> Backup<\/code><\/li>\n- Click
Backup<\/code><\/li>\n- It should print some debugging statements<\/li>\n
- Copy that line than run it in SSH<\/li>\n
- If you need help on SSH contact your host or google for more info<\/li>\n<\/ol><\/dd>\n
What is the difference between WP-DBManager and WP-DB-Backup?<\/h3><\/dt>\n\n- WP-DBManager uses
mysqldump<\/code> application to generate the backup and mysql<\/code> application to restore them via shell.<\/li>\n- WP-DB-Backup uses PHP to generate the backup. In some cases WP-DB-Backup will work better for you because it requires less permissions. Not all host allows you to access mysqldump\/mysql directly via shell.<\/li>\n
- WP-DBManager allows you to have automatic optimizing and repairing of database on top of backing up of database.<\/li>\n<\/ul><\/dd>\n
Why do I get the message \"Warning: Your backup folder MIGHT be visible to the public!\"?<\/h3><\/dt>\n\n- Ensure that you have renamed
htaccess.txt<\/code> to .htaccess<\/code> and placed it in your backup folder (defaults to wp-content\/backup-db\/<\/code>)<\/li>\n- If you are 100% sure you have did that and have verfied that the folder no longer is accessible to the public by visiting the URL
http:\/\/yousite.com\/wp-content\/backup-db\/<\/code>, you can safely disable the notice by going to WP-Admin -> Database -> DB Options<\/code> and set Hide Admin Notices<\/code> to Yes<\/code>.<\/li>\n<\/ul><\/dd>\n\n<\/dl>\n\n\nVersion 3.0.0<\/h3>\n\n\n- NOTE: The mysqldump and mysql paths are now passed as a single argument. If you added extra flags to either path under DB Options, move them out or your backups will fail.<\/li>\n
- NOTE: Requires WordPress 6.0 or later, up from 4.0, and PHP 7.4 or later.<\/li>\n
- NOTE: Backup file names now carry a real Unix timestamp. Backups taken before this release will show a date shifted by your timezone offset. The files themselves are fine.<\/li>\n
- NEW: WordPress 7.0<\/li>\n
- NEW: The Backup Database page now asks the server whether the backup folder is actually reachable over HTTP, instead of assuming a dropped in .htaccess protects it. nginx is detected and given a configuration snippet that works.<\/li>\n
- NEW: 'Attach Backup File' option to control whether the scheduled backup e-mail carries the database file. Existing sites keep attaching it.<\/li>\n
- NEW: New backups are gzipped by default.<\/li>\n
- CHANGED: New installs no longer prefill the backup e-mail address, so scheduled backup e-mails are opt-in.<\/li>\n
- CHANGED: Translations now come from the WordPress.org language packs. The bundled .pot file and the load_plugin_textdomain() call are gone, both were redundant.<\/li>\n
- FIXED: Escape all output on the admin screens to prevent XSS.<\/li>\n
- FIXED: Validate table names against the database before emptying, dropping, optimizing or repairing.<\/li>\n
- FIXED: The database password is no longer passed on the command line.<\/li>\n
- FIXED: Require the
install_plugins<\/code> capability for the backup folder notice, the download and the folder fix.<\/li>\n- FIXED: Only download backup files that resolve inside the backup folder.<\/li>\n
- FIXED: Validate the mysqldump, mysql and backup paths independently.<\/li>\n
- FIXED: Every file now refuses to run when loaded directly.<\/li>\n
- FIXED: Cron backups no longer rename and e-mail a dump that failed, an empty file is no longer passed off as a backup.<\/li>\n
- FIXED: Restoring no longer reports success when the restore did not run.<\/li>\n
- FIXED: Keep pruning old backups until the maximum is met, and treat a maximum below 1 as no limit.<\/li>\n
- FIXED: Two backups written in the same second are no longer invisible to pruning and the manage screen.<\/li>\n
- FIXED: Network activation and uninstall now cover every site, not just the first 100.<\/li>\n
- FIXED: Uninstalling on multisite no longer overwrites the current site ID while it works.<\/li>\n
- FIXED: Removed jQuery dependency.<\/li>\n<\/ul>\n\n
Version 2.80.10<\/h3>\n\n\n- FIXED: Don't throw fatal error if unknown .sql files are inside the database backup folder.<\/li>\n<\/ul>\n\n
Version 2.80.9<\/h3>\n\n\n- FIXED: Handle folder permissions properly<\/li>\n<\/ul>\n\n
Version 2.80.8<\/h3>\n\n\n- FIXED: Miss out database-backup.php.<\/li>\n<\/ul>\n\n
Version 2.80.7<\/h3>\n\n\n- FIXED: Changed 'edit_files' capability to 'install_plugins' instead.<\/li>\n<\/ul>\n\n
Version 2.80.6<\/h3>\n\n\n- FIXED: Remove 'manage_database' and use 'edit_files' to check for capability instead.<\/li>\n<\/ul>\n\n
Version 2.80.5<\/h3>\n\n\n- FIXED: Changed utf8 to utf8mb4 for backing up<\/li>\n<\/ul>\n\n
Version 2.80.4<\/h3>\n\n\n- FIXED: Clear WP-DBManager cron jobs on uninstall<\/li>\n<\/ul>\n\n
Version 2.80.3<\/h3>\n\n\n- FIXED: Poly fill array_key_first() for PHP < 7.3<\/li>\n<\/ul>\n\n
Version 2.80.2<\/h3>\n\n\n- FIXED: Newer backup is being replaced instead of older backup<\/li>\n<\/ul>\n\n
Version 2.80.1<\/h3>\n\n\n- FIXED: 1970 date issues.<\/li>\n
- FIXED: Sorting order of backup files. <\/li>\n<\/ul>\n\n
Version 2.80<\/h3>\n\n