Today is Backup Awareness Day! [en]

Two months ago, on February 24th, I hit the wrong “Drop” button in PhpMyAdmin, resulting in the immediate deletion of the blog you’re reading. I didn’t know when I had last backed it up.

The story ends well, though it cost me (and others) many hours (days, actually) of work to get the whole of Climb to the Stars back online again.

I’ve always been careless about backups. Like many of you, probably. We can afford to be careless because accidents don’t happen very often, and as with Black Swans, we are under the mistaken belief that having been safe in the past will keep us safe in the future. Not so. As I like to repeat, the first time a disaster happens, well, it had never happened till then.

So, I’ve decided to declare the 24th of each month “Backup Awareness Day”. Here’s what it’s about:

  • Back up your files.
  • Back up your website.
  • Blog about the importance of backing up (sharing tips, stories, advice).
  • Tell your friends to back up.
  • Help your friends back up.
  • Put in place automatic backup systems.

Bottom-line: decrease the number of people who never back up, or back up so infrequently they’ll be in a real mess if things go wrong.

Now, perfectionism is the biggest enemy to getting things done. Backup Awareness Day does not mean that you have to do all this. Here are a few ideas to get your started (better a bad backup than no backup at all):

  • If Time Machine (or any other regular backup system you use for your computer) has been telling you it hasn’t done a backup in ages, stop what you’re doing right now and plug it in.
  • If you use WordPress, when was the last time you went to Tools > Export to make a quick backup? It’s not the best way to do it, but in my case, it saved CTTS.
  • Do you use something like Mozy to have a remote backup of your most important files? Time to sign up, maybe.
  • Are you working on important documents that exist only on your computer, which is never backed up? At the minimum, pick up a thumb drive and copy them onto it — or send yourself an e-mail with the files as attachment, if your e-mail is stored outside your computer (Gmail, for example).
  • Do you have an automatic backup set up for your database or website? Set some time aside on Backup Awareness Day to figure out cron.
  • When did you make the last dump of your MySQL database? Head over to PhpMyAdmin, or the command line (it’s mysqldump --opt -u user -p databasename > my-dirty-backup.sql)
  • Do you have the backup thing all figured out? Write a post for your readers with a few tips or tutorials to help them along. (Tag your posts “backupawarenessday” — I thought about “BAD” but that wasn’t really optimal ;-))

I’m hoping to develop the concept more over the coming months. If you have ideas, get in touch, and take note of Backup Awareness Day for the month of May: Sunday 24th!

(Now stop reading and go do a few backups.)

PJW Blogminder Plugin for WordPress [en]

[fr] J'en rêvais, on m'a prise au mot: un plugin qui vous envoie une alerte si vous n'avez pas publié quoi que ce soit sur votre blog depuis x jours (entre un et sept jours). Histoire d'éviter que la semaine entière passe sans s'en rendre compte!

A few days, ago, I was dreaming out loud on Twitter about a plugin which would let me know when I hadn’t published anything on my blog after a certain number of days. I guess that, once again, I’d reached the end of a week and realised that I had not written a single thing on CTTS.

Well, my wish was heard, and Peter Westwood has just released the PJW Blogminder plugin. The plugin adds a simple option to your profile page, where you can request a reminder if you haven’t published anything in the last few days (set the number of days between one and seven).

Blogminder screenshot

Nice!

(Now I just need to get my server to send mail… ahem.)

WordPress on my iPhone [en]

Wow, just checking out the new WordPress iPhone app. It now allows comment moderation management, post and page editing, as well as saving non-local drafts. I’m going to start using it regularly… Though maybe not for writing my usual unending posts for CTTS!

Progress in Restoring CTTS [en]

[fr] Voilà, après la destruction involontaire de mon blog il y a une dizaine de jours, j'ai pu remettre en ligne tous les articles écrits avant le 25 octobre. Le reste suivra en cours de semaine.

After the big blogging disaster, I had a pretty busy week (it was a bad one too, but let’s not dwell on that).

I have now restored all posts and content published before October 25, the last post being about Qwitting Qwitter (remember that one?). Pages are back too, and I’ve put a Pages widget here in the right column so you can access them.

The rest of the content will follow, on Tuesday, normally. With comments.

One side-effect of the import is that I have also “recovered” (haha!) all the duplicate comments that the Disqus plugin inserted in my database. I removed them sometime in January, and this time, unfortunately, removal will not be so simple: the “DISQUS” comment agent I used to identify them got lost in the export-import process.

Ah, and it looks like my categories are an even bigger mess than before: most of them seem duplicated. Maybe it’s time to cut my losses, convert them all the tags, and wipe the slate clean.

Disqus Plugin Aftermath: Removing Duplicate Comments [en]

[fr] Comment se débarrasser de 5000 commentaires à double dans sa base de données WordPress!

Now that Disqus integrates Friendfeed comments, I could be tempted to give it another try, if I hadn’t spent an hour yesterday cleaning up my database because of an earlier attempt to use Disqus on this blog. After the story, how I did it — in case you’re in the same mess and could use the help.

Back in August, I installed the Disqus plugin for WordPress. Things started off not too badly, though I was a bit concerned that the plugin seemed to have duplicated all the comments in my database. It didn’t seem to show up on the blog though, so I didn’t worry too much.

After a few months, I was a bit frustrated with Disqus and the plugin (which was clearly an older version than the Disqus plugin available now). Moderating comments through the WordPress interface seemed to work erraticly, and some spam just wouldn’t accept to stay in the spambox. I never really tried to identify the exact problems too closely, I have to admit, but things were not really working how I expected them to.

Then a few (unrelated) people told me they had completely failed to comment on my blog with the new system. At some point, I got fed up and uninstalled it. Unfortunately, the duplicate comments which had been hidden from view remained there after uninstalling the plugin, so all the old comments appeared on the blog twice. I let the problem sit for a long time before attempting to fix it — wild hope there might be a ready-made script out there I could just run& in vain.

Here’s how I tackled the problem this week-end and ended up removing the duplicate comments without too much trouble, through PhpMyAdmin (PMA for short).

  • In PMA, I made sure that duplication seemed constant — it was
  • I discovered that the duplicate comments had “DISQUS” in the user-agent field
  • I dug around until I identified the last duplicate comment (when I installed the Disqus plugin, actually; I sorted the database comments table by comment date to do that)
  • I did a search, selecting comments which were younger than the last duplicate comment date AND had “DISQUS” in the user-agent field (the date bit is important, because comments posted while the plugin were active have “DISQUS” in the user-agent field but are not duplicates)
  • Then, I deleted everything that came up in the search — about 5000 comments (it helps to tell PMA to display 3000 lines per page when doing that :-))

Hope this can help somebody, and remember: always back up your database first!