this post was submitted on 27 Jul 2023
10 points (85.7% liked)

Selfhosted

40359 readers
331 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hi everyone,

I've been running a home server with Arch Linux (i7-3770, 16 GB RAM) for a few years now. It's a mix of Docker containers and some services directly on the host system. I'm trying to move everything to containers though.

For storage, I'm currently using a 256 GB SSD for the host system and three 6 TB HDDs in a RAID 5 for data storage. Backups are currently stored on the same hardware (not the best idea, I know) with Borg Backup.

I wanted to upgrade and rebuild my home server setup as I have a PC I don't use anymore (i7-8700K, 32 GB RAM), two 18 TB HDDs, a 256 GB PCIe m.2 SSD and a 1 TB PCIe m.2 SSD.

So my available hardware is this:

  • PC 1 - i7-3770, 16 GB RAM, 256 GB SATA SSD, 3x 6 TB HDD
  • PC 2 - i7-8700K, 32 GB RAM, 256 GB PCIe m.2 SSD, 1 TB PCIe m.2 SSD, 2x 18 TB HDD

Initially, I wanted to just move everything to PC 2 and be done with it but I've stumbled upon Proxmox and wanted to check if it makes sense to build a nice setup with this. At least some of the Docker containers could be converted to LXC or VMs. The rest could stay as Docker containers in a VM I guess.

I could do something like this:

  • PC 1 as a Proxmox Backup Server host
  • PC 2 as a Proxmox VE host

A lot of data on the current 12 TB RAID 5 doesn't need to be backed up so 12 TB just for backup storage should be enough.

I'm not sure if that's the best/most efficient way to use this mix of hardware, maybe someone has a similar setup or other advice :) I'm also trying to save as much energy as possible even though that might be hard with 2 physical servers. (Does Proxmox BS turn off HDDs when they're not in use?)

I'm not super fixed on Proxmox although it does look like it's easy to manage without a lot of maintenance involved.

top 6 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago (1 children)

I would move to the new PC2 with the intent of decommissioning PC1 later, since you want to save power running 2 systems doesn't make too much sense. And PC2 has tons of resources so you shouldn't have any limitations.

If you wanted to keep the 3x 6TB drives you could move them to PC2 as well.

Proxmox is great, very easy to manage and minimal maintenance. It has ZFS support so you could do a mirror with the 2x 18TB drives if you wanted to.

[–] [email protected] 1 points 1 year ago (2 children)

How would I handle backups though? I have some data I should definitely back up in some way, e.g. Nextcloud or paperless-ngx. A mirror is good but doesn't replace a backup :D

That's why I brought in Proxmox Backup Server, not sure if that's overkill though or if I can backup using Proxmox VE itself. I've also read about people running Proxmox Backup Server as a VM inside Proxmox. That way I only have one physical machine but I'm not sure how complicated it would be to access the backups if the Proxmox VE host itself goes down.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Yeah that is one reason to keep the other host.

In my case what I do is backup the Proxmox Backup Server VM to my desktop PC over the network, so if my Proxmox host fails I can:

  • Reinstall Proxmox on the host or some other host
  • Restore the Proxmox Backup Server VM that's saved on my desktop PC
  • Once that's running, I have access to all the other backups and can restore the rest of the VMs and Containers

Obviously that's assuming the drives haven't failed for some reason, if that's the case I also backup important stuff with Restic inside each VM and Container, and that gets stored on Wasabi S3 or Backblaze B2. Those backups are if everything else fails, a lightning strike takes it all out, or there's a fire or something. They would require rebuilding from scratch, but the important data is at least saved.

[–] [email protected] 2 points 1 year ago

PBS is a good backup solution, and it will also replicate to an external harddrive if you want an offsite. The backups are navigable/downloadable in the interface and with the CLI client, you could restore full trees back to a system or VM, besides being able to restore the whole image into a new VM. It also dedups quite heavily so you can keep months of images on little disk space.

Personally, I would leave PBS separate on a weak computer, it doesn't take much of a system to run it, for the reason you state. You can also backup the PVE host to that computer using rsync on the important bits like the /etc/pve folder as per the forum suggestions.

If you have other questions you can't get answered here, consider signing in to https://discourse.practicalzfs.com where there a number of Reddit refugees to answer questions. There's also some Proxmox forums on Lemmy here but none are very active yet.

[–] [email protected] 2 points 1 year ago

Definitely a trade off between energy and security. I have PBS running on an old laptop backed up to Backblaze and wouldn’t change it for anything, though. Proxmox backups are flawless and have saved me so many times. But yeah, 16GB of RAM with that processor is overkill for PBS and will probably consume more energy than is needed.

If everything is Dockerized anyway, you could just skip the step where you backup to PBS and use something like Kopia to backup your Docker volumes to a network share or offsite, rebuilding with compose or whatever if you have an issue.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

I’m also trying to save as much energy as possible even though that might be hard with 2 physical servers.

Desktop systems tend to eat a lot of power even at idle so this may be challenging. It's possible that 3 lighter machines would use less power than even one of those servers although you should use a power meter to test at the wall as there are often tweaks you can make.

Make sure there aren't any dedicated GPUs installed as they tend to contribute significantly.

load more comments
view more: next ›