njordomir

Hello Self-Hosters,

What is the best practice for backing up data from docker as a self-hoster looking for ease of maintenance and foolproof backups? (pick only one :D )

Assume directories with user data are mapped to a NAS share via NFS and backups are handled separately.

My bigger concern here is how do you handle all the other stuff that is stored locally on the server, like caches, databases, etc. The backup target will eventually be the NAS and then from there it'll be double-backed up to externals.

1. Is it better to run #cp /var/lib/docker/volumes/* /backupLocation every once in a while, or is it preferable to define mountpoints for everything inside of /home/user/Containers and then use a script to sync it to wherever you keep backups? What pros and cons have you seen or experienced with these approaches?

2. How do you test your backups? I'm thinking about digging up an old PC to use to test backups. I assume I can just edit the ip addresses in the docker compose, mount my NFS dirs, and failover to see if it runs.

3. I started documenting my system in my notes and making a checklist for what I need to backup and where it's stored. Currently trying to figure out if I want to move some directories for consistency. Can I just do docker-compose down edit the mountpoints in docker-compose.yml and run docker-compose up to get a working system?

My own city, which is not Indianapolis, has a few sections of trail that locals tend to avoid because they're congested with homeless camps and while I've never had an issue, there is a perception of danger and it doesn't make for a relaxing ride. I go in the day and in a group, but not alone at night.

I am planning a daytime ride in Indianapolis along the Monon Trail from Carmel to Downtown, then circling back using the White River. Are there any sketchy or outright dangerous sections of trail I should know about?

The city glows bright red on crime maps, but so does almost every downtown in every US city over 500,000 people.

I've looked at what's available online. A lot of what I could find was either generalized or dated so I'm still looking for additional perspectives.

Hi Folks,

We recently found a VHS video of a friend's scumbag parent getting kicked out of the house back in the 90s. We really want to digitize this video, but I can barely get it to play. The two VCRs I've tried keep having issues and trying to chew the tape or just stop and turn off. I wonder if the reels are too hard to move. We know the video is on there because we watched it a few days ago and it was decent save some typical VHS fuzzies and the occasional drop out of the picture.

If it would play, I would just use an adaptor and capture the VCR output. What I need is some advanced data recovery.

Is there a service out there that can directly scan and digitize the ribbon itself or recover a cassette that hasn't weathered the years so well? I'm happy to pay for this service, but I'm looking a skilled service that isn't just going to do what I tried to do, but can actually deliver results in a difficult case.

Can anyone be my hero and help me understand what I'm looking for and maybe help me find a service? Colorado local is great, but mail order is acceptable.

I do have at least 2 more VCRs I could try, but I don't want to do damage.

This is an open ended question. How do you create continuity in how you visualize your fitness journey across devices/platforms?

For example, I have data from my Amazfit, Zepp, Google Fitness days, I currently use a Garmin 530 while cycling and a Fenix 6 Pro Solar for everything else. With Garmin+ hinting at bad things to come and the high prices of Garmin watches I'm considering a possible Polar or a Suunto next. How do you visualize your trends over time?

• do you feed your stats into a spreadsheet?
• Do you use a quantified self app like Exist that pulls data from multiple sources

Another concern of mine is winding up split between ecosystems like if I bought a Suunto watch and eventually replaced my Garmin Edge 530 with a Wahoo device.

I can't pretend that Garmin does this especially well, even when my current devices are all Garmin, but I know my watch measures recovery and readiness after the rides I do on my edge, so I'm never in the dark as to where I stand on my recovery. Using a device only for workouts seems like it would be problematic as fitness isn't just movement, but also how you eat, sleep, etc.

Has anyone else seen this? This seems to be a common pattern lately. Companies will list all their products:

Product X1 Product X2 Product Y1 Product Y2 Product R42 Product F25

... but they don't have a page explaining what the difference between the X line, Y Line, R Line, and F Line actually are. Let's say they are gadgets. Would it hurt them in any way to simply say the X line prioritizes speed, the Y line is backwards compatible with legacy gadgets, the R line is meant for business use, and the F line is experimental form factors. How do you not think to put this info on your page?

I am specifically asking about software and needed libraries, not stuff like Wikipedia or the writings of Ernest Hemmingway.

To keep people from archiving all of github on thousands of shucked external hard drives cobbled together all Frankenstein-y to create a postapocalyptic data center assume a ~1TB storage limitation. Though I'm sure that person exists here on Lemmy somewhere :D

I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

I'm just curious, for those of you with home labs, do you use a testing environment of some kind or do you just push whatever your working on straight to "production

• edit: grammar

I have a

Beelink Ser5 Pro Mini PC, AMD Ryzen 7 5850U(8C/16T, Up to 4.4GHz), 32GB DDR4 RAM 1TB PCIe3.0 x4 SSD Running Spiral Linux (Debian w/ BTRFS Snapshots in GRUB and some other optimizations)

I've been using it as a server with mostly docker containers, rarely taxing it's abilities in any meaningful way. It's a playground that also runs a few serious/useful apps. Storage is largely on my Synology NAS.

My question is this. I hesitate to store data on the minipc as I seem to be ending up with a broken system fairly frequently when upgrading. NAS seem to be more expensive now and I want to add more storage for Tube Archivist. Are there DAS, Raid Enclosures, USB3 disk enclosures that I can plug in that will manage the disks and such, but don't pose a challenge to remount if I destroy and reimage the MiniPC?

I recently found an unopened HP PhotoSmart 6520 in my mother in law's closet. She had it prepared for when her workhorse gave out. I've needed a scanner downstairs and want to figure out if I can safely connect this thing to the network without it bricking itself. You all probably already know HPs reputation and how they do sketchy things like blocking third party ink with firmware updates after the consumer has already purchased the product, or making it so you can't scan if the ink is out. Right now, all I want to do is scan some docs to linux, likely over USB, maybe over the network if I can get it to work. I don't want to rule out that my partner may want to print something.

What is the best way to go about this? Can I block the printer from accessing the internet on my router, but still have devices on the local network print to it? Should I? Can I see somewhere if updates are reported as safe and only then unblock the internet access so it can update?

Problem is, as usual, Google is less than helpful. Does anyone know where I can find a list of which printers were affected and which are still affected?

I'm down to the last few hours of discounts here. I need to get my NAS and my server onto a UPS months ago. Both are already set to come back on when power restores. We rarely have power outages and have solar panels (no house battery though), so a full outage is even rarer.

I understand that a UPS can send a shutdown signal when power is lost. Is this a universal standard or format for this? If so, what keywords should i use when searching for compatible products? My father told me to look for one with Ethernet ports. I just want to make sure everything is compatible. I go out of town occasionally and as well as preventing data loss, I also need everything to go down and come back up automatically so I don't have to call a friend, neighbor, or my spouse to go mess with stuff for me.

UPS brands considered (alternatives welcome): APC, Cyberpower

Systems protected, Synology DS 220+ & BeeLink MiniPC running Debian 12.

Also, for anyone who has helped me out previously in my self-hosted journey, thank you! Things are going great and I have a few useful docker images running various services and have set up grub btrfs snapshots to easily fix my screwups. This community has been incredibly helpful.

Hi folks, I just picked up a Pixel 8 Pro on an early black Friday deal. I've had my previous OnePlus 9 for way longer than the average timeframe and the same with my Oneplus 6 before that.

Looking at cases, I noticed I recognize very few of the manufacturers, basically just Otterbox and Spigen.

If you gravitate towards a particular case manufacturer, I would love to know:

Who makes the best phone cases in 2024?

No limits on style or form, but I don't need rhinestone bling or anything like that.

Hi folks,

You all have been instrumental to my self-hosting journey, both as inspiration and as a knowledge base when I'm stumped despite my research.

I am finding various different opinions on this and I'm curious what folks here have to say.

I'm running a Debian server accessible only within the home with a number of docker images like paperless-ngx, jellyfin, focalboard, etc. Most of the data actually resides on my NAS via NFS.

1. Is /mnt or /media the correct place to mount the directories. Is mounting it on the host and mapping the mount point to docker with a bind the best path here?

2. Additionally, where is the best place to keep my docker-compose? I understand that things will work even if I pick weird locations, but I also believe in the importance of convention. Should this be in the home directory of the server user? I've seen a number of locations mentioned in search results.

3. Do I have to change the file perms in the locations where I store the docker compose or any config files that don't sit on the other end of NFS?

Any other resources you wish to share are appreciated. I appreciate the helpfulness of this community.