I'll get to the good stuff in a minute, but I just closed case 08008196 in disgust after I was told to edit registry keys on a Linux appliance. Who puts REGISTRY keys in Linux??? That just screams "I went to a six-week Linux for n00bs bootcamp." That's not to mention the extensive use of dotnet in Linux. At risk of repeatedly sounding like Austin Powers, who does that? Really?!
Okay, good stuff as promised:
FIPS complaince and zero-trust built right in. Love the way shell access is managed, for example. I don't love that the shell is limited to tmux, which breaks scrollback. Maybe don't do that? I get that it means other authorized people can watch your shell session but there have got to be better ways than tmux, which I generally hate anyhow (it's a Linux-people holy war of long standing)
Setup and maintenance is a breeze. I'm sure there are things in the initial setup that could be improved but all in all it went nice, and having the hosts keep themselves patched and up to date is great
Performance is good (with caveats). If everything configures cleanly, you've got a nice system doing exactly what you want, and nothing more.
All in all, acceptable as a first try. Now get rid of the "think-windows" approach to development and configuration, and move to those tasks being done the way Linux is meant to be used.
'If you truly love Veeam, then you should not let us do this ' --Gostev, in a particularly Blazing Saddles moment
Huh? Linux appliance cannot possibly use "registry keys" because there's no registry in Linux OS in principle!
Veeam appliance uses good'ol config files approach, the classic Linux way to set custom parameters.
Guess support misspoke because they mostly deal with Windows installs. These are config files and if you're really for getting rid of the "think-windows" approach, how can you complain about having to edit config files? When it comes to Linux, it's how you do.... well, anything at all really
Yeah, you'd think that, but they really did map registry keys to a handful of files in /etc. Looky here: https://www.veeam.com/kb4779
Most cack-handed mess I've seen in a long time.
'If you truly love Veeam, then you should not let us do this ' --Gostev, in a particularly Blazing Saddles moment
The KB explains exactly what I'm saying? THey are using classic config files, like any other Linux software.
Specific example given inthe article:
File: /etc/veeam/veeam_backup_and_replication.conf
Section: [root]
Value: InverseVssProtocolOrder=1
In your mind, how's this different from the following rsync configuration parameter for example???
File: /etc/rsyncd.conf
Section: [file]
Value: read only = no
I see exactly the same approach for managing software parameters! Note, not similar or identical - but EXACTLY the same.
so how's one "how Linux is meant to be used" and another "cack-handed mess" lol
' --Gostev, in a particularly Blazing Saddles moment