Veeam Community Forums Digest for dandvo [Feb 5

Veeam Community Forums Digest for dandvo [Feb 5 - Feb 11, 2018]

Veeam Community Forums Digest

February 5 - February 11, 2018

THE WORD FROM GOSTEV

I have no significant updates to share this week, however there is one big open question we'd like your input on in regards to the system requirements for our next product update cycle. I've put the rest of the story into the forum post, since this is specific to VMware vSphere users > [POLL] Legacy ESXi versions usage (2018 Edition)

I also wanted to draw your attention to our Subscription Center. At first sight, the page may seem like a bunch of check boxes on marketing stuff no one of us likes to be getting. Except product announcements perhaps, but then again – if you follow this digest closely, you're usually the first to know anyway. But if you look closely, at least one check box there is super important for all Veeam admins – and that is Security Advisories. These go directly from our support organization, and is something you'd usually want to act upon immediately – while this digest adds up to 6 days of "latency". So do consider subscribing to at least that part for sure!

This is a really curios study, because we all know the same cannot be said about a backup software > Humans like faulty robots better

BEST POST OF THE WEEK

Re: Veeam Linux Appliance [BY: Gostev • LIKED: 4 times]

@Michael, I've fixed the link for you.

csydas Wrote:But the point is, a Linux appliance isn't just some trivial thing. It's not a matter of "port the veeam agent over to *nix and call it a day", you lose tons of functionality.

Correct. I would put it this way - it would be trivial if Veeam was not so advanced and had all those "invisible" features that make a huge difference. For example, one type of issues we've ran into is our advanced NTFS processing features like BitLooker: they work perfectly on Windows proxies (using native NTFS driver), but crash left and right on Linux proxy with its NTFS driver. We wasted much time on this issue and gave up at some point.

One valid use case for Linux proxy that I am considering is the protection of clusters running purely Linux workloads - we do have such customers and this functionality would benefit them. There, we obviously would not have to worry about all that NTFS-related functionality. But then again, how do you prevent the rest of users from getting excited, deploying Linux proxies everywhere else and starting to open support cases complaining how this or that no longer works, or performs worse? That is always my challenge - how to ensure that some new feature does not impact customer satisfaction with our solution, considering that just about nobody reads the manual?

All in all, our choice of Windows platform for everything comes from one simple number - 90% of all VMs running on vSphere run Windows OS. It's not that we do not have any Linux expertise - if you were using Veeam back in its early versions, you know that all this product could do originally is process VMs running on "fat" ESX host with [effectively] an on-host Linux-based proxy. However, the introduction of ESXi and some our first innovations - as well as very limited development resources - have pushed us to focus on Windows proxies at the time.

ddprecist

Prohledat tento blog

Veeam Community Forums Digest for dandvo [Feb 5 - Feb 11, 2018]

Komentáře

Okomentovat