• 1 Post
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle


  • TIL about Fedora, last I knew it was a rolling bleeding edge OS. Clearly lots of movement in the Red Hat camp.

    As for gaming, drivers were not the problem for me. Getting games to run with ease was. On OpenSUSE, I just install Steam, enable Proton and basically go at that point. Red Hat was non-trivial to do this. Could be a skill issue, but I had a better time getting going with OpenSUSE TW.


  • Sort of, OpenSUSE Tumbleweed. I started on OpenSUSE Leap but had issues getting things like GPU and Steam working. Red Hat was also a non-starter because of the lack of gaming functionality.

    TW works great for gaming and the enterprise features I care about (like domain joining) work out of the box. Its certainly harder to set up than something more geared towards home use (typically one of the various the downstreams of Debian or Arch) but that doesn’t bother me.


  • Second to this - for what its worth (and I may be tarred and feathered for saying this here), I prefer commercial software for my backups.

    I’ve used many, including:

    • Acronis
    • Arcserve UDP
    • Datto
    • Storagecraft ShadowProtect
    • Unitrends Enterprise Backup (pre-Kaseya, RIP)
    • Veeam B&R
    • Veritas Backup Exec

    What was important to me was:

    • Global (not inline) deduplication to disk storage
    • Agent-less backup for VMware/Hyper-V
    • Tape support with direct granular restore
    • Ability to have multiple destinations on a backup job (e.g. disk to disk to tape)
    • Encryption
    • Easy to set up
    • Easy to make changes (GUI)
    • Easy to diagnose
    • Not having to faff about with it and have it be the one thing in my lab that just works

    Believe it or not, I landed on Backup Exec. Veeam was the only other one to even get close. I’ve been using BE for years now and it has never skipped a beat.

    This most likely isn’t the solution for you, but I’m mentioning it just so you can get a feel for the sort of considerations I made when deciding how my setup would work.


  • As others have mentioned its important to highlight the difference between a sync (basically a replica of the source) vs a true backup which is historical data.

    As far as tools goes, if the device is running OMV you might want to start by looking at the options within OMV itself to achieve this. A quick google hinted at a backup plugin that some people seem to be using.

    If you’re going to be replicating to a remote NAS over the Internet, try to use a site-to-site VPN for this and do not expose file sharing services to the internet (for example by port forwarding). Its not safe to do so these days.

    The questions you need to ask first are:

    1. What exactly needs to be backed up? Some of it? All of it?
    2. How much space does the data I need backed up consume? Do I have enough to fit this plus some headroom for retention?
    3. How many backups do I want to retain? And for how long? (For example you might keep 2 weeks of daily backups, 3 months of weekly backups, 1 year of monthly backups)
    4. How feasible is it to run a test restore? How often am I going to do so? (I can’t emphasise test restores enough - your backups are useless if they aren’t restorable)
    5. Do you need/want to encrypt the data at rest?
    6. Does the internet bandwidth between the two locations allow for you to send all the data for a full backup in a reasonable amount of time or are you best to manually seed the data across somehow?

    Once you know that you will be able to determine:

    1. What tool suits your needs
    2. How you will configure the tool
    3. How to set up the interconnects between sites
    4. How to set up the destination NAS

    I hope I haven’t overwhelmed, discouraged or confused you more and feel free to ask as many questions as you need. Protecting your data isn’t fun but it is important and its a good choice you’re making to look into it


  • Back in the day when the self-hosted $10 license existed I was using JIRA Service Desk to do this. As far as ticketing systems go it was very easy to work with and didn’t slow me down too much.

    I know you don’t want a ticket system but I’m just curious what other people will suggest because I’m in the same boat as you.

    Currently I haphazardly use Joplin to take very loose notes and sync them to Nextcloud.

    If you want a very simple option with minimal setup and overhead you could use Joplin to create separate notes for each “part” of your lab and just add a new line with a date, time and summary of the change.

    I do also use SnipeIT to track all my hardware and parts, which allows you to add notes and service history against the hardware asset.

    Other than that, I’m keen to see what everyone else says


  • Jumping on the OpenSUSE bandwagon. I use it daily, have been running the same install of Tumbleweed for years without issue. I’m using KDE Plasma which it let’s you choose as part of the installation which fulfils that requirement for you as well.

    If you’re familiar with Redhat you’ll feel at home on it. Zypper is the package manager instead of yum/dnf and works really well (particularly when coping with dependency issues.

    I’ve worked with heaps of distros over the years (Ubuntu, Debian, Fedora, RHEL, old school Red Hat, CentOS, Rocky, Oracle, even a bit of Alpine and some BSD variants) and OpenSUSE is definitely my favourite for a workstation.






  • Whilst I agree and sympathise with people on how difficult it is to change your primary email address (been there), the outcome will be better for them. They are no longer wedded to an ISP purely because all their mail goes there.

    To liken it to something more tangible; when you move house, you need to change your mailing address. For renters, that can be often and is just as painful. Or when your phone number changes and you have to update your contacts. The difference here is who is pulling the trigger; the end user vs the provider.

    Gmail is a great option, as is Proton Mail for the security conscious and tech savvy.

    This isn’t to excuse the ISPs; it’s a shitty move on their part and the people using these mail accounts will likely be older technically challenged folks, but it is a logical one from a technical perspective. They may have also inadvertently taken the only thing away that’s creating stickiness between them and their customer and driven them into the arms of another ISP.



  • I’m the admin of krabb.org, honestly I’m loving it. There is a learning curve, particularly for non-technical folks, but that will get easier as time goes on.

    As an admin, it is far easier to “jump start” an empty Lemmy instance with content from other instances than it is to do with Mastodon and Pixelfed.

    Where we need to improve is the mobile apps, documentation and providing ways to make it easier for small instances to get new users. These are all very much in the spotlight and improving every day (especially the apps), so I’m confident we can get there

    Tldr: it good, do like


  • I might cop some flack but I use Cisco, they’re rock solid, last for years and just work with minimal issues and I’ve not run into problems with hardware under performing or firmware bugs like I have on others.

    That said, Ubiquiti makes fantastic hardware, I believe Mikrotik does too.

    You can absolutely buy open hardware that allows you to install custom switching OS; Dell and Mellanox make them as do many other manufacturers (I think even Facebook has a hardware switch, not that I’d buy it lol). One of the more common OS to install on them is Cumulus Linux and a lot of these use “spine leaf” topologies.