Matrix 👉 @danny:radiantfig.fyi

  • 0 Posts
  • 22 Comments
Joined 30 days ago
cake
Cake day: August 4th, 2026

help-circle


  • good response 👍 bad questioning though 👎 i have a nas, with a raid1 array split out with lvm for separate partitions and users on my server, holding 2x2tb ssd’s. This backs up every night to 2x8tb HDD’s. I have a script that i invoke on my machines manually, that runs rsync on important data, and a backup to the nas raid1 array, overwriting the previous invocation. the HDD’s hold out of sync versions running back to 2 months, which i can dip into any time to recover something. so if something does fail, i wont lose anything. I dont hold offsite backups, so if a nuke lands on my house, i will lose everything. Im comfortable with that level of risk, but i know some people arent. however the op wasnt specifically asking about data backup, they were asking about replication, and how to preserve the initial install and setup to be able to revert and replicate. there are better ways to achieve this than just cloning the disk. Build your own actual distro is the best solution and burn it to a usb as a live disk that is easily installed. or just save a list of packages and configs. cloning a disk is a huge amount of out of date data.



  • For me that would be a waste of time. Just because my setup seems perfect today, tomorrow I might decide to make changes to accommodate a new task. My pc’s are living breathing machines that are always a day or 2 away from a slight tweak.

    When I move to a new machine, I rarely want to replicate another machine I have as then I would have 2 machines setup for the same tasks. Each machine serves a different purpose so needs a different setup.

    If I am replacing a machine, then I would transfer the physical disk itself. Only use clonezilla type tools for replacing a disk, as in replacing the sata SSD holding root with a new fast nvme.

    It’s easy to transfer config files from one machine to another if you want to replicate some specific setups.
















  • im on a basic uk isp, with no fancy router, just the isp provided one. i have a fully exposed web server, im even hosting a lemmy server. Thats my domain, radiantfig.fyi, totally public, has been for nearly 2 years now. From that you can get my servers IP address. My IP is dynamic, changes roughly every 6 weeks. I have a ddns script that updates my server IP address to my domain name provider automatically. I have certbot running updating my TLS certs with lets encrypt, and if a cert dies or fails or is compromised, my server will refuse to serve. Everything is behind an nginx reverse proxy through port 443. I also have an ssh port open on a random port. Have fail2ban setup fairly aggressively to prevent brute force attacks, and have crowdsec which also kind of does the same but in a slightly different way. the internet requires ip addresses. to protect your ip address you have to give somebody elses. that somebody is a 3rd party you have no control or say on the decisions they make. i must have over 20 individual services that are public facing. 3 fully federated, lemmy, forgejo and matrix. Im as secure as any other website. nothing is unhackable, no matter how far down the rabbit hole you go. its all just layers of difficulty.

    The important thing is dont listen to random internet people about security. dont listen to me. dont listen to anybody who tells you they know best. do your own research, understand the options, the risks, the compromises. only then do you put anything up. but if you are going to anxious or worried about your server and data, no amount of security guarantees you safety, so be warned.