Hacker News new | ask | show | jobs
by mceachen 2409 days ago
Where does this second backup live: cloud, or local? You might want to clarify that on your website.

If it's local, I wouldn't make it tiered by library size.

I think you're being perhaps optimistic with your $15/mo tier. I'd love to be wrong, but that money would pay for a new 10 TB HD every year. Maybe other people won't think that way? Are you using s3? Your costs might be lower using glacier or backblaze.

You should also take a look at https://github.com/mholt/timeliner. Open source, easy to install, runs locally for free. Worked perfectly on my very large library.

However, both your service and timeliner have to deal with Google Photos and the file mangling they do. Most tags are deleted, and several are modified (!!?) when you fetch them via takeouts or timeliner. I don't think there's anything you can do about it, because you're downstream of where the damage happens.

Good luck! You should try PhotoStructure, BTW. Link in my profile.

1 comments

We're using Wasabi for storage (wasabi.com) They offer S3 compatible hot storage at at fraction of the cost of AWS or any other cloud storage service.

Timeliner looks cool, but tools such as this are only suitable for the tech-savy crowd. I think there certainly is a market for these sorts of things, and PhotoStructure should be a good fit for those who want to keep thier data local.

Pixaver is targeted toward the vast majority of Google Photos users who don't have a technical background or the desire to maintain local physical backups. Backups running with just a few clicks and they don't to think about buying hard drives or fiddling with code.

As you mention, the data provided by the Google Photos API is sometimes not ideal. Geolocation data and some other metadata are omitted. Currently, only the "optimized" version of videos are provided. That said, our service is not meant as a replacement for Google Photos. We just want to be a way to get your images back if the unthinkable were to happen.