Hot answers tagged

10

"the boring work of backup"... Backups may be boring, but they are essential and gives you a fallback position in case things go wrong. Without backups, you're essentially playing Russian roulette with your site. It doesn't even take very long, and reverting isn't horrible or awful, it's pretty easy. WP veterans take backups, test upgrades on non-...


9

I've personally had limited success with the backup/restore plug-ins that are commonly available. Many times, the best backup plug-ins don't allow for a direct restoration from a backup file. So I do things manually. It's a bit more difficult, but far more reliable, too. Backing up with phpMyAdmin Log in to your host's control panel (it might be cPanel,...


7

I recommend rsync. It only transfers what has changed since your last rsync so subsequent updates are very fast, and it works over SSH. Sample usage in crontab: # backup rsync from example.com every morning 14 3 * * * rsync -az example.com:/var/www/example.com/htdocs/ ~/Backup/example.com/ The -a flag preserves many aspects of the original file (ie. ...


6

BackWPup has a lot of flexibility in timing, what to backup (down to the DB table level), and it can store to DropBox which would put it on your computer.


5

I've been doing this successfully with csync and an NDB cluster for years... Re other solutions: rsync works too, albeit slower. (Much, much slower; slow enough to rule out any file-based caching.) InnoDB/MyIsam master/slave works too, with HyperDB. But, you'll end up with a need to manage other stuff, namely auto-increments on write servers, if you need ...


5

There is a significant amount of memory usage if you use the $wpdb for queries that return very large result sets. $wpdb loads the entire results from any given query into memory. So if you're, say, selecting all the posts, then it'll try to load the whole thing into memory immediately. So for something like a backup plugin, direct calls to mySQL with loops ...


4

Since you guys haven't mentioned it yet then i'll have to BackWPup a free site and database backup plugin packed with features and easy to configure Database Backup WordPress XML Export Optimize Database Check\Repair Database File Backup Backups in zip,tar,tar.gz,tar.bz2 format Store backup to Folder Store backup to FTP Server Store backup to Amazon S3 ...


4

Updating is always important. They contain security fixes and other bug fixes. Generally update within the 3.0x considered safe. Moving between 3.x could require some changes and updates to your theme or plugins. I like to take the mantra, better safe than sorry. I would back up your database and anything your wp-content folder (plugins, uploads and themes)...


4

If it is an older version of WP, you need to find out what version of WP generated the database, as WP upgrades the DB most times the files are upgraded and you should incrementally upgrade to also upgrade the database. Look in the wp_options table for option 711 and see what the version is; option name will be site_transient_update_core and the value will ...


4

There is a plugin called WP-DB-Backup http://wordpress.org/extend/plugins/wp-db-backup/ You can configure it to email you a backup of your blog at a specific interval.


4

On your old site go to Tools > Export in the admin area. You can select what you want to export. In your case "Posts." Click Download Export File On the new site you'll go to: Tools > Import > WordPress You'll have to hit a button to install the core plugin, but you can remove it after the import. Import the file you downloaded from the old site....


3

I do backups via shell (see Grep and Friends for some commands and examples). File and database backup runs within seconds even on larger sites and stuff is easy to restore. No need to worry about backups and upgrade crashes at all. In a perfect world all plugins and themes would have been already tested with the new WP version before I upgrade, well, but ...


3

I am using Automatic WordPress Backup and it works well. It let's you schedule it and it takes both the database and the filesystem. Let me know if it works for you.


3

I think HTML mirror is the way to go here. There is no point keeping dynamic site that doesn't need to be. And leaving it unmaintained is not really possible on auto-pilot - even if updates are automatic there is no guarantee some plugin won't get just dropped by developer. Alternatively you can build multi-design site. It's not that hard to load ...


3

I've seen a bunch of ways of doing this, but here are a couple: Use a plugin, like BackupBuddy (paid): http://pluginbuddy.com/purchase/backupbuddy/ Export your whole DB using phpMyAdmin and run a search-and-replace tool that properly deals with the serialized data, e.g. https://interconnectit.com/products/search-and-replace-for-wordpress-databases/ (I use ...


3

phpMyAdmin is software typically installed by your host and available via your hosting control panel, it is not part of WordPress. A search on web for [your host] phpMyAdmin will probably tell you what you need to do.


3

If you still have access to your wife's blog, I would recommend: Running a regular WordPress export of the content Downloading the entire /wp-content directory over FTP These are the two most important parts of the site - the content and the uploads. From this, you should be able to recreate the site on a clean installation by FTPing the uploads to the ...


3

There are several back-up plugins. The simplest procedure is for the back-up to include the xml export file as then it can easily be imported into another WordPress installation. One plug-in that does this is BackWPup (http://wordpress.org/extend/plugins/backwpup/). You can set it to email you a back-up at regular intervals. It is highly customizable. ...


3

And when I need to restore, I do a search replace in the sql file all localhost to that dns... Doing a find/replace in a text dump of the database will break the serialized data stored in theme options. Use interconnectit.com WordPress Serialized PHP Search Replace Tool to correctly find/replace serialized data. Some simple themes without options don't ...


3

In essence: This is almost correct. Exporting/Saving your database handles all options, settings, configuration, and content. The other thing is saving all the neccessary files. In general, all you need (unless you have altered anything else) is: wp-config.php file; /wp-content folder. Just the theme is not enough, as you also might want to backup the ...


3

You're damned if you do, and you're damned if you don't. But it's typically better to "do". I have been working in WordPress support and development for a number of years now - and I can certainly say it's much better to keep everything up to date. Wait a little bit (2 weeks or so) after major updates before making the change to allow time for maintenance ...


2

I would start by reading the sections in the Codex on WordPress Backups, Backing Up Your Database, and Restoring Your Database From Backup, to get a good understanding of the issues involved. There are a number of plugins written to automate the database backup process. Due to your webhost issue, you may have to just try a few to find one that works. I ...


2

Try looking in the {$prefix}_options table in the WordPress MySQL database


2

BackupBuddy works flawlessly for backing up to AmazonS3. FYI: it is a commercial Plugin, though.


2

always keep a local copy of your site that you can test any upgrades on first.


2

Backup Buddy is my absolute favorite. Features: db only backups full backups migration tool scheduled backups to email or remote server malware inspection http://pluginbuddy.com/purchase/backupbuddy/


2

I would now like to know if it is easily possible to update wordpress when I only have FTP-access and phpMyAdmin. WordPress has automatic update feature, that will do its best to perform update without you having to upload new version manually. It is not perfect, but it is quite robust and works on most configurations. If changes to database are required ...


2

Another way to seamlessly switch from localhost to live (for MS Windows): install WP on the live site. from your site control panel download a database copy and a site back-up of your files, and copy them to your localhost (for eg C:/wamp/www/) and import the db in your phpmyadmin; it's better to do this the other way around to make sure your live site ...


2

WP-Cli, definitively, as explained here. In you localhost: wp db export Upload the SQL file and the wp-content/uploads to your live server: wp db import <sqlfile> wp search-replace http://localhost http://live-location


2

You can use a plugin like backwpup that lets you: Store backup to Folder Store backup to FTP Server Store backup to Amazon S3 Store backup to Google Storage Store backup to Microsoft Azure (Blob) Store backup to RackSpaceCloud Store backup to DropBox (free) Store backup to SugarSync (free) and manage the number of backup copies to store which means for ...



Only top voted, non community-wiki answers of a minimum length are eligible