From r/homelab itself -
Proxmox Thread - Home Lab / Virtualization
- Thread starter Party Monger
- Start date
Decadent_Spectre
Adept
I was actually googling for a definition, reddit was among the first results and I did browse that site long ago and now before posing the question. I understand what it is, I'm more curious how people would define it. It's not so much about what people do with it, rather how do you define (or differentiate) between a regular PC running some tools and a Homelab or so? Where is the line? So I asked how people would define it, more like a dictionary style definition so there is a clear label as to what it is. Of course if people prefer to leave it deliberately ambiguous that's fine too though a little confusing.
They did that exactly over there in the first post.
There isn't any. I can call my linux box running a few services, a homelab. Someone else would have a switch and multiple tinypcs on a rack as homelab. Some would even have a rack server.
Decadent_Spectre
Adept
While I understand your position and sentiment it doesn't answer my question. As mentioned I have already gone through the link.
I understand that most people who use the term don't recognize any proper definition, that is the reason I ask the question. Purely curiosity.
Another way to ponder would be a regular PC built for normal tasks, including media/games and also running say Plex or similar, if that doesn't work add a VM. Is it now a "homelab"? If so according to which definition?
why are you obsessed over semantics? though I would call your pc a "homelab" too. you don't need a definition, call it whatever you want, I call it a homelab and for me it's any pc running a bunch of self hosted services for personal use
Decadent_Spectre
Adept
If you thought I was obsessed you did not read it right. It isn't about my PC but feel free to say what you want. I am looking for a definition, hence my question, you may not have an answer that doesn't mean I can't have a question. Your definition might turn out to be pretty much any PC today but it is interesting, your choice of definition that is. Thank you.
It’s simple words, you run the services you need and experiment. Like backups and data managements(nas), photo managements(immich), documents management(paperless), media management(*arrs) and so on. Its like you the your own data and subsidies subscription/depending upon the ecosystem. To distinguish on further, homelab are server(enterprises hardware or any old hardware) and network gears(switches and gateways) to fulfils your needs, at your own control.
superczar
Skilled
I guess you would have done this already so the response is too late - but for future reference:
the beauty of virtualizing is no hassle backups and near instant restores
You do not need to backup (or image) the server itself.
but ALWAYS, and i mean always backup the VMs and CTs
1) The backup section is within the promox ui for individual VMs/CTs.
2) As a rule of thumb, at least manually backup each VM/CT once its set per your preference
3) Preferably setup a periodic task for backup
the backup itself will be a flat file thats saved locally under /var/lib/vz/dump (or you can alternatively even set it to be saved on a separate smb share)
sftp / copy these flat files to a safe location
If disaster strikes
Copy these back and restore 1 by 1
If you want to restore all in bulk, also keep a copy of the VM conf files (/etc/pve/qemu-server) and CT conf files (/etc/pve/lxc ) and copy all three in their respective location
Restart server and voila!
Worst case if the server itself is borked/ HDD needs replacement, the max time you need to spend is on doing a fresh proxmox base install and restore the copies
MarioBros
Disciple
thanks, this will help
as you suggested I have already started manually backing up VMs & CTs are required safe points.
Your testbed at home. Can be a desktop PC, can be a laptop, anything goes.
rsaeon
Patron
Ha, one of the things I experienced when I returned to India after a few years abroad is that questions aren't viewed as a sign of curiosity, they're often viewed as accusations.
Broadly speaking, there are two paths where a homelab takes you or where you go with it.
They both start with a controlled environment where you yourself are the highest authority so you have the freedom to experiment, learn and tinker around with enterprise-level technologies/products/services/ideas/concepts — without the fear of failure.
Examples of this could be as simple as DNS filtering or as complex as a central repository of media/backups/files.
The two paths diverge depending on whether this environment is meant to further your career or if it's meant to satisfy a curiosity.
For the former, you'll find homelabs built out of refurbished enterprise hardware and run by individuals intent on expanding their skillset.
For the latter, a homelab could be anything from a raspberry pi to an old laptop to shiny new hardware and everything in between.
It's generally accepted that a homelab consists of dedicated hardware that focusses on high availability. The smallest/simplest homelab would be a wireless router with a USB disk plugged into it (technically a NAS).
A personal machine running Plex that can be shutdown or taken offline is just that — a personal machine that has some server duties, not necessarily a homelab (unless if it's meant to be a portable homelab).
superczar
Skilled
This!
my first homelab was a couple of RPIs (OG gen) running Home autmation and NAS duties.
Over the years, a lot has changed - the hardware, the architecture and the topology (Currently a 10th gen intel with 48Gigs of RAM running 4 VMs and 5 containers)
But one thing that remained unchanged is that the homelab machine(s) always have had only two cables: Power and ethernet.. nothing more, nothing less…
They have always sat in forlorn corner, typically inside a closet - and I have never tried to use them for anything else but backend duties
I probably wouldnt even call it a lab anymore - if i take it down (or reboots for that matter), my family would start screaming at me within minutes
Any kind of experimentation (or even upgrades) with it are reserved for when the rest of the house is sleeping
Last edited:
Pat
Skilled
This!
my first homelab was a couple of RPIs (OG gen) running Home autmation and NAS duties.
Over the years, a lot has changed - the hardware, the architecture and the topology (Currently a 10th gen intel with 48Gigs of RAM running 4 VMs and 5 containers)
But one thing that remained unchanged is that the homelab machine(s) always have had only two cables: Power and ethernet.. nothing more, nothing less…
They have always sat in forlorn corner, typically inside a closet - and I have never tried to use them for anything else but backend duties
I probably wouldnt even call it a lab anymore - if i take it down (or reboots for that matter), my family would start screaming at me within minutes
Any kind of experimentation (or even upgrades) with it are reserved for when the rest of the house is sleeping
What services do you run currently on your homelab?
oh boy tfw, I can so relate to this, I don't have a homelab but I pay for a hetzner and if I ever take it down during the day I'll get calls within 10 minutes of itAny kind of experimentation (or even upgrades) with it are reserved for when the rest of the house is sleeping
superczar
Skilled
1 ubuntu VM as NAS and a couple of other services
1 VM running home assistant
1 VM running grafana and influxdb for various logging
1 VM running windows for legacy reasons
1 VM running opnsense as the primary router - (this was on an independent machine (baremetal ) earlier but moved it to this unit for power conservation/ easier backups and I am glad I did)
The containers are varied in nature - notable ones are a SDN/roaming controller for wireless APs, another for homebridge , one as a VPN punch hole(airtel blocks port 443 forwarding) etc
nice article for the Plex guys - Intel Quicksync wins hands down in transcoding
honestly, server pcs are not a good choice if you want proper media playback with atmos, dv and what not. Would recommend something like a Zidoo Z9x pro or a shield tv for it. Intel would suffice for a quick transcode where quality is not the issue but nothing more
variablevector
Disciple
Most people don't connect their Jellyfin/Plex server directly to their TV. You use it to deliver content over lan to your FireTV/Android TV box/Shield/etc. That way you can do HDR/atmos/etc with your personal media library as well as use any streaming apps you want. It's the best of both worlds.
yeah but then you need to disable transcoding which makes the point moot, and tbh out of all the options you listed, only Shield is capable, rest all are crap
Dolby_Vision_stuff - Google Drive check this out for a proper breakdown
Why ? Quicksync transcodes work in Plex.
Edit : I get that Atmos, DV etc won't work. Plex does not have DV license anyways.
Last edited: