• I plan on using multiple WordPress installs to give the appearance of having more than one blogs (or blog-like pages) on my web.

    I see I can either do this by using one database for them all or one per install. I can do either and don’t mind the installing, but which would be handier for maintenance and especially backups?

    For the page I currently have, which uses WordPress, I’ve used that handy backup plugin. Well, I like it but I’ve never had the need to restore the database.

Viewing 4 replies - 1 through 4 (of 4 total)
  • I, personally, find it easier for backups with multiple blogs in one database. Others may have different opinions though.

    The built-in backup plugin will get ’em all if you manually check all the boxes for the other blogs’ tables.

    You might look overInstalling_Multiple_Blogs.

    Thread Starter Kalli

    (@kalli)

    Thanks, I had already looked that one over. The question of maintenance was the big thing.

    I’m guessing that restoring the databases will not be a problem with this method?

    Restoring is easier this way — but keep in mind that by default you’ll restore ALL blogs in the db unless you go table by table.

    If you feel you’ll have more situations where you only want to restore one blog but not others (for whatever reason), then perhaps one db per blog then makes more sense.

    Thread Starter Kalli

    (@kalli)

    I think I’m getting the idea and I will go with one database. I’ve done a lot of backing up, but never needed to restore anything so I’ll rather have quick and easy backups. Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Multiple install database considerations’ is closed to new replies.