Healthchecks VS kopia

Hey mate, I'm using https://healthchecks.io/ for heartbeat monitoring my crons. It's been working flawlessly for quite some time now. The UI is super clean and easy to navigate. It's also free up to 20 monitored jobs. Note - I'm not in any way related to that project.

In fact, your platform (https://healthchecks.io/) is a prime example of where running customer wasm would be really excellent.

Instead of sending webhooks out to customer configured URLs, you could run a Wasm environment to execute customer code. Off hand, a good use case here is to do further inspection of the event before it gets sent off to some other system - maybe there are cases where you send false-positives and needlessly trigger external system alerts. The customer Wasm could do more introspection on the healthcheck event and make a more informed decision about how to proceed.

i use healthchecks.io and have been very happy

Is there anything different from https://healthchecks.io/ --- a service I've been using for free for a couple years now?

Because of this block on the router, and the fact that IPv6 connections are by default preferred over IPv4, many things on the system now cannot access the internet. the only things that can access the internet are for accessing servers that ONLY support IPv4 like my mail.smpt2go or my uptime monitoring scripts for healthchecks.io.

i use https://healthchecks.io/ and highly recommend it.

We use a heartbeat system. Basically the monitoring continuously sends an alert to a healtcheck system. If that heartbeat fails, PagerDuty sends an alert to the oncall.

i like healthchecks.io

I think Kopia would be great for your use case

https://kopia.io/

It has a great system to snapshot files but only store data if it's changed. I use it in an environment where I can't use something like zfs to snapshot data because I don't have the ability to make decisions about what filesystem we're using. It's been amazing, love it so much!

Thanks for the tip on Kopia. Setting it up now, looks perfect.

https://github.com/kopia/kopia

Kopia - GitHub

I've been happy with: https://kopia.io/

Fairly easy to configure, does snapshots to S3 and has a icon in my tray I can watch :)

Btw, kopia is one fine backup tool. Apparently borgbackup is good too.

Kopia is great, though it's worth noting for folks on Linux: non-UTF-8 paths aren't stored correctly [1] and xattrs aren't stored [2]. While most folks probably won't care about the former, the latter can could cause issues (eg. losing SELinux labels makes it difficult to restore a backup of the root filesystem on distros that use SELinux).

[1] https://github.com/kopia/kopia/issues/1764

[2] https://github.com/kopia/kopia/issues/544

I think Kopia [1] is on its way to be that. I am sticking to Restic for now but it seems like the strongest contender.

[1]: https://github.com/kopia/kopia

I used their trial for a bit to test it out with Vorta [1] in a container. Vorta (and Borg) seemed to work fine, until I wanted to restore an archive and I noticed that my recent snapshots were completely empty. Probably because of a misconfiguration on my end though. But it made me look elsewhere. For me backups should be a fire, test and forget solution.

Recently I made the switch to Kopia [2] which seems to have feature parity with Borg (and Restic [3]). It also has a web UI which is way easier to work with than Vorta. And I can easily view, extract and restore individual files or folders from there. This gave me way more confidence about this solution. The only thing I really miss is that I cannot chose different targets for different paths. For instance, with Borg I was able to backup a partial of my Docker appdata to an external source. And I haven't found a way to do this with Kopia. Besides that I'm pretty happy with this solution and I would recommend it.

1. https://vorta.borgbase.com/

2. https://kopia.io/

3. https://restic.net/

There's a few. Off the top of my head

https://github.com/kopia/kopia