What can/should I do to protect, secure, backup, etc.?
Earlier in this series, I answered the question about migrating to a different host. In that article, I gave an overview on how to backup your database.
Technically, you can use the same instructions to backup your blog. Do a database dump via phpMyAdmin (ask your host if you don’t know how to use this) and FTP your files down. You could also, if your adept and have the necessary SSH access, setup a cron job to run a script that will dump your database and archive it along with all your files on a daily or weekly basis.
It might seem like I’m dodging this question, but that is only due to the fact that there are lots of ways to do this.
Instead, I’ll talk about backups in general. Whenever you make any major changes to your blog ecosystem, you should back up your database. That means, whenever you upgrade, move to a new host, close down a blog - back up! You don’t know if you’ll need that data again.
Failure to backup, and subsequently messing something up, does not constitute a WordPress problem. :-)
Table of contents for WordPress FAQ
- WordPress FAQ: How Do I combine Blogs?
- WordPress FAQ: What’s up with the Amazon Plugin with WP 2.1.x?
- WordPress FAQ: How Do I Use Category Themes?
- WordPress FAQ: Where did my Preview Link Go?
- WordPress FAQ: How Do I Use Child Pages More Effectively?
- WordPress FAQ: How Do I Fix the Blogroll Category Issue in WordPress 2.1
- WordPress FAQ: How do I Move my blog to a new host?
- WordPress FAQ: User Roles Confusion
- WordPress FAQ: What is the best way to upgrade a WordPress 1.5 blog to WordPress 2.1?
- WordPress FAQ: Democracy Poll Feature
- WordPress FAQ: Benefits of Tagging
- WordPress FAQ: What’s the Best Way to Backup my Blog?
- WordPress FAQ: How Do I Integrate WordPress Into a Non-Blog Site?
- WordPress FAQ: Troubleshooting a WordPress Install




Add New Comment
Thanks. Your comment is awaiting approval by a moderator.
Do you already have an account? Log in and claim this comment.
Add New Comment