BUT as this ntifs - YOU MUST ensure the filesystems are shut down cleanly from Windows - otherwise ntfs3 driver will refuse to mount.
If you get write errors you must reboot into Windows and run chkdsk command for the file system
@soundofthunder created a very thorough topic on ntfs - worth a read.
If you have anything - scripts et.al. - that requires the device to have a fixed mountpoint my recommendation is to use a set of unit files.
This makes the device available when needed and unmount shortly after it is no longer needed.
As example we take your devices from fstab - comment the lines in fstab and save the file
#UUID=01D6D6DDA6146800 /mnt/Data ntfs3 defaults 0 0
#UUID=5E7E4E247E4DF575 /mnt/Fun ntfs3 defaults 0 0
Then reboot your system
When back up create 4 new files in /etc/systemd/system - file names reference the mount point
- /etc/systemd/system/mnt-Data.mount
[Unit] Description=Mount Data partition [Mount] What=/dev/disk/by-uuid/01D6D6DDA6146800 Where=/mnt/Data Type=ntfs3 Options=rw,noatime [Install] WantedBy=multi-user.target - /etc/systemd/system/mnt-Fun.mount
[Unit] Description=Mount Fun partition [Mount] What=/dev/disk/by-uuid/5E7E4E247E4DF575 Where=/mnt/Fun Type=ntfs3 Options=rw,noatime [Install] WantedBy=multi-user.target - /etc/systemd/system/mnt-Data.automount
[Unit] Description=Automount Data partition ConditionPathExists=/mnt/Data [Automount] Where=/mnt/Data TimeoutIdleSec=10 [Install] WantedBy=multi-user.target - /etc/systemd/system/mnt-Fun.automount
[Unit] Description=Automount Fun partition ConditionPathExists=/mnt/Fun [Automount] Where=/mnt/Fun TimeoutIdleSec=10 [Install] WantedBy=multi-user.target
Enable and start the .automount units
sudo systemctl enable --now mnt-Data.automount mnt-Fun.automount
Open your file manager an point to /mnt/Data - watch the magic…
What happens is - at the time of accessing the automount calls the mount thus making your data accessible.
The longer explanation