Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Sorry if I am unable to provide specific details for the queries. I don't have answers to most of them myself which is why I was hoping what the safest bet for these situations would be to implement.
Highly likely they would be installing new software
I don't know much about its use case, although it won't be too intensive since they probably have a separate machine for heavier work.
Backup storage option wasn't proposed at all. I'm thinking of proposing to implement one.
I expect between 10-20 users.
User permissions requirements wasn't discussed as well, although I wouldn't expect there to be any need to grant everyone admin privileges
Don't know about the criticality of data. I could only speculate to be considerable by default.
This basically means that the system will rot over time and will need to have someone who knows what they're doing to maintain it. If they don't know enough to do the initial setup, then I would worry about how quickly it would go awry after you no longer have access. given the number of users and the assumed criticality of the data, I would have a long conversation about what can happen and what their plans are
I personally would not do this. There are so many red flags.
Backup is step one, or even step 0, of setting up a server. The amount of frustration and even job loss a backup can prevent is always worth the expense of time/money.
Backup can be setup scripts/config files/automation if the data doesnt matter, but you do need it. Also, even if they say the data doesn't matter, the data almost always matters. It may not now, but it will in 3 years when people use the server for real work and everyone just doesnt even begin to think about a backup until the server fails one day and they lose years worth of their grant and thesis data.
Backups can be simple, they can be complex. They can be free or pay, they can have gui or just be scripts. Settle on one that you can make work, and CHECK THEM OCCASIONALLY with test restores of at least a few files. If you dont test and find a working backup, you have hope, not resiliency.
Could you suggest what would be the most appropriate backup solution in this case? I could also ask them to arrange a backup drive or a cloud provider if needed.
Depends on what you're doing a bit. Databases? Hypervisors? Just files? If all of the above, its best to use an actual product this. Either foss like borgbackup or Urbackup, or something like Veeam which is a popular pay option.
If its a proxmox hypervisor, they have their own free backup appliance, but you need a second physical server to run it on.
If it's just databases, most have a built in way to take a backup. Just google the name and backup. Make sure it's running automatically and is moved to a separate server on each run.
For files, rsync is a great option.