Trying to backup Synology; "Bad File Descriptor" error.

[ghost]

Any ideas on how to fix this?
Using Samba to connect.

[ghost]

This happens with all network disks from my understanding and testing.
Is there a fix?
I think it's VSS related.

[SirHumphreyAppleby]

On Windows, Cyphertite runs under the Network Service account, so it cannot see any drives you've mapped. Map drives on startup via Group Policy so they are shared. UNC paths won't work.

[ghost]

How would I do that on Windows 7 Ultimate?

[SirHumphreyAppleby]

Create a batch file to map the drive (e.g. net use z: \ip\share)

Run "Edit Group Policy" (or similar, I'm on Windows 10) from Control Panel. Navigate to "Local Computer Policy | Windows Settings | Scripts", and double click "Startup". From there you can add the batch file you created. Reboot, and all going well, you should see the drive you mapped in Explorer.

[ghost]

You made my day. Thanks :)

[sdwhwk]

I'm actually having a similar issue, but with actual physical drives. Cyphertite backs up an assigned folder on c: drive perfectly. When I schedule it to backup my two other drives (complete drive backup under one schedule), It schedules D: and E: Drives during setup. When it runs, I get the "Bad File Descriptor" a couple of seconds in. I go to edit, it shows D:. D:. (yes, there is a dot after the ) instead of D:\ E:\

I select my D: drive only, same error. It schedule for E: drive only, and it works (it's a raided drive while D: is a physical with 1 partition). So somethings blocking D: and I have no clue.

Running windows 8.1.