this post was submitted on 16 Dec 2024
26 points (93.3% liked)

Selfhosted

40633 readers
306 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 2 years ago
MODERATORS
 

I just spun up a Nextcloud VM, and I'm trying to decide the best way to manage the data storage.

For context, I'm running it on proxmox and installed it with This script.

Ideally I'd like to keep most of my storage on my NAS. I'm trying to figure out if I should keep the data directory local and add a NAS NFS share as external storage, or just move the whole data directory to an NFS share.

How are you guys handling your Nextcloud storage?

you are viewing a single comment's thread
view the rest of the comments
[–] ShellMonkey@lemmy.socdojo.com 3 points 21 hours ago

My two main boxes are split to be storage vs compute. The NAS box has a minimal CPU and a pile of 3.5 drives for the low cost storage and they hypervisor has all the CPU and fairly small storage.

Basically the goal in my setup is all the working data is in one place and the handling in another with various snapshots and RAID mixed in to avoid the risk of "oh shit did I just...?" situations.

So anything that could be called bulk data gets offloaded to the NAS directly via mounts and any cache/working data is held locally. If your lab space grows to a notable level over time eventually you need to consider disk I/O as part of the design and having the bulk data on another box let's you effectively trade some network load in for disk load.