winfsp VS dokany

I’ve got a same sort of setup - difference is I have 2 Plex servers, one on the seedbox and one on a local Windows PC. Have you thought about mounting the seedbox locally? I use SSHFS and WinFSP which the seedbox I use supports - another route I took was using FreeFileSync which is an easy to use program that does all sorts of syncs.

In the Windows guest, install https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md#downloads and also https://github.com/winfsp/winfsp/releases/latest.

when talking about rclone for Windows, I find it more than worthy to include WinFSP. It makes it much easier to access the drives mounted with rclone, and even using Windows File Explorer.

If you want to have that drive available in your Windows File Explorer you will need to install another open-source free software called WinFSP (for Windows File System Proxy) which can be downloaded from its website (https://winfsp.dev/), following this link.

You need WinFSP. It's basically the equivalent of FUSE but for Windows. (I think it actually has a FUSE-compatible API so that FUSE filesystems can in theory be ported to Windows easily - guessing rclone is probably using this function actually.)

It's not really the same though. A Projected File System copies the files from the backing store to somewhere on the local file system when requested and then performs IO normally on the local files.

For an actual implementation of userspace filesystems on Windows see dokany: https://github.com/dokan-dev/dokany

Now that you are inside the Mirror folder with cmd, let’s start the Mirror function to attach a NAS or cloud folder as a local disk in order to get recognized by the BB client and be backed up. Write something like (read the dokany documentation for more details here): mirror.exe /r x:\ /l m , where x:\ should be the letter of the folder attached with Raidrive and m:\ the letter you want to assign to the new local disk.

I lead a project that included shipping a filesystem driver and a virtual disk on Windows.

What I did to learn the lower-level APIs, and perform initial testing on the driver, was write a "mirror" drive. The user-mode code pointed to a folder on disk, the driver made a virtual disk drive, and all reads and writes in the virtual disk drive went to the mirror folder.

On Windows, you can implement something like that using Dokany, Dokan, or Winfsp. On linux, there's the Fuse API. On Mac, there's MacFUSE.

Even if you don't do a "mirror" drive, understanding the callbacks that libraries like Dokany, Dokan, Winfsp, and Fuse do helps you understand how IO happens in the driver. Many IO methods provided in popular languages provide abstractions above what the OS does. (For example, the Windows kernel has no concept of the "Stream" that's in your C# program. The "Stream"'s Position property is purely a construct within the .Net framework.)

https://dokan-dev.github.io/

https://github.com/dokan-dev/dokany

https://osxfuse.github.io/

Another place to start is the OS's documentation itself. For example, you can start with Window's CreateFileA function. This typically is what gets called "under the hood" in most programming languages when you open or create a file: https://learn.microsoft.com/en-us/windows/win32/api/fileapi/...

You'll need this ressource installed in 1.X version to make it work : https://github.com/dokan-dev/dokany

Potentially no need to buy any hardware https://github.com/dokan-dev/dokany/wiki/Use-Mirror-example

Yeah, I had an issue and had to downgrade the Dokan Library. I downloaded from here.