Synced folder is instandly locally cleared (virtualized) Is that normal?

ℹ️ Support
, ,
1
Support intro

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
  • Operating system and version (e.g., Ubuntu 24.04):
    • replace me
  • Web server and version (e.g, Apache 2.4.25):
    • Linux 3.10.108 x86_64
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • none (not yet, --insecure, testing)
  • PHP version (e.g, 8.3):
    • 8.5.9
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes (but its a new install)
  • When did this problem seem to first start?
    • Its a new install
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Docker using compose from examples, on Synology DSM 7.4
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No for now even --insecure, as I am testing

Summary of the issue you are facing:

So is it normal that when I add a large 160GB folder to sync, that it not only syncs it all, but also instantly deletes all local copies from the laptop so they are virtualized? Even when all of those files were created in the last 2 days?

When I later disabled virtual files, it seems to start work again to copy them back, that part is still running, but I am not at all impressed by this behavior. I though files might eventually be optimized/visualized when they get stale. But right away? On such young files?

Is it possible to disable virtual files based on policy or at user account creation.

I was hoping to use this more as backup/versioning for family members and their PC’s laptop. but if everything gets deleted right away, I am not sure about that.

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.
2

what OS and exact Nextcloud desktop client version is on the laptop? the server version alone doesn’t tell us which virtual-files implementation is running.

virtual files are controlled by the desktop client. you can enable or disable them on that sync connection, and managed account setup supports --isvfsenabled=0. i couldn’t find a documented server policy that waits for files to reach a certain age before making them online-only.

before changing the mode again, check that the whole folder is present in the web interface and keep a separate copy. i also wouldn’t use sync, trash, and versions as the family’s only backup.

if the same client version virtualizes newly uploaded local files again, create a client debug archive and note one affected path and time. that should help separate expected client behavior from a bug.

3

This PC is windows 10, but several would be windows 11

Indeed, the whole virtual file cloud thing is not a good backup. Hence I wanted it turned off. But it was already to late, as it was already doing the virtualization purge. Not that I mind, firstly, I did not seem to loose any data, it just went over the network twice. And secondly, it was a fake data directory created just for this purpose. Which is why I could confidently say all files were recently created.

I also dislike the fact the user can turn Virtual files back on accidentally. I just wanted them to have a transparent experience with continuous backup as well as file versions and ransomware protection.

But I do not want the sync. Even though it is obviously the client that does the work, I was hoping for a server/account side policy that tells the client to forbid virtual files.

Which remind me, the client is just the latest windows x64 from the website 2 days ago. I cannot check the version right now.

BTW: additionally, I was planning to pull a weekly flat filesystem extract from the NAS to an external USB that is mounted/unmounted with a script so it is not even present all the time.