How to set up a home server for my business and family

@mido thank you for joining the forums and glad you posted the question here. Definitely, I think your use case is very common for those running a home server/home lab. You could run Linux directly on your Dell server and then install applications in Linux natively. However, I would recommend running some type of hypervisor on your Dell hardware, as that will allow for lots of capabilities in terms of management, backups, etc. What type of storage are you using with your Dell server. Is it all local storage? 

Also tagging @malcolm-r @t3hbeowulf @jnew1213 as they are running quite a few resources in the lab and appreciate their insights around self-hosted services.

@mido great to have you here! i tend to shy away from one "machine" (or 1 VM) doing everything. yes, you can install all the apps on it and they'll work, but compartmentalizing via multiple VMs or containers is easier to manage. for example, the more you install on one instance, the more services you would affect if/when you have to restart that machine (or if you break the machine).

docker/VMs are also great because if you mess something up (like i do constantly) it's easy to start over with a clean slate.

with regards to Plex... it can have some hardware requirements depending on your use case. if you're going to be transcoding media, a dedicated GPU (or a CPU with Intel QuickSync) will be your best option.

@Mido, it's great to have you here!

I'm in full agreement with my cohorts, here, that a combination of virtual machines and containers, under a suitable hypervisor is the way to go.

VMs treat machines as files, which makes them very easy to backup, clone, move (even while running!), destroy and replace.

Containers take away some of the overhead that virtual machines have by virtualizing the operating system and environment an application runs in, allowing a single OS instance to run multiple applications (VMs each have an instance of an operating system, containers share their OS.)

It's common to spin up, say, an Ubuntu Server virtual machine, install Docker on it and then install a couple of applications inside Docker. Docker apps can use persistent storage, which can be backed up and which survives server reboots, application upgrades, etc.

Some hypervisors support containers -- Docker and other containers -- natively, without creating a virtual machine to host them.

Most servers built in the last decade or longer have really been built to run a hypervisor rather than a single operating system, like Windows Server or Linux. This keeps the hardware useful and busy rather than having multiple expensive servers sitting around, each with minimal load.

Once you get your server and environment up and running, you'll come to realize that you have a performant little data center all sitting on your one box.

There are some ways to minimize the impact of multiple applications running on the same machine and competing for resources. Some consider this as much an art as a science. It's something to discuss as you build your environment and bring it online.

More information about your server and it's hardware configuration (I'm a server guy!!) would aid discussion going forward, as would you sharing your thinking on hypervisors and which one(s) you're looking at.

Best regards!

I'm a little late to the party but I wanted to at least say that @brandon-lee, @jnew1213 and @malcolm-r have the right idea and are posing the right questions for you to ask yourself and consider. 

My homelab journey started with a single server running a desktop linux OS (Linux Mint) and docker containers. Nearly every service I wanted to run at the time (Plex, Mattermost, Jenkins, etc) were in Docker containers with local storage mounted in where necessary. Don't use a desktop OS... the rest was fine for a first run. 
The next iteration of that single server was ProxMox. I made an image of the original OS and turned it into a virtual machine on that same server. This gave me the ability to clone the VM and make changes without disrupting services in the first VM. I added Portainer to the VM to manage the Docker containers in a GUI. 

When hosting services for family, I can say that the most important thing is always maintain the ability to keep something up and running. They don't understand downtime and while admin stuff is fun, admin with impatient family is less fun. 

I quickly realized that I needed two servers... one to play on, spin up services, test things out, etc. One that has the services the family uses. I would promote configurations and VMs to the "family" server once vetted and working in my sandbox. 

For your case, start simple. ProxMox is super quick and painless to install onto almost anything and presents a pretty usable Web GUI for 94% of the things you'd ever need to do.

• Build a VM in ProxMox. (I personally like Debian, there are plenty of distributions to use.)
• Maybe install Portainer (This helps manage docker containers in it's own Web GUI)

There are many tutorials and guides which document how to get a service up and running with a Docker Compose file. Portainer can use those too, making it fairly straight-forward to get a container running your preferred service. Once you have a baseline, there are number of ways to back things up. @brandon-lee mentioned Duplicati, something I need to try myself. I use ProxMox Backup Server... it's running in a VM on my server and has its own storage mounted for keeping backups. If you decide to set up a second server, you can use ProxMox Backups to restore VMs and containers to that second server.

All in all, have fun, tinker and feel free to ask questions.