Sync is not backup, backup is not sync.

I had an issue - nothing new - with the backups - ouch - and this time it was my fault one hundred percent.

Days ago I've bought a Raspberry Pi, just to have fun with the possibilities (media center, retro games, download center...) you can do almost everything you can imagine. One of the ideas I had was to create a usb softraid with 2 external usb drives and add the raspi as Syncthing node, because I'm using syncthing across some nodes to sync essential data, as backup (*err*).

While playing with the usb drives I noticed that the raspi was not able to feed both disks because of the limited voltage. It was running perfectly fine with one external disk but when attaching the second one we got weird noises in drives. Crazy.

Even crazier when noticed myself that syncthing was not down while playing with this stuff. And the craziest was to check that I've lost data in this process. It seems that something really weird happened to the main disk when attaching second one and it was like some folders just dissapeared.

I was able to recover all the data - or I think so - because I unexpectedly had a syncthing node that was down. It was what saved me this time. Moral of the fable: sync does not mean backup and viceversa.

I had to review the backup policy and just tune up the nodes making some completes and incremental data backups. Tools I've been using: rdiff-backup, duplicity, duply and syncthing.

I've not finished yet but I think I did an further improvement of what I had. Time will tell. You just remember: Sync is not backup and backup is not sync.


About the author

has doubledaddy super powers, father of Hugo and Nico, husband of Marta, *nix user, Djangonaut and open source passionate.
blog comments powered by Disqus