Published Jul 29, 2026, 4:00 PM EDT Korbin is a Linux system administrator who spends most of his time in a terminal figuring out how things actually work. Over the last decade he's written hundreds of articles about Linux configuration, troubleshooting weird problems, and using open-source tools in the real world. He also works a lot with Windows systems and networking, especially in mixed environments where things don't always behave the way the documentation says they should. Writing things down is how he makes sense of it all and hopefully saves someone else a few hours. It's become all too common for people to keep the only copy of something that matters to them in the cloud. Keeping wedding photos and years of work in a single folder that's synced to the cloud doesn't treat it like the single point of failure it actually is. As long as the sync icon stays green, everyone considers the data protected. A post on r/DataHoarder this month offers a sobering reminder of why that strategy doesn't constitute a real backup. A Dropbox user discovered that his account had been disabled, with no notification or explanation. Support eventually cited a section of the Acceptable Use Policy covering prohibited imagery. He disputes the finding and suspects the trigger was a home video of his young son riding a cleaning robot around the house. Whether it's a false positive or not, all of his files are now locked away, with no clear answer as to when or if they'll become available again. A single flag took down the entire account And years of unrelated files along with it The Dropbox account contained years' worth of content unrelated to the allegation, including sentimental and irreplaceable files. The customer has requested an export of the unrelated files, with a compromise that the file in question remain permanently inaccessible. Dropbox refused the request and claims the account won't be unlocked. They also won't shed any light on the particulars of what happened, refusing to identify the offending file without going through the proper legal process. At first, this might not sound so bad. Dropbox works by scanning a folder and syncing the content with their servers, so that means the files should still exist in the original folder on his PC, right? That would be the case, but the user had Dropbox's Sync on Demand feature enabled, so some files resided solely on the company's servers. The feature works by showing your file explorer the full contents of your Dropbox, but many entries are placeholders — stubs that get filled with real data the first time you open them. It's a convenient way to fit a 2TB Dropbox onto a 256GB laptop, but it also means that many of the local copies on your disk are just pointers to Dropbox's servers. Once the Dropbox account gets disabled, you're stuck holding the pointer and nothing else. That's a different kind of failure that most home labbers probably aren't prepared for. Normally, we worry about failing disks, silent data corruption, or a physical disaster wiping out our files. If any of your files are stored in cloud storage, this case exemplifies yet another type of failure that everyone needs to incorporate into their backup strategy. From reading the post, I'd say chances are slim that Dropbox will ever release any of the user's files, and he'll have to chalk this experience up to a lesson learned the hard way. At least his sharing of the events may save someone else's files from the same fate. A NAS puts you in charge of your storage As well as any potential failures that occur One reason I'll always advocate for a self-owned NAS is that it eliminates this entire category of failure, since no terms of service sit between me and the hard drives in my house. You don't need any special hardware for a NAS, either. Mine is just an older desktop PC that didn't have a purpose after I decided to upgrade. TrueNAS is free and easy to set up. Throwing my spare drives into the box and setting up a RAIDZ2 pool was straightforward, didn't cost anything, and is now the backbone of my entire home lab. There are still plenty of kinds of failures that I do need to worry about, but at least I'm able to do something about them. With Dropbox or similar cloud storage, I'm at their mercy. If a disk dies, all I need to do is swap it out and let the pool resilver. Even during that process, I don't lose any access to my data. Snapshots have also saved me from myself a few times, allowing me to roll back mistakes by restoring a deleted file or reverting to an old save. The cloud still does one thing my NAS doesn't It gives me an offsite copy of my files There's still at least one good case for keeping cloud storage. My NAS is a single box that sits in my office, and, however unlikely, it's still susceptible to a fire, flood, or burglary that could take out every copy of my files at once. Dropbox works well for geographic redundancy, since the files will continue living on its servers even if my NAS explodes. It's a convenient way to keep an extra copy of your files around and requires barely any extra configuration or setup, since Dropbox handles all the infrastructure. I've opted for a rented VPS to meet the offsite requirement, but cloud storage is a viable choice as long as it's not the authoritative source for any important files. Cloud subscriptions make sense, but I mostly use a rented VPS because I'd rather the offsite copy live on a box I administer myself. Regardless of how you achieve an offsite backup, the biggest takeaway from the poster's experience is: cloud synchronization alone is not a backup. Own the files and rent the redundancy It's scary to think that access to your files can be revoked by a process you can't see or appeal. But it's one of the many reasons that I advise people to grab an old PC and a few hard drives, and install TrueNAS to start managing their own files. The final piece of the puzzle is syncing the files somewhere offsite; then you've got a solid 3-2-1 backup strategy that doesn't hinge on cloud storage having your back.
A Dropbox user lost everything and proved why you need a NAS, not cloud storage
Full Article
Original Source
Read the full article at Xda-developers →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.