It is always to backup any computer files that you value, and especially wise with your blog or website.
I recommend wp-db-backup because of its simplicity to set up, but currently have a few problems with a few sites which for a couple of reasons to not follow the default installation of wordpress. I’ll elaborate later, but am getting great support from the plugin authors so am using this as a diagnosis page for them.
How the backup fails
When the plugin is working properly on a site setup the default wordpress way, it will expect to backup your core tables and offer extra tables that have been added by plugins. They would be listed on the left and right of the backup screen respectively.
As you press the ‘Backup now!’ button to do the first unscheduled backup, some warnings and a progress bar will appear at the top of your screen. You know there is something wrong when the progress bar appears but it does not move beyond 0%!
Screenshot as the backup is started:
What causes the backup failure
WordPress ‘out of the box’
The default installation of wordpress is into a directory called wp. If you have a hosting package rather than run your own server then you often put your files in a directory called public_html.
So, if you run one wordpress site or blog, your files live in public_html/wp/ and the address of the home page of your blog is www.yourdomain/wp/index.php.
Other directory structures
There are several reasons why you do not want the default setup, and wordpress has allowed for this (see settings > general on your dashboard). For example:
- you want simple page addresses. My site for example lives in public_html/wp/ but because the whole site is based on wordpress, I want the home page of the site to be www.interweave-now.co.uk/ and not www.interweave-now.co.uk/wp/.
In this case in my settings > general the wordpress url is set as www.interweave-now.co.uk/wp and the site url reads www.interweave-now.co.uk/. The domain points to the public_html/wp
- you do not want to make it obvious you use wordpress, or have no need for other pages in the ‘root’ of your domain. Put the wordpress files into public_html/myblogname/ and point the domain to public_html/myblogname/
- you want something more personal than ‘wp’. For example, I have a site for members of a group and put wordpress in public_html/ourgroup/members/
So WordPress can adapt to your file structure and to a degree can separate the appearance in the browser address bar from the hierarchy of your directories. At the moment the plugin struggles with this but I expect it will be sorted very quickly.
Contact me if you need to discuss having a website or blog for your needs.