Skip to main content

Apple Photo is still uploading

I'm still trying to upload all of our photo and video artifacts. We have 53K photos and 3k videos which are about 250GB is size. Because of the Apple opinion on how and where to store these artifacts we are stuck with iCloud. The process of syncing her Apple iPhone, gmail and desktop are just so messed up that we are bound to lose something else before I get these pictures sync'd.

After our last failure I decided to backup out picture to 3 places.

  • backblaze - intelligent FULL system backups
  • Google+ - into a private folder in a smaller resolution just as a last resort since the resolution is lower
  • iCloud - because it's Apple's native solution and includes syncing from the phone to the desktop over the air
The problem with these services is that it is point in time. If you update or delete your files locally then they will be reflected in the backup. There is no delete nothing solution. Also, those ransomeware assholes are likely to corrupt the backups as the service cannot tell if the crypto is intentional or not; and by the time all of that is sorted out it's going to be to late.

Synology has some interesting devices and tools. The problem here is that it and some of the others do not consider that the local device may not have sufficient storage to hold everything except a project or two. And then the same challenges reappear.

This a complicated and potentially expensive problem. You'd think that we'd have it solved by now. Personally I do not want to be tethered to Apple. I like their computers and elements of their operating system. On the one hand I would like a closed system as I have been enjoying my Chromebooks an Chromebox but Apple has not actually achieved that level yet. iPads are still single user.


Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…