# Backup Runtime after 2.0.7.1 update

**URL:** https://forum.duplicati.com/t/backup-runtime-after-2-0-7-1-update/16378
**Category:** Support
**Created:** [June 13, 2023, 12:54am UTC](https://forum.duplicati.com/t/backup-runtime-after-2-0-7-1-update/16378 "2023-06-13T00:54:02Z")
**Posts on this page:** 1
**Showing post:** 90

<div class="post-metadata">

### Author: ![tkohhh](https://forum.duplicati.com/user_avatar/forum.duplicati.com/tkohhh/32/4015_2.png) [@tkohhh](https://forum.duplicati.com/u/tkohhh)
#### Post date: [June 25, 2023, 2:04am UTC](https://forum.duplicati.com/t/backup-runtime-after-2-0-7-1-update/16378/90 "2023-06-25T02:04:55Z")

</div>

So I finally read the release notes for Unraid 6.12 as I was preparing to update my server today. Turns out they DID address the FUSE issue. Or rather, they gave us a built-in way to bypass FUSE in the correct circumstances. For the curious, read the “Share Storage Conceptual Change” section of the [6.12.0 release notes](https://unraid.net/blog/6-12-0-stable).

Honestly, that’s good enough for me to consider this issue resolved.

After upgrading Unraid, I did set up my appdata share to be an “Exclusive Share,” which is the signifier in Unraid to bypass FUSE. I updated my Duplicati config to undo the previous workaround to bypass FUSE manually. I will report back if I experience slowness again, but I expect it will work well.

---

_[View the full topic](https://forum.duplicati.com/t/backup-runtime-after-2-0-7-1-update/16378)._