201–210 of 360 posts
Earlier quoted context omitted.
You can use Synology Hyper Backup (or any cloud backup program) and an AWS S3 compatible provider, such as Backblaze.
what would be an option to still do it locally? without sending it to the cloud? probably needs a good compression
I've put some work into customizing my Synology NAS(s), and they're doing a lot for me right now, so it will be painful to transition, but I'm going to bite the bullet and do it anyway, because they've become irredeemable.
The year is 2025. Delivering a good product is not considered profitable enough anymore. If a company or product is beloved by customers then that means it doesn't squeeze them to the max. This is clearly money left on the table that someone will sooner or later extract. High-end brands are not exempt from this.
Easily explained: when times are tough, delivering growth naturally is hard. Squeezing the customer is the lowest hanging fruit. Sure, long term reputation is severely damaged, but why would decision makers care? Product owners interests are not aligned with interests of the company itself. Squeeze the customer, get your miniscule growth, call it "unlocking value", get your bonus, slap it onto your resume and move on…
Earlier quoted context omitted.
My main issue with their system is how closed it is. I got an issue where mind would randomly start writing disk like crazy and maxing cpu usage, to the point I was bothered by the noise. I’d stop all containers, leave it as close to idle as I could manage, still spiking. There was no way I could learn what was causing it. I would like to assume it was a disk maintenance process or something, but for all I know it co…
There are guides on how to mainline Synology NAS's to run up-to-date debian on them https://forum.doozan.com/list.php
FWIW the new Ugreen NAS run Debian. I don't know a ton about it, but it's be great if they could stay a little more up to date. This Synology story with ancient forks & weird encryption sounds truly bogus.
Earlier quoted context omitted.
Are you sure they survive for the time period you intend them to? When I was a teenager, I though the DVDs and BluRays I burned would be forever - 15 years later I am very unhappy to find that some of them started to crack and flay - it's a pain to keep checking them. Nothing like the guarantees a NAS + Cloud backup could provide.
NAS also fail, and cloud backups can be taken away without notice. Hence why multiple copies.
Earlier quoted context omitted.
Why do they need to use an old Brtfs fork? What is missing in the mainline kernel for them?
As I understand it, they forked years ago when btrfs was very much not ready to be used for production NAS storage. Their value prop was they took it and added lots of their own special patches that they claimed made it highly dependable. Over time their advantage has eroded as upstream has caught up, to the point that it looks ridiculously out of date today.
Not only that, but their security situation is terrible. Their OS is full of EOL'ed stuff. On products you can buy TODAY, you find: - Their Btrfs filesystem is a fork of a very old branch and doesn't have modern patches - A custom, non standard, self built, ACL system for the filesystem - Kernel 4.4 - PHP 7.4 (requirement for their Hyperbackup app) - smbd 4.15 - PostgreSQL 11.11 - smbd 8.2p1 - Redis 6.2.8 - ... They…
The encryption is also broken. If you use encrypted shared folders, you have an arbitrary filename limit ( https://kb.synology.com/en-ro/DSM/tutorial/File_folder_path_... ). If you use volume encryption, your encryption key is stored on the NAS itself, which is capable of decrypting the data, unless you buy a second Synology NAS ( https://blog.elcomsoft.com/2023/06/volume-encryption-in-syno... ) to act as a key vault…
Earlier quoted context omitted.
The filename limit comes from ecryptfs ( https://www.ecryptfs.org/ ) which is what Synology uses for encrypted shared folders. As for full disk encryption, you can select where to store the key, which may be on the NAS itself (rendering FDE more or less useless) or on a USB key or similar.
For full disk encryption you need DSM >= 7.2 and you can either, store it locally (useless) or in a KMIP server. [0] As a KMIP server you use: - Another Synology NAS with DSM >= 7.2 - A KMIP compatible key server Except for the demo implementation that Synology uses (PyKMIP), all the KMIP compatible servers I've found have licenses in the tens of thousands a year. So if anybody has any suggestions to substitute PyKMI…
Used to do the same thing at EMC back in the 90s-early 2000s with Symmetrix. The cover story was that the EMc-branded drives, which were marked up like 1000x had “special firmware”.
The reality was that it was to prevent procurement guys from putting a BOM spreadsheet in front of the sales rep and saying “why are you charging me $2M for $100k of parts I can buy at Fry’s?