# 100% Data loss when moving between folder **URL:** \ **Category:** 📱 Desktop & mobile clients\ **Tags:** desktop-client, external\_storage, smb, featurerequest\ **Created:** [January 24, 2026, 8:26am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229 "2026-01-24T08:26:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 24, 2026, 8:26am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/1 "2026-01-24T08:26:55Z")
**Environment** - Client: Windows 11, Nextcloud Desktop **4.0.5** (Jan 2026) - Server: Nextcloud 32.0.5 with **two local external storages** - Desktop client syncs **two separate folders** : `/SAMBA` and `/LOCAL` **Initial state** - Large dataset fully present locally under `/SAMBA` (already synced). - Goal: move data from `/SAMBA` to `/LOCAL`. **Action (on the workstation)** - In the local Nextcloud folder, user **moves** data from `/SAMBA` to `/LOCAL`. **Expected** - Safe transfer: data appears on the server under `/LOCAL`, then the server copy under `/SAMBA` can be removed without loss. **Actual** 1. Locally, the move is **instant** (local FS operation). 2. Client starts **upload** of the moved data to server’s `/LOCAL` (slow due to large size). 3. In parallel, client detects the files no longer exist under `/SAMBA` and **deletes them on the server**. 4. The upload to `/LOCAL` **aborts/fails** (timeout/error on slow external storage). 5. Result: files are **deleted on `/SAMBA`** and **not fully present on `/LOCAL`** → **data loss**. ---
**Author:** ![Mornsgrans](https://help.nextcloud.com/user_avatar/help.nextcloud.com/mornsgrans/32/40386_2.png) [@Mornsgrans](https://help.nextcloud.com/u/Mornsgrans)\ **Post date:** [January 24, 2026, 9:52am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/2 "2026-01-24T09:52:28Z")
Did you try occ files:scan after moving the files? > **[Using the occ command — Nextcloud latest Administration Manual latest...](https://docs.nextcloud.com/server/28/admin_manual/configuration_server/occ_command.html#file-operations-label)** ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 24, 2026, 10:04am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/3 "2026-01-24T10:04:49Z")
No, because the client has deleted all of the data. Nothing to scan anymore. 100% data loss. ---
**Author:** ![adelaar](https://help.nextcloud.com/letter_avatar/adelaar/32/5_5575768a8748004e209b776fc1b2916d.png) [@adelaar](https://help.nextcloud.com/u/adelaar)\ **Post date:** [January 24, 2026, 11:09am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/4 "2026-01-24T11:09:01Z")
What’s with the **Trash** in web-Interface of your NC-Server? ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 24, 2026, 11:11am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/5 "2026-01-24T11:11:14Z")
Trash is not installed on the Nextcloud server. But nothing could be found in Trah because the files had been **moved** and not deleted. ---
**Author:** ![adelaar](https://help.nextcloud.com/letter_avatar/adelaar/32/5_5575768a8748004e209b776fc1b2916d.png) [@adelaar](https://help.nextcloud.com/u/adelaar)\ **Post date:** [January 24, 2026, 11:17am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/6 "2026-01-24T11:17:03Z")
There shall be a Trash by default. See: ![Trash](https://help.nextcloud.com/uploads/default/original/3X/a/2/a226e3508b1ba6726dcca7448c2cce97b3c1a98a.png) here named “Gelöschte Dateien” Either it’s moved or deleted. ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 24, 2026, 11:26am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/7 "2026-01-24T11:26:34Z")
> [@adelaar](#): > > “Gelöschte Dateien” This only appears if you haven’t disabled the “Deleted Files” app. But in my case, it is disabled. ---
**Author:** ![adelaar](https://help.nextcloud.com/letter_avatar/adelaar/32/5_5575768a8748004e209b776fc1b2916d.png) [@adelaar](https://help.nextcloud.com/u/adelaar)\ **Post date:** [January 24, 2026, 11:29am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/8 "2026-01-24T11:29:27Z")
Okay, so you need to restore the files from backup. If you don’t have a backup, the files are meaningless and their loss is not tragic. ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 24, 2026, 11:45am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/9 "2026-01-24T11:45:49Z")
Of course, it doesn’t matter at all, because you’re just playing around with it. 😉 But I didn’t expect that you would need a backup just because you want to [rename a folder from uppercase to lowercase](https://help.nextcloud.com/t/100-data-loss-instead-of-renaming-a-folder/239231) letters! ---
**Author:** ![adelaar](https://help.nextcloud.com/letter_avatar/adelaar/32/5_5575768a8748004e209b776fc1b2916d.png) [@adelaar](https://help.nextcloud.com/u/adelaar)\ **Post date:** [January 24, 2026, 11:51am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/10 "2026-01-24T11:51:24Z")
> [@Sanook](#): > > Client: Windows 11 So a Windows System was involved. But: > Windows treats folder and file names as **case-insensitive** by default, meaning “FolderA” and “foldera” are considered identical, and you cannot have both in the same location So what you did must cause Problems. Addendum: > **Renaming Issues:** If you try to rename a folder from “data” to “DATA”, Windows might not accept it immediately because it doesn’t see a difference. A common trick is to rename it to something else first (e.g., “data1”) and then rename it to the desired casing (“DATA”). ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 24, 2026, 12:12pm UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/11 "2026-01-24T12:12:38Z")
> [@adelaar](#): > > Windows might not accept it immediately because it doesn’t see a difference Only within the /SAMBA folder. Here, the folder is **deleted** instead of renamed. But it does work within the /LOCAL folder. Here you can rename “TEST” to “Test” on Windows 11. ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [January 24, 2026, 8:21pm UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/12 "2026-01-24T20:21:15Z")
Like always without logs nobody can help - collect your client log - collect your server log - create Github issue describing the problem - add you logs there fortunately desktop client creates very verbose log which is usually useless but in this situation it might help troubleshooting. ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 25, 2026, 3:26pm UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/13 "2026-01-25T15:26:53Z")
In Debian 13 with Nextcloud Desktop 3.16.7, you can rename a folder from “TEST” to “Test” in the /SAMBA folder, but an error message appears in the client: ![error_renaming_uppercase_to_lowercase](https://help.nextcloud.com/uploads/default/original/3X/4/9/498c14aad18389e03df021717a417f22da52e9b7.png) And then there are two folders in the client: ‘TEST’ and “Test,” even though only the “Test” folder exists on the server: ![error_renaming_uppercase_to_lowercase1](https://help.nextcloud.com/uploads/default/original/3X/9/5/95bf08ff086dbead5fec9feff51d7b763fac3298.png) But at least Linux doesn’t delete the folder, because if you do that with Windows, you’ll need the backup because Windows deletes the folder instead of renaming it. ---
**Author:** ![adelaar](https://help.nextcloud.com/letter_avatar/adelaar/32/5_5575768a8748004e209b776fc1b2916d.png) [@adelaar](https://help.nextcloud.com/u/adelaar)\ **Post date:** [January 25, 2026, 3:54pm UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/14 "2026-01-25T15:54:23Z")
> [@Sanook](#): > > you can rename a folder from “TEST” to “Test” in the /SAMBA folder For me its not clear what is the OS of the Host of the /SAMBA folder? Debian 13 with Nextcloud Desktop 3.16.7 seems to be a Client. > [@Sanook](#): > > if you do that with Windows, you’ll need the backup because Windows deletes the folder instead of renaming it I did for Testing reanming on Client Win 11 Prof. a Folder from Podcasts → PodCasts. But unsimilar to you your Test → TEST is a Subfolder of the originally synced folder. LIke `Podcasts/Test`. So that was different to my Test. In my Test nothing was deleted. Win renamed Podcasts into PodCasts and the Client (Nextcloud-4.0.6-x64.msi) did not even noticed the name change. In the Client PodCasts was still Podcasts. ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 25, 2026, 3:57pm UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/15 "2026-01-25T15:57:23Z")
> [@adelaar](#): > > what is the OS of the Host of the /SAMBA folder? Sorry i forgot to mention that the /SAMBA folder is hosted on a Synology DS220J. ---
**Author:** ![adelaar](https://help.nextcloud.com/letter_avatar/adelaar/32/5_5575768a8748004e209b776fc1b2916d.png) [@adelaar](https://help.nextcloud.com/u/adelaar)\ **Post date:** [January 25, 2026, 4:03pm UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/16 "2026-01-25T16:03:16Z")
> [@Sanook](#): > > Synology DS220J I was not familar with Synology DS220J. SO i googled: > The Synology DS220j runs on Synology DiskStation Manager (DSM), a browser-based, Linux-based operating system designed to manage the NAS. ---
**Author:** ![adelaar](https://help.nextcloud.com/letter_avatar/adelaar/32/5_5575768a8748004e209b776fc1b2916d.png) [@adelaar](https://help.nextcloud.com/u/adelaar)\ **Post date:** [January 25, 2026, 4:15pm UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/17 "2026-01-25T16:15:50Z")
I suspect both, the Synology DS220J and the NC-Server Hardware are both placed in your local network. So i ask myself why using a SAMBA-share instead of a NFS-Share? Since both systems most likely use a Linux-based operating system, in my opinion NFS is preferable over SAMBA. ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 26, 2026, 7:09am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/18 "2026-01-26T07:09:24Z")
I have now deleted the Samba share and expanded the [golden rule](https://help.nextcloud.com/t/what-is-it-with-nextcloud-updates/220217/2): > **Don’t mix Samba with Nextcloud!** ---
**Author:** ![Sanook](https://help.nextcloud.com/user_avatar/help.nextcloud.com/sanook/32/13847_2.png) [@Sanook](https://help.nextcloud.com/u/Sanook)\ **Post date:** [January 24, 2026, 10:13am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/19 "2026-01-24T10:13:24Z")
Just wanted to rename a folder from “DATA” to “Data” but the Nextcloud Client has deleted the folder! 100 % data loss (!) The “DATA” folder is a subfolder of an external Samba share which is mounted via fstab to the filesystem of the Nextcloud server. Setup see: [100% Data loss when moving between folder](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229) ---
**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\ **Post date:** [January 26, 2026, 8:33am UTC](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229/20 "2026-01-26T08:33:14Z")
You renamed it on the server or client-side? And is it just the client that deleted the folder on the client, or as well on the server (and SMB)? [Next page](https://help.nextcloud.com/t/100-data-loss-when-moving-between-folder/239229.md?page=2)