

Get a load of this guy, thinking containers are more of a hassle than VMs!
Get a load of this guy, thinking containers are more of a hassle than VMs!
Object storage is really popular for backups now because you can make it immutable by protocol standard and with erasure coding you can have fault tolerance across locations.
The problem with external LUNs is that they’re out of the control of the hypervisor. You can run into situations where migration events can cause access issues. If you can have the data presented through the hypervisor it will lead to less potential issues. Using object or NFS are also good options, if available.
Don’t present LUNs to VMs is the best practice. The only time you should do it is if you’re absolutely forced because you’re doing something that doesn’t support better shared disk options.
Save your files to a local s3 object storage mount, enable versioning for immutability and use erasure coding for fault tolerance. You can use Lustre or some other S3 software for the mount. S3 is great for single user file access. You can also replicate to any cloud based S3 for offsite.
Might want to move the NAS to a separate, unrouted VLAN. Storage only needs local connections and it’s good practice not to make it routable.
Walk away and find a not incompetent lawyer.
Send him docx files and tell him if he can’t work with modern files he needs to fix it. It’s like $30/mo for an office subscription. There’s no excuse for him being so cheap.