In some cases, users or institutions choose to place the sync folder on a network drive. This is not impossible, but SURFdrive advises against it and only supports it to a limited extent. This causes the following issues:
- Once the network is not accessible, your files will not be available. The advantage of SURFdrive is precisely that files are available, even when there is no network connection.
- Local changes are not always noticed, so these changes are not synchronized to the server. This has to do with the fact that in certain environments no so-called 'filesystem events/filesystem handlers' come from the network drive.
Workaround
For the second problem, there is a workaround by force synchronizing. To do this, the surfdrive.cfg file must be modified.
By default, this is in the following location:
C:\Users\<username>\AppData\Roaming\SURFdrive\surfdrive.cfg
This should be put in:
[SURF drive]
remotePollInterval=30000
forceSyncInterval=40000
fullLocalDiscoveryInterval=120000
notificationRefreshInterval=120000
For more information about this topic, see: https://doc.owncloud.com/desktop/advanced_usage/configuration_file.html
Solution
We therefore advise not to use the network drive. If there is little space available locally, you can also choose to sync only a part to your local work PC. You can uncheck folders within the SURFdrive client. These folders then remain in the web interface (and on any other desktops), but are no longer present on your work PC.