Page 1 of 1

[Help] Unable to Backup /homes

Posted: 05 Dec 2025, 21:49
by VioletSquirrel
Hello

I wondered if someone could help with the following issue. I am not able to backup the /homes directory with Duple backup, I get an errors saying the directory does not exist.

NAS: F4-425 Plus
TOS: 6.0.794
Duple: 2.1.048
Mode: Hybrid

When setting up the backup, I select the homes share.
Image

After confirming this is displayed as home, not homes.
Image

The backup then fails with the error:

Code: Select all

stat /Volume1/home: no such file or directory
User home directories are enabled. I can backup any other shared folder as expected.

Anyone have any ideas?

Re: [Help] Unable to Backup /homes

Posted: 09 Jan 2026, 23:23
by qidi4feet
I have same issue, it replaces the /homes with /home notice the missing S in the end
its pretty annoying , and i cant understand why it is happening and they should fix it right away

Re: [Help] Unable to Backup /homes

Posted: 10 Jan 2026, 01:45
by VioletSquirrel
I raised a support ticked for this. They said this is a known issue and it is fixed in the next Duple release. They were not able to provide a release date.

Does anyone know the Duple backup version that is on mixed with TOS 7?

Re: [Help] Unable to Backup /homes

Posted: 10 Jan 2026, 03:02
by qidi4feet
I just installed the TOS 7 , and its the same with duple , and the home folder , so nothing new there

Re: [Help] Unable to Backup /homes

Posted: 10 Jan 2026, 03:49
by VioletSquirrel
Shame, guess we will have to wait for the next release and see. Surprise this has not come up before. Makes me wonder how many people are actually using Duple in the first place as this seems like a prime backup candidate.

Re: [Help] Unable to Backup /homes

Posted: 10 Jan 2026, 14:27
by qidi4feet
yeah its pretty streight forward , but mayby people just dont backup home folder ?? but that else do they use then when backup to another nas

Re: [Help] Unable to Backup /homes

Posted: 10 Jan 2026, 20:44
by TMbuddy
qidi4feet wrote: 10 Jan 2026, 14:27
The issue you reported is a known defect. We are currently working on a fix internally and will release a new version to resolve the problem as soon as possible. Please wait patiently. Thank you for your understanding!