|
1 === WP-DB-Backup === |
|
2 Contributors: filosofo |
|
3 Donate link: http://austinmatzko.com/wordpress-plugins/wp-db-backup/ |
|
4 Tags: mysql, database, backup, cron |
|
5 Requires at least: 2.0.3 |
|
6 Tested up to: 3.6.1 |
|
7 Stable tag: 2.2.4 |
|
8 |
|
9 On-demand backup of your WordPress database. |
|
10 |
|
11 == Description == |
|
12 |
|
13 WP-DB-Backup allows you easily to backup your core WordPress database tables. You may also backup other tables in the same database. |
|
14 |
|
15 Released under the terms of the GNU GPL, version 2. |
|
16 http://www.fsf.org/licensing/licenses/gpl.html |
|
17 |
|
18 NO WARRANTY. |
|
19 |
|
20 Copyright (c) 2013 Austin Matzko |
|
21 |
|
22 == Installation == |
|
23 1. Extract the wp-db-backup/ folder file to /wp-content/plugins/ |
|
24 1. Activate the plugin at your blog's Admin -> Plugins screen |
|
25 1. The plugin will attempt to create a directory /wp-content/backup-*/ inside your WordPress directory. |
|
26 1. You may need to make /wp-content writable (at least temporarily) for it to create this directory. |
|
27 For example: |
|
28 `$ cd /wordpress/` |
|
29 `$ chgrp www-data wp-content` (where "`www-data`" is the group your FTP client uses) |
|
30 `$ chmod g+w wp-content` |
|
31 |
|
32 == Frequently Asked Questions == |
|
33 |
|
34 = How do I restore my database from a backup? = |
|
35 |
|
36 Briefly, use phpMyAdmin, which is included with most hosting control panels. More details and links to further explanations are [here](http://codex.wordpress.org/Restoring_Your_Database_From_Backup). |
|
37 |
|
38 = Why can't I schedule automatic backups to be saved to my server? = |
|
39 |
|
40 Although WP-DB-Backup provides the option of saving the backup file to the server, I strongly discourage anyone from leaving backed-up database files on the server. If the server is not perfectly configured, then someone could gain access to your data, and I do not want to make it easy for that to happen. |
|
41 |
|
42 = My backup stops or hangs without completing. = |
|
43 |
|
44 If you edit the text of wp-db-backup.php in a text editor like Notepad, you’ll see around line 50 the following: |
|
45 |
|
46 `/** |
|
47 * Set MOD_EVASIVE_OVERRIDE to true |
|
48 * and increase MOD_EVASIVE_DELAY |
|
49 * if the backup stops prematurely. |
|
50 */ |
|
51 // define('MOD_EVASIVE_OVERRIDE', false); |
|
52 define('MOD_EVASIVE_DELAY', '500');` |
|
53 |
|
54 Do what it says: un-comment MOD_EVASIVE_OVERRIDE and set it to true like so: |
|
55 |
|
56 `define('MOD_EVASIVE_OVERRIDE', true);` |
|
57 |
|
58 That will slow down the plugin, and you can slow it even further by increasing the MOD_EVASIVE_DELAY number from 500. |
|
59 |
|
60 Better yet, put the lines that define the `MOD_EVASIVE_OVERRIDE` and `MOD_EVASIVE_DELAY` constants in your wp-config.php file, so your settings don't get erased when you upgrade the plugin. |
|
61 |
|
62 = What is wp-db-backup.pot for? = |
|
63 |
|
64 This files is used by non-English users to translate the display into their native language. Translators are encouraged to send me translated files, which will be made available to others here: |
|
65 http://austinmatzko.com/wordpress-plugins/wp-db-backup/i18n/ |
|
66 http://plugins.trac.wordpress.org/browser/wp-db-backup/i18n/ |
|
67 |
|
68 = Why are only the core database files backed up by default? = |
|
69 |
|
70 Because it's a fairly safe bet that the core WordPress files will be successfully backed up. Plugins vary wildly in the amount of data that they store. For instance, it's not uncommon for some statistics plugins to have tens of megabytes worth of visitor statistics. These are not exactly essential items to restore after a catastrophic failure. Most poeple can reasonably live without this data in their backups. |
|
71 |
|
72 == Usage == |
|
73 1. Click the Tools or Manage menu in your WordPress admin area. |
|
74 1. Click the Backup sub-menu. |
|
75 |
|
76 1. The plugin will look for other tables in the same database. You may elect to include other tables in the backup. |
|
77 ** NOTE ** |
|
78 Including other tables in your backup may substantially increase the size of the backup file! |
|
79 This may prevent you from emailing the backup file because it's too big. |
|
80 |
|
81 1. Select how you'd like the backup to be delivered: |
|
82 * Save to server : this will create a file in /wp-content/backup-*/ for you to retreive later |
|
83 * Download to your computer : this will send the backup file to your browser to be downloaded |
|
84 * Email : this will email the backup file to the address you specify |
|
85 |
|
86 1. Click "Backup!" and your database backup will be delivered to you. |
|
87 |
|
88 The filename of the backup file will be of the form |
|
89 DB_prefix_date.sql |
|
90 DB = the name of your WordPress database, as defined in wp-config.php |
|
91 prefix = the table prefix for this WordPress blog, as defined in wp-config.php |
|
92 date = CCYYmmdd_B format: 20050711_039 |
|
93 the "B" is the internet "Swatch" time. |
|
94 See the PHP date() function for details. |
|
95 |
|
96 When having the database backup emailed or sent to your browser for immediate download, the backup file will be _deleted_ from the server when the transfer is finished. Only if you select delivery method "Save to server" will the backup file remain on your server. |
|
97 |
|
98 *** SECURITY WARNING *** |
|
99 Your database backup contains sensitive information, |
|
100 and should not be left on the server for any extended |
|
101 period of time. The "Save to server" delivery method is provided |
|
102 as a convenience only. I will not accept any responsibility |
|
103 if other people obtain your backup file. |
|
104 *** SECURITY WARNING *** |
|
105 |
|
106 == Changelog == |
|
107 |
|
108 = 2.2.3 = |
|
109 * Nonce check fix for localized WP users from Sergey Biryukov |
|
110 * Fix for gzipped files' incorrect size. |
|
111 * Some styling improvements. |
|
112 * Fix for JS multiple checkbox selection. |
|
113 |
|
114 == Upgrade Notice == |
|
115 |
|
116 = 2.2.3 = |
|
117 * Fixes problems users had when using localized WordPress installations. |
|
118 * Fixes a bug that caused the size of gzipped backup files to be reported incorrectly. |
|
119 |
|
120 == Advanced == |
|
121 If you are using WordPress version 2.1 or newer, you can schedule automated backups to be sent to the email address |
|
122 of your choice. |
|
123 |
|
124 == Translators == |
|
125 Thanks to following people for providing translation files for WP-DB-Backup: |
|
126 * Abel Cheung |
|
127 * Alejandro Urrutia |
|
128 * Alexander Kanakaris |
|
129 * Angelo Andrea Iorio |
|
130 * Calle |
|
131 * Daniel Erb |
|
132 * Daniel Villoldo |
|
133 * Diego Pierotto |
|
134 * Eilif Nordseth |
|
135 * Eric Lassauge |
|
136 * Friedlich |
|
137 * Gilles Wittezaele |
|
138 * Icemanpro |
|
139 * İzzet Emre Erkan |
|
140 * Jong-In Kim |
|
141 * Kaveh |
|
142 * Kessia Pinheiro |
|
143 * Kuratkoo |
|
144 * Majed Alotaibi |
|
145 * Michał Gołuński |
|
146 * Michele Spagnuolo |
|
147 * Paopao |
|
148 * Philippe Galliard |
|
149 * Robert Buj |
|
150 * Roger |
|
151 * Rune Gulbrandsøy |
|
152 * Serge Rauber |
|
153 * Sergey Biryukov |
|
154 * Tai |
|
155 * Timm Severin |
|
156 * Tzafrir Rehan |
|
157 * 吴曦 |
|
158 |
|
159 == Past Contributors == |
|
160 skippy, Firas, LaughingLizard, MtDewVirus, Podz, Ringmaster |