If you ever decide to host your own, via VPS or sth consider checking docker-mailserver and watchtower. First takes care of the mail stuff and the second updates your containers frequently so you will not have to manually update to new versions of the container (for security patches etc.).
didn’t have money for an external hard drive or anything like that growing up, so a lot of stuff got lost over the years. but when i upgrade my NAS’ hard drive i will buy an enclosure and scrape all of the important stuff together. like recovery codes for my 3ds collection, old photos of my late cat. that kinda stuff. then i’ll see how frequently i’m gonna update the data.
Se if you can get a DVD or Blu-ray writer and backup stuff to DVD or Blu-ray discs. If you keep the discs in individual jewel cases or in a disc wallet they keep very well.
When you use deduplication on the backup side you can do backups every minute without needing much storage. When the backup programm looks at the filesystem to determine which file has changed, the CPU only need to process the changed files.
For my personal devices i do daily backups. There is not enough change every day.
Personal and business are extremely different. In personal, you backup to defend against your own screwups, ransomware and hardware failure. You are much more likely to predict what is changing most and what is most important so it’s easier to know exactly what needs hourly backups and what needs monthly backups. In business you protect against everything in personal + other people’s screwups and malicious users.
If you had to setup backups for business without any further details: 7 daily, 4 weekly, 12 monthly (or as many as you can). You really should discuss this with the affected people though.
If you had to setup backups for personal (and not more than a few users): 7 daily, 1 monthly, 1 yearly.
Keep as much as you can handle if you already paid for backups (on-site hardware and fixed cost remote backups). No point having several terabytes of free backup space but this will be more wear on the hardware.
How much time are you willing to lose? If you lost 1 hour of game saves or the office’s work and therefore 1 hour of labour for you or the whole office would it be OK? The “whole office” part is quite unlikely especially if you set up permissions to reduce the amount of damage people can do. It’s most likely to be 1 file or folder.
You generally don’t need to keep hourly snapshots for more than a couple days since if it’s important enough to need the last hours copy, it will probably be noticed within 2 days. Hourly snapshots can also be very expensive.
You almost always want daily snapshots for a week. If you can hold them for longer, then do it since they are useful to restoring screwups that went unnoticed for a while and are very useful for auditing. However, keeping a lot of daily snapshots in a high-churn environment gets expensive quickly especially when backing up Windows VMs.
Weekly and monthly snapshots largely cover auditing and malicious users where something was deleted or changed and nobody noticed for a long time. Prioritise keeping daily snapshots over weekly snapshots, and weekly snapshots over monthly snapshots.
Yearly snapshots are more for archival and restoring that folder which nobody touched forever and was deleted to save space.
The numbers above assume a backup system which keeps anything older than 1 month in full and maybe even a week in full (a total duplicate). This is generally done in case of corruption. Keeping daily snapshots for 1 year as increments is very cheap but you risk losing everything due to bitrot. If you are depending on incrementals for long periods of time, you need regular scrubs and redundancy.
When referring to snapshots I am referring to snapshots stored on the backup storage, not production. Snapshots on the same storage as your production are only useful for non-hardware issues and some ransomware issues. You snapshots must exist on a seperate server and storage. Your snapshots must also be replicated off-site minus hourly snapshots unless you absolutely cannot afford to lose the last hour (billing/transaction details).
I was familiar with just organise my docker-compose containers without any frontend. But I discovered casaOS, which make things pretty simple. An AppStore and a SMB-Shared File manager gave me a really good workflow. Things that aren’t on the AppStore can be handled outside of Casa, too.
PS. But never make the mistake to integrate the outside handled containers, this mess things up.
Thanks, yeah I’ve heard good things about casaOS. I think that I’m trying to move in the other direction though: fewer UI’s and more CLI’s + Configuration files.
Sounds like a connection would work with that setup but it would depend on what you are planning on hosting. Anything that is sensitive to latency would probably not work well. Static sites should be fine though.
Honestly, for personal use I just switched to straight Markdown that I edit with Vim (w/ Vimwiki plugin) or Markor on Android and synchronize with Syncthing. Simple, low effort, portable, does enough of what I need to get the job done.
And if I wanna publish a read-only copy online I can always use an SSG.
I’ve been using Wiki.js since I asked this question a few months ago. I’ve been pretty happy with it. Stores data in text files using markdown and can synchronize a number of backends. I’ve got mine syncing to a private github repo.
If you want to start try to find something used on DBA, like an old laptop. If you are an student, maybe someone in your class upgrades their laptop and you can get it cheap. (Best a laptop where you can remove the battery, plus you need to change a setting so it doesn’t go in standby when closing the lit)
You can add an external hard disk for nextcloud data.
My first home server was an raspberry pi, it’s not great for nextcloud, you need to disable all preview image, and the UI might still be slow. Untop using an microSD card for the OS might randomly break (happens to me, SanDisk).
My second server was my old laptop, I used an laptop with i3 from like 2013 as server for a long long time.
Best thing I can recommend is to not rush and get the first best thing, try to look for a good deal. Start small and you can always increase your server in the future.
selfhosted
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.