Snapshot Backup 2.0 RC1 – Ready for Testing

- by

I’ve been slaving away at the keyboard again. It’s been too long, and you’ve all been patiently waiting for your favourtive backup plugin to do something while you sleep.

Say hello to Snapshot Backup 2.0 which can now create backups while you sleep. Here’s a list of new features:

  • Automation: create backups every hour, every day, every week, etc (relies on WP Cron so your site needs to have some traffic
  • Rolling Backups: only keeps x amount of Snapshots in your repository
  • New Menu Structure
  • Funky Branding

Before I release it next week, please let me know your feedback and any bugs you notice.

You can download it here:

https://wpguru.co.uk/wp-content/uploads/2011/07/snapshot-backup-20-rc1.zip

UPDATE: I have tested the RC-1 version for a couple of weeks now and it seems stable. Hence I’ve released it to the world this morning – RC-1 is identical to the 2.0 release on the Official WordPress Repository.

Have fun 😉



If you enjoy my content, please consider supporting me on Ko-fi. In return you can browse this whole site without any pesky ads! More details here.

6 thoughts on “Snapshot Backup 2.0 RC1 – Ready for Testing”

  1. Hi Jay,

    I just updated to v2.0 and I’ve found some issues with it… I don’t think you packaged /includes/snapshot-functions.php in the official 2.0 release. It is however in the RC-1 release. I’m also receiving a few other php errors, but that could be my doing trying to stitch this together. I’ll let you know if i find anything else. Other wise, thanks for the update!

  2. Thanks for letting me know Matt,

    It was all Subversion’s fault – I’m out and about at the moment but will fix this problem tonight. Sorry about this. The RC1 is pretty much identical to the full release BTW.

  3. Thanks for the update! I have found this to be one of the best Backup Plugins out there. I was having problems this morning after I had upgraded a blog to the latest WP version, but after installing the Snapshot update later on today it seemed to resolve the issue.

    Thanks again!

Comments are closed.