1 | === WP-DB-Backup ===
|
---|
2 | Contributors: filosofo, skippy, Firas, LaughingLizard, MtDewVirus, Podz, Ringmaster
|
---|
3 | Donate link: http://www.ilfilosofo.com/blog/wp-db-backup/
|
---|
4 | Tags: mysql, database, backup, cron
|
---|
5 | Requires at least: 2.0.3
|
---|
6 | Tested up to: 2.7
|
---|
7 | Stable tag: 2.2.2
|
---|
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) 2008 Austin Matzko
|
---|
21 |
|
---|
22 | == Installation ==
|
---|
23 | 1. Copy the wp-db-backup.php 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 | = My backup stops or hangs without completing. =
|
---|
39 |
|
---|
40 | If you edit the text of wp-db-backup.php in a text editor like Notepad, youâll see around line 50 the following:
|
---|
41 |
|
---|
42 | `/**
|
---|
43 | * Set MOD_EVASIVE_OVERRIDE to true
|
---|
44 | * and increase MOD_EVASIVE_DELAY
|
---|
45 | * if the backup stops prematurely.
|
---|
46 | */
|
---|
47 | // define('MOD_EVASIVE_OVERRIDE', false);
|
---|
48 | define('MOD_EVASIVE_DELAY', '500');`
|
---|
49 |
|
---|
50 | Do what it says: un-comment MOD_EVASIVE_OVERRIDE and set it to true like so:
|
---|
51 |
|
---|
52 | `define('MOD_EVASIVE_OVERRIDE', true);`
|
---|
53 |
|
---|
54 | That will slow down the plugin, and you can slow it even further by increasing the MOD_EVASIVE_DELAY number from 500.
|
---|
55 |
|
---|
56 | 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.
|
---|
57 |
|
---|
58 | = What is wp-db-backup.pot for? =
|
---|
59 |
|
---|
60 | 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:
|
---|
61 | http://www.ilfilosofo.com/blog/wp-db-backup/i18n/
|
---|
62 | http://dev.wp-plugins.org/browser/wp-db-backup/i18n/
|
---|
63 |
|
---|
64 | = Why are only the core database files backed up by default? =
|
---|
65 |
|
---|
66 | 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.
|
---|
67 |
|
---|
68 | == Usage ==
|
---|
69 | 1. Click the Manage menu in your WordPress admin area.
|
---|
70 | 1. Click the Backup sub-menu.
|
---|
71 |
|
---|
72 | 1. The plugin will look for other tables in the same database. You may elect to include other tables in the backup.
|
---|
73 | ** NOTE **
|
---|
74 | Including other tables in your backup may substantially increase the size of the backup file!
|
---|
75 | This may prevent you from emailing the backup file because it's too big.
|
---|
76 |
|
---|
77 | 1. Select how you'd like the backup to be delivered:
|
---|
78 | * Save to server : this will create a file in /wp-content/backup-*/ for you to retreive later
|
---|
79 | * Download to your computer : this will send the backup file to your browser to be downloaded
|
---|
80 | * Email : this will email the backup file to the address you specify
|
---|
81 |
|
---|
82 | 1. Click "Backup!" and your database backup will be delivered to you.
|
---|
83 |
|
---|
84 | The filename of the backup file will be of the form
|
---|
85 | DB_prefix_date.sql
|
---|
86 | DB = the name of your WordPress database, as defined in wp-config.php
|
---|
87 | prefix = the table prefix for this WordPress blog, as defined in wp-config.php
|
---|
88 | date = CCYYmmdd_B format: 20050711_039
|
---|
89 | the "B" is the internet "Swatch" time.
|
---|
90 | See the PHP date() function for details.
|
---|
91 |
|
---|
92 | 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.
|
---|
93 |
|
---|
94 | *** SECURITY WARNING ***
|
---|
95 | Your database backup contains sensitive information,
|
---|
96 | and should not be left on the server for any extended
|
---|
97 | period of time. The "Save to server" delivery method is provided
|
---|
98 | as a convenience only. I will not accept any responsibility
|
---|
99 | if other people obtain your backup file.
|
---|
100 | *** SECURITY WARNING ***
|
---|
101 |
|
---|
102 | == Advanced ==
|
---|
103 | If you are using WordPress version 2.1 or newer, you can schedule automated backups to be sent to the email address
|
---|
104 | of your choice.
|
---|
105 |
|
---|
106 | == Translators ==
|
---|
107 | Thanks to following people for providing translation files for WP-DB-Backup:
|
---|
108 | * Gilles Wittezaele
|
---|
109 | * Ä°zzet Emre Erkan
|
---|
110 | * Michele Spagnuolo
|
---|
111 | * Rune GulbrandsÞy
|
---|
112 | * Sergey Biryukov
|
---|
113 | * Tai
|
---|
114 | * Timm Severin
|
---|
115 | * åŽæŠ
|
---|