- September 2024 (1)
- August 2024 (2)
- July 2024 (2)
- May 2024 (2)
- April 2024 (2)
- February 2024 (2)
- April 2023 (1)
- March 2023 (2)
- September 2022 (1)
- February 2022 (1)
- November 2021 (1)
- March 2021 (1)
- February 2021 (2)
- August 2019 (1)
- November 2018 (1)
- May 2017 (1)
- December 2016 (1)
- April 2016 (1)
- August 2015 (1)
- December 2014 (1)
- August 2014 (1)
- March 2014 (1)
- December 2013 (1)
- October 2013 (3)
- September 2013 (4)
- August 2013 (2)
- July 2013 (1)
- June 2013 (1)
- February 2013 (1)
- October 2012 (1)
- June 2012 (1)
- May 2012 (1)
- April 2012 (1)
- February 2012 (1)
- October 2011 (1)
- June 2011 (1)
- May 2011 (1)
- April 2011 (1)
- March 2011 (1)
- February 2011 (1)
- January 2011 (1)
- December 2010 (3)
- November 2010 (1)
- October 2010 (1)
- September 2010 (1)
- August 2010 (1)
- July 2010 (1)
- May 2010 (3)
- April 2010 (1)
- March 2010 (2)
- February 2010 (3)
- January 2010 (4)
- December 2009 (2)
- November 2009 (5)
- October 2009 (2)
- September 2009 (2)
- August 2009 (3)
- July 2009 (1)
- May 2009 (1)
- April 2009 (1)
- March 2009 (5)
- February 2009 (5)
- January 2009 (5)
- December 2008 (3)
- November 2008 (7)
- October 2008 (4)
- September 2008 (2)
- August 2008 (1)
- July 2008 (1)
- June 2008 (1)
- May 2008 (1)
- April 2008 (1)
- January 2008 (5)
- December 2007 (3)
- March 2007 (3)
- February 2007 (1)
- January 2007 (2)
- December 2006 (4)
- November 2006 (18)
- 3D (5)
- AI (14)
- Admin (3)
- Blogging (5)
- Business of Software (9)
- Copyright (1)
- Dirigible (3)
- Django (1)
- Eee (3)
- Finance (6)
- Funny (11)
- GPU Computing (2)
- Gadgets (8)
- JavaScript (1)
- Linux (13)
- Memes (2)
- Meta (7)
- Music (4)
- NSLU2 offsite backup project (13)
- OLPC XO (2)
- Oddities (4)
- Personal (3)
- Politics (3)
- Programming (61)
- Python (36)
- PythonAnywhere (12)
- Quick links (2)
- Rants (4)
- Raspberry Pi (1)
- Resolver One (22)
- Resolver Systems (18)
- Robotics (8)
- Space (2)
- Talks (3)
- Uncategorized (5)
- VoIP (2)
- Website design (4)
Project: Automated offsite backups for an NSLU2 -- part 1
I have a Linksys NSLU2 on my home network, and I'm very pleased with it. It is almost silent, was not too tricky to set up, cost very little (and is even cheaper on Dabs these days), and it happily serves the contents of a 200Gb USB-connected hard disk to all of my PCs. But there's one problem; it would be easy for someone to steal. I was burgled a couple of years back, and while (thankfully) they missed the disk, I realised that while almost everything else in my flat is insured and replaceable, the data on that drive is not. I decided that I needed it backed up offsite automatically, so that even if my home was completely cleared out, my data at least would be safe.1
Shortly after the burglary, I set up a temporary solution, which - like all these things - has lasted for somewhat longer than intended. My media-centre PC is always on, and it runs IBackup, which synchronises the contents of the NSLU2 (mapped as several network drives) every night.
This approach has three problems:
- Cost of the service. IBackup charge $10/mo per 5Gb, which isn't bad by the standards of their competition, but is more than I really want to spend - especially given that my usage is getting pretty much near that 5Gb limit now. Costs go up in 5Gb increments.
- Cost of electricity. Leaving a PC on all the time costs more than you'd think. Our electricity bill at work comes to something like GBP 7 -- say, $12 -- per computer per month; domestic electricity is a bit cheaper, but that's still about as expensive as the storage. I don't know what the NSLU2's power requirements are precisely, but it's probably safe to say that it uses less than a full PC... (Update - It looks like it uses about 2.5W - see the table at the bottom of this page -- which is a couple of percent of a PC's power consumption.)
- Elegance. There's just something fundamentally wrong with getting a clever little NAS device to handle all of your shared disk space and then keeping a fully-blown PC running just so that the NAS disks are backed up. The server should handle its own backups - otherwise you might as well just share space out from the PC.
So, I need something better - cheaper, more power-efficient, and more elegant. Here's the plan: I want to find a decent supplier of offsite backup space, and to somehow put in place software to keep the contents of the NSLU2 synchronised with that space. I suspect getting this all sorted may take a while, and I'll keep detailed notes here.
Next: Where and how?
-
The NSLU2 does have the ability to automatically back itself up to another network drive - presumably it accesses the other drive using the same Windows SMB protocol it uses to share its own disks. If I wasn't looking for offsite backup specifically, this would have been quite useful -- good enough, at least, to protect against hard disk failures. ↩