[docs] Mention UNC path workaround to create network drive
This commit is contained in:
@@ -14,9 +14,21 @@ directly stream chunks of Google Takeout zips that are stored on network drives.
|
||||
|
||||
In particular, the folder watch functionality suffers a lot since the app needs
|
||||
access to file system events to detect changes to the users files so that they
|
||||
can be uploaded whenever there are changes.
|
||||
can be uploaded whenever there are changes. Network drives are less reliable in
|
||||
providing these file change events correctly.
|
||||
|
||||
Since are high chances of the user having a subpar experience, we request
|
||||
customers to avoid using the desktop app directly with network attached storage
|
||||
and instead temporarily copy the files to their local storage for uploads, and
|
||||
avoid watching folders that live on a network drive.
|
||||
|
||||
## Exporting to UNC paths
|
||||
|
||||
Generally, exports are likely to work better than imports, since the interaction
|
||||
with the file system is relatively simpler (Note that the app still needs to
|
||||
scan the folder to find existing files, esp. if the continuous export option is
|
||||
enabled).
|
||||
|
||||
A special case is when exporting to a UNC path. In this case, the file
|
||||
separators will not work as expected and the export will not start. As a
|
||||
workaround, you can map your UNC path to a network drive and use that instead.
|
||||
|
||||
Reference in New Issue
Block a user