Nobody decides to run their family's memories on an untested box with no backup. It just happens - one auto-upload at a time. This is the most common Nextcloud story in the world, and there is a calm way out of it.
It begins innocently, exactly as the video intends: install Nextcloud in five minutes, just to see it. Then someone installs the phone app. Auto-upload gets switched on - it is right there, why not. The spouse starts using the shared folder. A year later, two thousand photos exist only on that box, the admin password is in one person's head, and nobody ever made a backup, because it was only a test. If any of that sounds familiar, this page is yours.
Notice that nobody in the story did anything foolish. The install worked. Using it was the point. Auto-upload is a feature doing its job. The drift is structural: a test has no checklist, no backup and no owner - and a successful test quietly acquires users anyway. Each small step was reasonable; the sum of them is a production system with a test's safety arrangements.
Offices do this too, with higher stakes: the quick install a technician spun up "to evaluate" is, eighteen months later, where the shared drive lives. The story scales; the fix is the same.
Read the panel above and count honestly. Dependence - would anyone complain if it vanished tonight? Uniqueness - do files exist here and nowhere else? Automation - is anything flowing in without a human deciding, like phone uploads? Knowledge - is the admin password, and the knowledge of where the box even is, held by exactly one person? Protection - is there a backup, tested, on a different device?
Two or more yes-answers and the word "test" is now a fiction. That is not a failure - it is a status report, and status reports exist so you can act on them.
The fix is a week of small moves, in this order:
Notice what is not on the list: reinstalling. A drifted-into-production install is usually promoted in place far more safely than it is rebuilt in a panic.
End the week by choosing, out loud, one of two endings. Either promote it - it is production now, it gets a backup routine, an owner and a monthly five-minute check - or retire it deliberately, moving everyone and everything off it first and switching it off second. Both are respectable. The only wrong answer is the third one: continuing to call it a test while a family's archive accumulates on it.
The five-minute install did nothing wrong. It succeeded, and success has a maintenance bill. Pay the small one from this page, and the story ends the way it should: unremarkably.
See how the test begins - five harmless minutes - and then decide, with this page, what yours has become.
Watch Full VideoNo - running one knowingly is fine. Plenty of people evaluate Nextcloud for months on a spare machine with throwaway files. What is wrong is the unknowing part: real files and real dependence arriving while the setup still has a test's arrangements - no backup, one password holder, no owner. The fix is not guilt; it is promoting the setup to match its real status.
A copy, today, onto a device that is not that box - an external drive or another computer - before you change, clean or upgrade anything. Do not start by tidying the photo library or reorganising folders; every change before the copy exists is risk without benefit. Once the copy is verified by opening a few files from it, work through the day-two checklist at a calm pace.
Usually not as the first move. Promote it in place first - backup, accounts, two-factor, warnings cleared - because that removes the real dangers this week, on the system people already use. A full rebuild or migration can follow later, calmly, if you outgrow the package; the upgrade-path page in this series covers that move. Reinstalling in a panic is how small problems become lost weekends.