How does a Windows-only Application help with GNU/Linux ?
It doesn't.
How does a Windows-only Application help with GNU/Linux ?
Backup shouldn't be complicated. Everything you need is covered with ZFS snapshots/send/receive + rsync + cron jobs. Personally I am quite happy with zfs-autobackup.It doesn't.I'm still looking for a decent Linux Backup program but haven't found one yet.
. This is why my 2 backup servers are still Windows.
![]()
Immutable backups. That's the only way to protect yourself. They can't be overwritten or deleted (unless rotated).Oh yeah I'd be in a big **** if that happened. Same credential everywhere both for root and normal User. Once again tied to that Issue with Salt and lack of being able to deploy Credentials.
I could in Theory change everywhere except my Workstations, and store the passwords in Bitwarden, but then it's also how to unlock in that event where I got no SSH / Clevis access at boot. Entering 64 Characters via IPMI Web Interface isn't fun.
True, but arguably, with immutable backups, it doesn't really matter. Once the backup is written, it is written in stone until you delete/rotate it. Even admin credentials can't modify it.But at the risk of stating the obvious, make sure the backup machine has different admin credentials than the rest of the network.
Isn't that the whole mess that happened back then with the Merging/Aquisition of Hitachi / HGST into WD, then Toshiba taking over ex-Hitachi business, now split into Kioxia ?More worrisome the drive is probably at least 6 years old.
and Most worrisome the listing includes a pic of a Toshiba drive instead.
The backups would be on a hardened repo. As an e.g. with Veeam:But that's the thing I don't get. There is nothing you can setup with root privilege that can't be removed with the same privileges. Assume a semi-competent malware takes control of your backup machine. What will protect those files? He can simply copy an encrypted version of those files locally then delete all backup data.
I was looking for Restic when I found Backups. Restic is a CLI only program and I prefer a GUI.
A) Most malware isn't that complicated. The stuff that looks for things on the network is going to be going after common things, off the shelf (both consumer and pro) systems, open SMB shares, etc.But that's the thing I don't get. There is nothing you can setup with root privilege that can't be removed with the same privileges. Assume a semi-competent malware takes control of your backup machine. What will protect those files? He can simply copy an encrypted version of those files locally then delete all backup data.
The only solution is WORM tape thenNot quite sure how that works.
They say Certificate based Authentication ... How is that different from just using SSH with Certificates (yes ... there is actually an Option to add Certificates to OpenSSH on top of using the Private & Public Key Pair).
Also in that Case, if your management Client gets taken over, then you will be able to connect to the Backup Machine and delete the Backup.
A) Most malware isn't that complicated. The stuff that looks for things on the network is going to be going after common things, off the shelf (both consumer and pro) systems, open SMB shares, etc.
B) Failing a vulnerability a remote system set up with a decent level of login protection, such as a combination of: SSH key only login, good passwords, MFA, no direct root, setting your "backup sync" users to not allow a full shell, not using the default SSH key or location on the client system, not having ANY of the remote login users be SUDOers, having the password to elevate to root/admin be DIFFERENT than any of the remote login passwords. Or the ultimate paranoia, admin login not possible from client system.
C) You are generally NOT going to deal with a direct hack or super sophisticated/targeted malware, the less "like" other people your system is the less things with impact you "fully". ZFS snapshots from a desktop replicated to another machine is going to be super niche for consumers, and somewhat niche for even business.
D) Your NAS is and always should be only PART of your backup solution. 3-2-1 rule or as close as you can get.
This is the primary reason why you are struggling with Backup on Linux. GUI are much more complicated to create than a CLI, and most developers just want to maintain something simple.I was looking for Restic when I found Backups. Restic is a CLI only program and I prefer a GUI.
I'm still looking, being limited to one backup is profoundly stupid. as is the fact that it's so difficult with Linux and so stupid easy with windows. CLI is out of the question, tho it made be easy to code it's anything but to use. It's like groping in the dark and never really knowing if you got it right or not. Plus it's much easier to destroy your data with cli than it is with a gui. And typos and syntax errors will drive you insane. And finally, I'm of the opinion that it's a bad idea to put all your eggs in one basket by using backup software that uses an archive. And as for security and encryption, I don't need any of that and would rather not have to deal with it.