# Backup mounted filesystems

**URL:** <https://kopia.discourse.group/t/backup-mounted-filesystems/1477>\
**Category:** General Topics\
**Created:** [October 12, 2022, 7:06pm UTC](https://kopia.discourse.group/t/backup-mounted-filesystems/1477 "2022-10-12T19:06:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Capon](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/chris_capon/32/501_2.png) [@Chris\_Capon](https://kopia.discourse.group/u/Chris_Capon)\
**Post date:** [October 12, 2022, 7:06pm UTC](https://kopia.discourse.group/t/backup-mounted-filesystems/1477/1 "2022-10-12T19:06:02Z")

</div>

We use Cryptomator to mount encrypted file systems in Windows 10 at this location.

C:\Users\Chris\Client

When adding a Policy in KopiaUI, the backup will not cross this boundary and back up files underneath (unless it is pointed at a sub-directory underneath).

| Policy Root folder | Kopia sees this |
| --- | --- |
| C:\Users\Chris | 0 files found |
| C:\Users\Chris\Client | 0 files found |
| C:\Users\Chris\Client\Documents | 192 files found |

Is there an option to handle this scenario? I think the filesystem appears as a Symbolic Link.

p.s. I tried the option for “Scan only one filesystem” Y/N but it has no impact.

Windows 10  
KopiaUI v0.12.1  
Cryptomator 1.6.4  
Dokan 1.5.1

---

<div class="post-metadata">

**Author:** ![stpr](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@stpr](https://kopia.discourse.group/u/stpr)\
**Post date:** [October 13, 2022, 7:27pm UTC](https://kopia.discourse.group/t/backup-mounted-filesystems/1477/2 "2022-10-13T19:27:42Z")

</div>

I am not what your question is: are you looking for a way to exclude some root directory except a particular subdirectory underneath? If so, it should be possible to do it via ignore rules.

As for “Scan one filesystem”, I am not exactly sure how Kopia interacts with Dokan, and whether it is properly being detected as a “different filesystem” (I am not sure if Windows reports Dokan mounts as being filesystems other than NTFS). It is perhaps worth filing a GitHub report to discuss whether this should be properly handled.

---

<div class="post-metadata">

**Author:** ![Chris\_Capon](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/chris_capon/32/501_2.png) [@Chris\_Capon](https://kopia.discourse.group/u/Chris_Capon)\
**Post date:** [October 13, 2022, 8:52pm UTC](https://kopia.discourse.group/t/backup-mounted-filesystems/1477/3 "2022-10-13T20:52:53Z")

</div>

No. This is not an Exclude type issue.

Literally, Kopia will not back up the root folder of a mounted volume, but it will happily back up any sub folder underneath.

So, in the example above, a new snapshot of C:\Users\Chris\Client (the mount point of the volume) will result in no files or folders being backed up.

But, a new snapshot of any sub-directory like C:\Users\Chris\Client\Documents (under the mount point) results in all its files and folders being backed up with no problems.

I think the fact that the root folder is implemented as a symbolic link is giving Kopia trouble. If Kopia will not back up the contents of a symbolic link, it would explain what is going on.

---

<div class="post-metadata">

**Author:** ![stpr](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@stpr](https://kopia.discourse.group/u/stpr)\
**Post date:** [October 14, 2022, 1:09am UTC](https://kopia.discourse.group/t/backup-mounted-filesystems/1477/4 "2022-10-14T01:09:25Z")

</div>

Ah I see, yes as far as I am aware, Kopia does not “follow symlinks”, which might be what is going on here.

---

<div class="post-metadata">

**Author:** ![Chris\_Capon](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/chris_capon/32/501_2.png) [@Chris\_Capon](https://kopia.discourse.group/u/Chris_Capon)\
**Post date:** [October 14, 2022, 5:26pm UTC](https://kopia.discourse.group/t/backup-mounted-filesystems/1477/5 "2022-10-14T17:26:52Z")

</div>

Thank you. I will file a feature request. Cheers.