Luckily, to replace most of the Office applications, their respective online web applications work very well. That wouldn't be a major issue in migrating to Linux.
Fascinating! The wine discovery reminds me one scene from the book 'The Dark Forest'[0] when the protagonist drinks a wine from some centuries before... spoiler: it wasn't good.
That's the point, but often in many network issues, the name resolution is the root cause of the problem. Not necessarily the DNS itself. Sometimes the /etc/hosts is more than enough to cause headaches!
I'm disappointed: I can't see any comments about the awful .zip file integration in modern Windows version.
Extracting the files requires a pop-up or a non-intuitive context menu.
> if it's VMDK for example, you can read the raw disks without booting it
Yes, but that's the difference between "readable" and "usable". Many companies don't realize the technical difficulties to be able to run the VMs. They just expect that it will work, if needed.
This rises a potential problem, often underrated by companies: some have backups with infinite retention.
It is common to have backups with retention of 10 years, some may have 20 years for legal reasons… but the majority of people don't understand the difference between "readable" and "usable".
Of course, it depends on the data… And there are companies backing up whole virtual machines with infinite retention, believing to be able to run them: it is hard enough to restore a vSphere 5.x machine on a brand new vSphere 8, I really don't understand this waste of space.
Hi, I'm the author. Sincerely, I didn't think to a license yet, but I will.
I just wanted to "show" that big vendors don't care about solving very practical issues: some companies still rely on backups on physical tapes, but the current versions of firmware of most libraries don't allow optimizing automatically the tapes. That's quite a problem when maybe a customer just bought 2,000 cartridges.
About the parallelism, it's quite simple: a tape needs to be read and optimized by a _tape drive_[0]. Libraries can be configured with a various number of drives, and the script manages all the available ones using the special device of the library and the `mtx` tool on Linux.
Also, you're right: it's impossible to decrease the optimization time of a single tape.[1][2][3]
Ah, while writing this, I noticed that HPE may have the appropriate tool on their autoloader.[4]