Linux As File Server- Break Out From Other Thread
-
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
My question is, what are the recommendations/best practices when setting up Linux file servers. I guess I'm less concerned about which distro to use (I've been using Fedora more and more so that's likely my first choice) and more concerned with how you would set things up. For example, do you disable SMBv1 and only allow SMBv2 as the minimum standard? What's the best approach for setting up access rules for Linux if in a workgroup? Any gotchas or ah ha's I should know about?
Basically treat it all the same as you would with Windows. If you'd do those things with a Windows file server, do them with a Samba one, too.
-
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
These clients mostly run Windows PCs although some have agreed to test out using Linux desktops to see if that could be a fit. The oldest version of Windows for any client is Windows 7 (but they will be upgrading to Windows 10 shortly). Some have Macs but very few.
Windows and Mac are SMB native. Linux desktops will use SMB, but it's not as elegant as moving to NFS. Anytime you can use NFS, go for it. Works so well on Linux.
-
@dafyre said in Linux As File Server- Break Out From Other Thread:
There are some Gotchas with using SAMBA and Macs.
Be sure to install vfs_fruit
-
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
Most of my clients are small business owners, running in workgroup environments, and as licensing renewals/upgrades come up in discussion, most are also interested in reducing the licensing costs associated with Windows. As I slowly convert them to Hyper-V servers rather than Windows Servers running Hyper-V role, for clients for whom it makes sense to have on-premises file servers, it often might make sense to make the suggestion they move to Linux file servers (unless there are other reason why they must be running Windows).
Generally worth moving to KVM instead of Hyper-V, too. No need for the complexity and overhead of Hyper-V, especially if you don't have AD. KVM is just easier to manage in the SMB world.
The only problem with this is, although I'm getting better with Linux and can manage most scenarios now, Hyper-V is the hypervisor I'm most comfortable with. KVM may be a much bigger learning curve. That's likely a topic for a different thread but things like how do I run backups/recovery from KVM for VMs, management methods/tools for KVM, etc?
-
@nashbrydges scott's reply will be "the same way you run backups on any other hypervisor".
Agent based or by simply exporting the VM on a schedule to a remote storage medium.
-
@dustinb3403 said in Linux As File Server- Break Out From Other Thread:
@nashbrydges scott's reply will be "the same way you run backups on any other hypervisor".
Agent based or by simply exporting the VM on a schedule to a remote storage medium.
"Same way" of course but tools are going to be different. I'll take this away and do some research before asking more question about using KVM.
-
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
@dustinb3403 said in Linux As File Server- Break Out From Other Thread:
@nashbrydges scott's reply will be "the same way you run backups on any other hypervisor".
Agent based or by simply exporting the VM on a schedule to a remote storage medium.
"Same way" of course but tools are going to be different. I'll take this away and do some research before asking more question about using KVM.
Any agent based solution like Veeam or UrBackup etc would work here. If you needed something that was operated at the hypervisor level you'd simply export the VM.
There are also likely some scripts to do this that exist, but I don't know where they might be or how they work.
-
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
These clients mostly run Windows PCs although some have agreed to test out using Linux desktops to see if that could be a fit. The oldest version of Windows for any client is Windows 7 (but they will be upgrading to Windows 10 shortly). Some have Macs but very few.
Windows and Mac are SMB native. Linux desktops will use SMB, but it's not as elegant as moving to NFS. Anytime you can use NFS, go for it. Works so well on Linux.
Any objection using both nfs and smb on the same server?
-
@dustinb3403 said in Linux As File Server- Break Out From Other Thread:
@nashbrydges scott's reply will be "the same way you run backups on any other hypervisor".
Agent based or by simply exporting the VM on a schedule to a remote storage medium.
This is the stupid lazy answer because while it may be the same way technically, the tools do not exist the same.
-
@jaredbusch I agree.
-
@obsolesce said in Linux As File Server- Break Out From Other Thread:
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
any hints on how to more effectively manage these file servers?
SaltStack.
Agreed.
-
@black3dynamite said in Linux As File Server- Break Out From Other Thread:
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
These clients mostly run Windows PCs although some have agreed to test out using Linux desktops to see if that could be a fit. The oldest version of Windows for any client is Windows 7 (but they will be upgrading to Windows 10 shortly). Some have Macs but very few.
Windows and Mac are SMB native. Linux desktops will use SMB, but it's not as elegant as moving to NFS. Anytime you can use NFS, go for it. Works so well on Linux.
Any objection using both nfs and smb on the same server?
No issue at all, but not on the same share. But definitely on the same server.
-
@dustinb3403 said in Linux As File Server- Break Out From Other Thread:
@nashbrydges scott's reply will be "the same way you run backups on any other hypervisor".
This is exactly right. You want a process that is portable and uniform. How do you back up now on Hyper-V? For a file server that probably means backing up files via a script or agent. Your hypervisor is not a factor in that choice. It is unique to hypervisor level backups to have to worry about your platform when making backups. For a file server, you don't even need a backup utility if you don't want one, scripted backups work fine in most cases. Agents are normally better. Agentless has its place, but creates extra overhead in a situation like this. File servers can be backed up any way you want, they are the most flexible of all workloads.
-
-
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
The only problem with this is, although I'm getting better with Linux and can manage most scenarios now, Hyper-V is the hypervisor I'm most comfortable with.
This is like saying that lighting a campfire with flint and stones is what you will do because you are used to it, when the lightswitch is already invented. Even being used to it, I think the light switch remains easier once you try it out
-
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@black3dynamite said in Linux As File Server- Break Out From Other Thread:
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
These clients mostly run Windows PCs although some have agreed to test out using Linux desktops to see if that could be a fit. The oldest version of Windows for any client is Windows 7 (but they will be upgrading to Windows 10 shortly). Some have Macs but very few.
Windows and Mac are SMB native. Linux desktops will use SMB, but it's not as elegant as moving to NFS. Anytime you can use NFS, go for it. Works so well on Linux.
Any objection using both nfs and smb on the same server?
No issue at all, but not on the same share. But definitely on the same server.
Ok. I just remember using NFS and SMB on the same server for a lab project a while ago. And I had an NFS share set up for Linux servers to back up to. And SMB share for Veeam Endpoint Backup to use.
-
@black3dynamite said in Linux As File Server- Break Out From Other Thread:
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@black3dynamite said in Linux As File Server- Break Out From Other Thread:
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
These clients mostly run Windows PCs although some have agreed to test out using Linux desktops to see if that could be a fit. The oldest version of Windows for any client is Windows 7 (but they will be upgrading to Windows 10 shortly). Some have Macs but very few.
Windows and Mac are SMB native. Linux desktops will use SMB, but it's not as elegant as moving to NFS. Anytime you can use NFS, go for it. Works so well on Linux.
Any objection using both nfs and smb on the same server?
No issue at all, but not on the same share. But definitely on the same server.
Ok. I just remember using NFS and SMB on the same server for a lab project a while ago. And I had an NFS share set up for Linux servers to back up to. And SMB share for Veeam Endpoint Backup to use.
Nearly all NAS do that, too. Very common to have AFP, SMB, NFS, FTP all on the same box.
-
I genuinely dont why and what is file server anymore in this day and age, as it sounds very simple basic and archaic task to the point that it gone pointless, like FTP and SFTP.
Regarding Linux as file server, you should seriously consider Linux Centos/Fedora and check how easy it is to setup and harness the power of linux LVM/FS/VDO/RAID below:
https://mangolassi.it/topic/17760/unlock-vdo-in-cockpitIt as very simple when dealing with elegant GUI client like cockpit, and you just need to install centos minimal + cockpit storaged packages, and your ready to fly. You can do RAID 10 on 4 drives, and then create LVM on top of it, and easily resize that volume any second or grow it without the need of unmounting it. VDO adds the compression and duplication support.
Why do you want to deal with Windows idiot way of mounting network drives and it is limitations.
Screw that, and even if you want to do this, why not use WinSCP with its 16 years of experience with another secure protocol and modern one like WebDav or SCP.
I just dont get why File Server old way of thinking is needed for any company, let them have local copy + sync copy on the server as NC does, way modern and + you can easily host it on premises + open port and you allow them to work from home and access their files.
-
@scottalanmiller said in Linux As File Server- Break Out From Other Thread:
@nashbrydges said in Linux As File Server- Break Out From Other Thread:
The only problem with this is, although I'm getting better with Linux and can manage most scenarios now, Hyper-V is the hypervisor I'm most comfortable with.
This is like saying that lighting a campfire with flint and stones is what you will do because you are used to it, when the lightswitch is already invented. Even being used to it, I think the light switch remains easier once you try it out
Lmao. That's not even a valid comparison. Using Hyper-V or KVM is going to provide an excellent hypervisor platform and while there may be some advantages of using one over the other, we aren't talking about a full on departure from what would be considered good business practice. While I learn about KVM as a hypervisor and continue to use Hyper-V in the meantime, I'm still using standard industry best practice tools. If something was completely against today's norms like running Windows Server with Hyper-V role instead of Hyper-V Server, then it's fair to say that's not the right approach.
Let's not forget that there is huge value in using something you know well over something you don't, especially when it is still best practice.
-
@emad-r said in Linux As File Server- Break Out From Other Thread:
I just dont get why File Server old way of thinking is needed for any company, let them have local copy + sync copy on the server as NC does, way modern and + you can easily host it on premises + open port and you allow them to work from home and access their files.
There are instances where a local file server is the best approach. I think even die hard fans of completely lanless designs cough cough @scottalanmiller cough cough
would agree. I have clients who are in rural areas where internet connection speeds are simply too slow to be effective with any cloud storage technologies. Even their backups are taken offsite every night by their team because internet speeds can't support a cloud solution.I also have clients who are in the graphics and video business. The file sizes they deal with make it mandatory that they use onsite file servers. For a double whammy, this particular graphics company is rural with poor internet speed.
Other cases where business owners are not "comfortable" using cloud only are still running local file servers. But slowly, we're winning them over, especially when some have had to recover backups that are cloud stored and were able to get back online quickly. Some do see the value while others can't handle it. At the end of the day, it is their business and as long as they aren't asking me to support them in a way that I think is detrimental, then they get their local file servers.
