Backup4All can't write to Cryptomator virtual drive

[steven127]

Just wondering anyone else has experienced a problem like this.

I'm using Backup4All v7.4 build 479 under Windows 10 Pro.
I have a OneDrive account and attempting to create client-side encrypted backups using Cryptomator.
https://cryptomator.org/

I have created an encrypted folder in OneDrive, which creates a virtual drive on my machine, called drive L:
I can see and access L: within Windows Explorer and it's even a pickable destination in Backup4All under the Local Drive destinations.
However, the backup always fails with the message

[11/14/2018 8:12:32 PM] Checking backup destination (Local hard drive)
Backup aborted. Reason:
Cannot create folder "L:\BkpSteven\CryptoBackup". The system cannot find the path specified

I can readily copy/drag files to it via Explorer, which I'm doing in the interim.

Suggestions are welcome and appreciated.
Thanks
Steven

[Adrian (Softland)]

Hi,

Do you run the backup manually or scheduled?
Do you have the same problem if you run Backup4all as administrator?

[steven127]

[quote="Support"]Hi,

Do you run the backup manually or scheduled?
Do you have the same problem if you run Backup4all as administrator?[/quote]

Hi, thanks for the questions.

I have tried running both manually and scheduled - they both fail with the same error.
[11/19/2018 8:35:12 AM] Checking backup destination (Local hard drive)
Backup aborted. Reason:
Cannot create folder "L:\BkpSteven\CryptoBackup". The system cannot find the path specified

I just tried running as administrator and got the same results.

When I open the Properties and look at the destination settings under Local Hard Drive field, I get this
L: <drive does not exist>

Yet it appears in Windows Explorer, This PC window and other file utilities and I can readily drag files to/from it.

-steven

[Adrian (Softland)]

Hi,

Is L: drive the correct one?
Can you give me access to your computer using TeamViewer?
Please send us an email to support[at]backup4all[dot]com

[steven127]

[quote="Support"]Hi,

Is L: drive the correct one?
Can you give me access to your computer using TeamViewer?
Please send us an email to support[at]backup4all[dot]com[/quote]

Hi, yes, L: is the correct drive letter - I specifically assigned it for consistency.
Sorry, while I appreciate this offer to help via TeamViewer, I can't share this computer.
But I would be willing to share screen shots, logs, screen-casts etc. if any of that could help.
-steve

[Adrian (Softland)]

Hi,

Do you have the same problem if you set the Cryptomator virtual drive outside the OneDrive folder?

[steven127]

[quote="Support"]Hi,

Do you have the same problem if you set the Cryptomator virtual drive outside the OneDrive folder?[/quote]


Great question. I immediately created a vault on a local drive and received the same error message but referencing this new drive letter of course.

[Adrian (Softland)]

Hi,

I installed Cryptomator here, but it seems to be very slow in accessing and handling files.
The problem seems to be it does not respond in a decent time to Backup4all's request.

[steven127]

[quote="Support"]Hi,

I installed Cryptomator here, but it seems to be very slow in accessing and handling files.
The problem seems to be it does not respond in a decent time to Backup4all's request.[/quote]

Thanks for doing this and testing it out yourself.
Ahh, so it's more of a timing-out issue - which would kind of explain how it sees the drive letter in the Properties setup/config process but fails in the execution.
Oh well. It's no deal breaker for me as I already use BFA regularly to back up my files locally (works extremely well).
it backed up to the cloud in direct/plain format very well too.
But Cryptomator appealed to me because it seemed like a good (and easy) solution for a client-side encryption for cloud-based backups
I will contemplate alternatives....and open to suggestions

Thanks and Happy (U.S.) Thanksgiving!
-steve