Discussion about this post

User's avatar
Vincent Harn's avatar

Thanks for sharing your backup strategy. Have you looked into Amazon S3 Glacier Deep Archive as a long term archive for past projects?

My backup strategy is similar when traveling. I'm not managing anywhere near as large of a dataset as you though.

1. Record to two SD/CFe cards when possible in camera.

2. At the end of the day copy SD/CFe to an external SSD.

3. Also copy the SD/CFe to cloud backup (if internet speeds allow).

4. I always have one copy on me and one in hotel (external SSD). When changing out SD/CFe cards, I keep one of the pair on me and the other in the hotel with the external SSD. If one gets stolen, it's unlikely I'll lose both copies. If for whatever reason I do, there's the cloud copy.

5. Back at home, copy SD/CFe to desktop NVMe SSD. NVMe SSD is synced to a NAS. NAS does another backup on schedule to Backblaze B2.

I don't wipe my SD/CFe cards or the SSD used for backup in the field until preparing the next assignment.

I also can't afford Backblaze B2 to have a hot copy of all my files. When I'm done with projects for the year, I archive them all into .tar files, compute sha256 checksums, and upload in 5GB chunks into Amazon S3 Glacier Deep Archive. It's very much more affordable to store in deep archive than having cloud data hot. Recovering from this would be a last resort and I am okay with paying the restoration costs.

Aaron Bludworth's avatar

Very similar:

1- Dual cards with DNG to both when using a camera that is capable

2- SSD backup when remote (clear when moved to RAID at office)

3- Working copy local on MacBook until done editing and/or delivered

4- G-RAID (SSD and spinners) when back to office

5- RAID backed up to cloud on Backblaze (insanely affordable)

Thanks for sharing your system.

3 more comments...

No posts

Ready for more?