Storage

To better understand my positions about this topic and their reasons, it would be useful to read my experience with data loss.



Needs

  1. Durability: I want to be able to effortlessly access all of my data now as 30 years from now.
  2. Reliability: my storage system has to be absolutely fail-proof (of course, no system is. I need to achieve the best reliability I can afford). I cannot lose any of my data again.
  3. Scalability: the amount of pictures collected and stored by everyone in the world is growing at a tremendously fast pace, my pictures are no exception. I would prefer not to end up stuck in a resources consuming framework which is great with 2TB of pictures, but makes 10TB of pictures unmanageable.
  4. Affordability: I should not spend too much on this. In the end, shooting pictures is not my job (yet).
  5. Accessibility: if possible, I would like to be able to access all of my pictures from anywhere anytime.
  6. Portability: the system I choose must be as bare-bones and simple as possible, so that, if in the future I want to switch to a better one, I can do it as seamlessly as possible.
  7. Replicability”: why should my system work for me only? It would be ideal, by documenting everything, to make my final solution “replicable”, hence available to anyone as a source of inspiration. I am writing these words for this reason.


Doubts

  • Can I rely on flickr to piwigo alone to host all of my JPGs, even my private ones? No
    • is it reliable? How much do I risk of losing my data? Not too much. Not more reliable than any server around the world.
    • is it secure? Are my private pictures somehow server-side encrypted? No encryption. Not the best option to backup pictures
  • Does it make sense to use my cubbit’s 4TB for long-term picture storage? It does, as long as some features will be included
  • Should I use portable Hard Disks, as the ones I already have, or internal hard disks to plug to linuxplosion? None of the two, if the Cubbit solution works


Solution

The solution I found out to be working greatly up to now is the one described in importing workflow, which consists in setting a window of a few hours per week while linuxplosion is available to synchronize pictures and run tasks via SSH. In this way, storage is safely and redundantly backed up at home.

cubbit is the most promising long-term solution it lacks a crucial feature: it is not optimized for pictures (yet): albums and photo galleries are limited to folders and sub-folders, there is not even any support for tags.



Resources



RAID

On linuxplosion, I am considering to configure a RAID 1 storage system. Below, some notes about this.



Backup checklist
  • Export apps settings
  • Messaging apps (except Telegram and Matrix)
  • Images
  • Audios
    • Recordings
    • Important WhatsApp audios (which should be selected and separately saved at the time of reception)
  • Contacts (currently synchronized via iCloud)
  • WiFi passwords (currently synchronized via iCloud keychain)
  • Two Factor Authentication App (currently synchronized with KeePass via Cloud)


Importing workflow

Let’s be honest: importing and managing personal media without relying on big tech software is a stressful, itchy, and exhausting process. I am constantly trying to make it as simple, quick, and reliable as possible, but I am having a hard time. Below I noted some some of my experiments and the steps I currently follow.



Basically

  1. import everything in an isolated folder
  2. run DupeGuru (VIDEOS MANAGEMENT?)
  3. run [[Exiftool]]


Transferring files

Android

The cleanest way to move files from an Android to a MacOS device is by using ADB.

  1. Connect the phone to the computer;
  2. Open the terminal and move to the platform-tools folder (I keep in Documents): cd Documents/platform-tools;
  3. Check if the two devices are connected correctly by running ./adb devices;
  4. Navigate in the phone directories ./adb shell, ls -al;
  5. once the path of the directories which contain the content that has to be copied on the computer has been noted, execute ./adb pull /path/in/phone /destination/path/on/computer;
  6. Done. This is how simple, neat, fast, and powerful this process is.

iOS

I still haven’t figured the best way to transfer a lot of images from iPhone to MacOS. AirDrop is wonderful, but it cannot work with all of the photos and videos in my mobile gallery.


PhotoSync

To save pictures from my iPhone to [[Linuxplosion]] I use [[PhotoSync]]. Here are the key steps I performed to set everything up:

  1. make a desktop computer remotely reachable via SSH
  2. Importing pictures automatically via SFTP
  3. I configured PhotoSync so that directories based on date are automatically created.
  4. I set a weekly reminder to make me start the import when Linuxplosion [[Linuxplosion#Schedule|is scheduled to be on]]

Share

🏗 WIP section 🛠

This section should contain a beautifull graph displaying the relations among this note and all of the others on tommi.space. Unfortunately, showing it requires great coding skills and I am still working on it.

Comments

Webmentions

No webmentions were found.