My strategy for photos is to place them in my Dropbox folder, and sync them to one box in particular but they also live on the Dropbox cloud (it also used to be that they end up on Flickr as they sometimes still do; Google Photos does backup in regular resolution stuff from my iPhone). All this gets backed up via various backup services (Backblaze, CrashPlan).
Lately, I’ve been wondering if that makes sense since Dropbox applies compression to my JPGs. I missed the announcement of Dropbox using Lepton image compression, but did read with great interest that Flickr is using it too – A Year Without a Byte.
Lepton “provides lossless, bit-exact storage for any type of photo, whether it be for archival purposes, or for serving live.” It is open source.
I understand it saves Dropbox countless petabytes. I just don’t like the idea that my images are being re-compressed without me knowing about it. It may be that other services do this too. But one thing is for sure – the moment its in my Dropbox folder, they reduce in size, and my backups are also getting said reduction. Sure it’s lossless, bit-exact storage. But I’m thinking about archival forever!
P/S: I’m going to guess this is why Dropbox doesn’t support Live Photos in Camera Uploads yet. They haven’t figured out how to save space…
A while back, I realised that com.apple.bird was getting too large and it was easy to purge it. I had to do this again.
The app I use to see where my space is going is OmniDiskSweeper. Its free, and I highly recommend it.
I use Arq to handle backups (in addition to Backblaze, and CrashPlan), and today I noticed that ~/Library/Arq/ had a huge (32.7GB) Cache.noindex. Apparently it is safe to delete, so that’s what I have done.
I also notice a large /Library/Backblaze.bzpkg – 8.1GB – and apparently you can’t delete it. The penalty you pay for keeping offsite backups?
Anyway, I suddenly have a lot more free space. Its annoying that I’ll have to keep track of all this from time to time, as one has to occasionally perform some housekeeping of one’s Mac.
Check out how Linden Labs, creators of the popular game Second Life, upgraded their MySQL database. The MySQL they use? Straight out of Debian! Of course, now, they’re running with the Percona patchset, against MySQL 5.0.84. Definitely a good read.
Its good to see Lars post about contributing to the MySQL replication & backup codebase. It sounds like the replication & backup team have decided that mentoring is the way to go – you get a “coach developer” if the idea is accepted. I like this very much, and sincerely hope it spreads to the rest of the server; it will help decentralise development of MySQL, and the endgame is a larger community.
While I know Christmas is over, The 12 Days of Christmas (MySQL Edition), is actually quite a fun watch :)
Happy New Year all!
A while back, Ted Ts’o asked for a incremental backup solution that used a database. It reminded me of the talk at the 2009 MySQL Conference & Expo, titled Build your own MySQL time machine.
Chuck and Mats will talk about the backup and replication code, and will show off a web interface, that allows you to go back in time, similar to Apple’s Time Machine in Mac OS X. Its a talk that I most certainly want to attend, as an avid Time Machine user.
for the MySQL Conference & Expo 2009 before February 16, and you’ll get an early bird discount (saving $200). April 20-23 2009 will be a rocking few days, see you there.