ntolia

Very different products and can't compare them. Veeam is enterprise-grade and used for a larger variety of mission-critical workloads. Kopia is meant for end-user backups (though folks use it for a bunch of other things too).

Note that Veeam contributes to Kopia - https://www.veeam.com/sys451

Unfortunately, this is not true. You need to grab all the DB files (WAL, etc.) in a consistent manner. You can't grab them while writes are in progress. There are ways though. Look at what Kanister does with its recipes to get consistent DB snapshots to get a sense of the complexities need to do it "right."

One thing I will mention is that other backup projects have switched from Restic to Kopia. Velero from VMware comes to mind.

However, you should be able to use Glacier Instant Access. It will get you a bunch of the way there.

I haven't looked at duplicati in a while and, it has evolved. While Duplicati's feature set looks similar now, I would need to benchmark it both for efficiency and final backup sizes.

And, while not directly, I know a number of companies, including mine, do test restores all the time.

I've been using Kopia for my personal use and for products I have helped build at a couple of enterprise backup companies! It's also used by other open-source backup projects that focus on specific ecosystems (Velero and Kanister for Kubernetes, Corso for Microsoft 365 backup).

I am obviously biased but it's pretty amazing. AMA.

Hey folks, let us know if you have any questions about Corso. Would love to hear more about what you like to see as the project evolves.

You know, this is a great question. I believe what ARM is pushing now is Scalable Vector Extension (SVE) as the successor to NEON. I haven't seen benchmarks in the wild yet but it does have promise.

You can see some of the performance differences here - https://blog.kasten.io/benchmarking-kopia-architecture-scale...

I ran some performance benchmarks not too long ago. https://blog.kasten.io/benchmarking-kopia-architecture-scale...

Kopia announced the 0.5 release of Kopia! This is a big milestone on the way to an upcoming 1.0 release. Apart from pluggable compression, deduplication, and encryption, this release includes expanded object storage support and an easy-to-use UI. Feedback welcome!

Apart from the announcements highlighted above, if you want a little bit more color and my take on the community, marketing vs. reality, and some of the tech-related controversy I saw, feel free to check out my notes on the conference here - https://blog.kasten.io/posts/our-top-highlights-from-kubecon...

Kasten | Backend Engineer | Go | San Francisco Bay Area | Full-time | ONSITE | VISA

Interested in working on cloud-native technologies such as Kubernetes, being a part of the CNCF ecosystem, and solving real-world problems with running stateful applications within containers? If yes, come and join Kasten!

We are a well-funded startup based in the San Francisco Bay Area (Los Altos downtown to be precise). You can find a lot more about the open position, our culture, and more at https://kasten.io/careers/

I believe the problem has now shifted to a slightly higher level and especially when working in a microservice/containerized world. For example, given the number of specialized services you mentioned, we see more applications with polyglot persistence stacks underneath. If they form a part of the same application, how do you collectively manage them? What does it mean to take a consistent snapshot? These and a bunch of other similar questions need to be answered.

There is some work we are doing (https://kanister.io) to help with these issues but there are a lot of emerging solutions in this space. Look at CNCF's landscape for some more detail.

Honestly, the answer will really vary depending on who you talk to. That said, if you have worked hard and built a network in the area, those things are actually true. Even around 2001/2002 as well as 2008/2009 there were always jobs around if you knew where to go look. Similarly, if one has established a reputation for themselves (one doesn't need to be a public figure though), it makes it easier to get something off the ground.

The main webpage (and the links from that) will give more context on how the readings were chosen - https://www.andrew.cmu.edu/course/15-749/.

On a separate note, it is always great to see Satya's courses in the news.

Cool. While this deck wasn't too bad, sometimes the video-only presentations without a link to the actual slides really do need notes like this.

In addition to what Vibhav said, Maginatics also hires/sponsors H1Bs.

We are also trying to get a great team together. You can check us out on LinkedIn or find most of us at http://twitter.com/#!/maginatics/team/members. Drop us a note or come meet us for coffee!

Mountain View, CA

Maginatics is hiring!

While we are still in stealth, we are looking for strong systems developers. In general, you need to be smart and hands-on with experience in distributed systems, storage systems, security, algorithms, or Infrastructure-as-a-Service (IaaS) and other cloud systems.

Check out http://maginatics.com/jobs.html to apply. We also do H1Bs.

The gray areas were exactly my point. There are sometimes clear-cut cases but generally things can be very vague to us non-lawyer types.

Look at this earlier HN thread for more info - http://news.ycombinator.com/item?id=2208056 . It talks about all the potential ramifications and that one should almost always talk to a lawyer.

Unfortunately, the blog post is somewhat flawed. In the CA law he references, it clearly states that the exception to you owning your code/ideas is if they "relate at the time of conception or reduction to practice of the invention to the employer's business, or actual or demonstrably anticipated research or development of the employer."

While IANAL, the consensus on a number of websites is that, while working for a tech startup, anything that you do in your free time could technically belong to the company you work for as its related to your "employer's business."