Questions on Homelab setup

Depending on the VMs you’re creating, you’ll likely need an average of 40-60GB space. In any case, you’ll want to configure thin provisioning for your virtual disks, both for VMware Workstation and for ESXi, this means that the disks only consume the space required initially, rather than reserving it all. This way if you create a virtual disk with 100GB maximum capacity, but only use 8GB, that’s what gets consumed! Though be aware, once a disk is grown, aka more space has been consumed, it doesn’t automatically shrink back.

For ESXi data stores I’d actually recommend you create a disk in VMware workstation per VM you intend to create in ESXi. This means that when you no longer need a VM, you can delete the datastore from ESXi, then the disk from VMware Workstation, and that way you’ve reclaimed your space on your laptop.

As for required capacity, depends on how much you need to test but 400-500GB should be sufficient to get going and build a decent amount of infrastructure.

Yes, im going ahead with VMWare Workstation 16. :) Thank you for the link! I was able to install and set it up. Does that mean i can skip this step?

Thank you for this MicoolPaul. I already started my journey and what i did was my laptop OS is a fresh install. I installed Windows 10 Pro. After that, i also installed VMWare Workstation 16 (Using NFR) licese. I then installed ESXi (Vshphere 7.0.0), yes, not the latest due to my storage is not being detected by that Vsphere 7.0.3u. 

Some questions i have is, i understand i will be installing other VMs inside my V sphere. So many GB should i in my Vsphere considering other things that i will be doing to with it for the process. 

I understand i need to put a Windows Server inside, how many gb should i allocate there as well.

So far this is where i am at. I will encounter more questions for sure but will like to be able to move past this step.

I’d also add 2 more thoughts to this.

My “Lab” quickly became “PROD” in my house, running home assistant, IP Cameras etc. This seems to happen to many of us.

Servers take a while to boot. Make sure to get a UPS, or something that can boot fast. There is nothing quite like haivng the power go out for 1 second, and waiting for a server, ESXI, Then a windows DC, then Home Assistant to turn on before you can have lights.   The sequence was automated, but took 5-10 minutes. Same goes for a TV restarting vs missing 10 minutes of a show because you are waiting on the DHCP server/DC to boot.

To add to that, once it becomes “Home PROD” as I like to call it, fan noise is pretty annoying 24 hours a day if the server is in your house.  I switched to a NUC for my Home Assistant due to low power and no fans. Removed a few of the 48 port PoE switches and replaced them with PoE injectors upstairs. 

I still have my monster server, but only power it on when I need. I also don’t have my house relying on AD with a DC anymore haha. 

Hey! Absolutely you can! Here’s how I did it:

You’ll want to use a ‘daily driver’ OS for the laptop I imagine, as you won’t get any guarantees of supported hardware if you ran ESXi or Hyper-V natively on it. Windows or Linux doesn’t really matter.

Depending on Windows or Linux you’ve got some options, these will be ‘type-2’ Hypervisors in that, they’ll run on top of your OS, performance won’t be as good, but I doubt you’ll see any major bottlenecks here.

If you’re using Windows, you can install VMware Workstation, OR, Hyper-V, or even something like VirtualBox. On Linux you won’t have the Hyper-V option but the other options remain.

Now, you won’t be using Veeam to interact with these, instead you’ll be using nested virtualisation to run a supported Hypervisor within Workstation/Windows 10 Hyper-V/VirtualBox. Why you might ask? Because Veeam needs to leverage APIs to interact with a host for VM processing. The two main hypervisors that Veeam supports are ESXi and Microsoft Hyper-V. Now the complicated part: You’ll need to enable exposing virtualisation capabilities to your VM within whichever type-2 hypervisor you chose (Workstation/Windows 10 Hyper-V/VirtualBox), there are different ways of doing this depending on the application you choose to use, but they’re only a google search away, or state here what you’re planning to use and we can hopefully point you in the right direction.

Once you’ve deployed a virtual hypervisor such as ESXi or Hyper-V into your type-2 hypervisor, you can then either deploy a Veeam VM within your virtual hypervisor, or within your type-2. Your only networking requirements are that you create a bridged network between your host (laptop), your other VMs, and your virtual hypervisor.

Now onto some specifics:

ESXi free edition doesn’t provide the APIs required to backup data, either use a trial, or NFR key if possible to license this, you don’t actually need vCenter, just a licensed ESXi.

Fun fact: Your laptop is more powerful than the PC I used for my lab when I was studying my VMCE, it’s a quad core with 32GB RAM and I still achieved what you’re trying to do.

So, hopefully this helps you get started, and I’ll do my best to answer any questions I can to get you going!

Hi All,

Im very new to Veeam so i would like to apologize for the questions.

I recently bought a laptop. Yes, not a server. The specs are Ryzen 7 Pro 5950u with 8 core, 16 threads, 1TB SSD, and 48gb ram. 

I am planning to create my homelab prior to my VMCE training this coming end of October 2022. Will i be able to do it with a laptop? I dont have servers with me and im really new to VMWare and other things so i wanted to know if i can do it in the laptop or i am just wasting time trying to replicate a home lab there. I hope you can enlighten me.

Regards,

Sean

Thanks, I’ll check into that.  We don’t have MSDN right now but it wouldn’t hurt us any.  I know we get some Azure credits from our partnership, but I don’t know how much nor do I know how much we’re using them at the moment.  But thanks!

I think that it’s almost a requirement.  I mean, you see the likes of Rick Vanover and Anthony Spiteri run labs that I think span both premise and cloud.  For sure they have to have cloud to spin up labs for cloud-base products, etc.  I mean, it’s not all of the sexiness of running hardware in your own datacenter, but for the purposes of learning and testing, I suppose it’s pretty much a requirement.  In fact, the other day I was looking for free/NFR versions of Azure to do some testing of cloud-based services as well as extending to object storage in Blob, etc.

Great point, but I wouldn’t consider it as a lab @dips… I might be wrong, but I see or classify it as a learning / training environment.

#Humblebrag

The current work lab…..also looks nicer than a lot of productions environments I’ve seen.  But alas...it needs some reworking as it gets updated to version 2.  The pics are a bit Veeam off topic, but that HP behind the monitor is the box running the VBR/VDRO VM’s, and there’s proxies in the ESXI cluster to keep it Veeam related.

 

That is one sweet setup!

Hey @Iams3le the link you post contain a redirection from a Veeam competitor, can you clean it? 😂

@dloseke agree on the Ubiquiti comments there, I’ve always been a Cisco guy, I even tried to see if I could get any Cisco Meraki GO hardware that has been released. Unfortunately, Meraki GO is basically last-gen EoL hardware to put it nicely. Cisco doesn’t have a WiFi 6 Meraki GO solution, I can only assume to avoid competing with their Meraki ranges that require a subscription. The Meraki GO firewall was off-putting too, at 250Mbps.

The WiFi access points are solid for me, haven’t had any firmware issues yet but I’m painfully aware they’re out there from my MSP previous life. Can’t say I’ve tried any Ruckus hardware either for comparison. My main critique of the WiFi 6 Ubiquiti devices are that despite being able to use 5Ghz @ 160Mhz channel width, the device only has a single 1Gbps port, even though it’s possible to push more than 1Gbps through the APs. But I can understand there aren’t many environments and scenarios whereby pushing 1Gbps+ speeds through WiFi are actually required yet.

+1… Same strategy as @MicoolPaul. They should run only when needed. This is what I currently do with my Workstations whenever I ain't using them, and it will me extended to my new lab.