When performing a Cloud File backup for data on Google Drive, the following error message is displayed on the backup client interface, or in the backup report:
Note: This issue will only affect files and folders on Google Drive with name containing underscore ( _ ) (also called underline) character.
|*||info||...||Start [ Windows platforms (computer), AhsayOBM pre-220.127.116.11 ]|
|*||info||...||Finished running pre-commands|
[New File] File="backup_source/path_with_slash_character" Error="com.ahsay.
afc.bfs.cloud.o: [CloudFileSystem.createFile] Parent directory 'backup_source
/path_with_slash_character' does not existrn at com.ahsay.afc.bfs.cloud.y.a
(Unknown Source)rn at com.ahsay.afc.bfs.cloud.v.a(Unknown Source)rn at com.
ahsay.cloudbacko.pc.a(Unknown Source)rn at com.ahsay.cloudbacko.pc.a(Unknown
Source)rn at com.ahsay.afc.bfs.cloud.v.a(Unknown Source)rn at com.ahsay.obx.
core.backup.file.d.a(Unknown Source)rn at com.ahsay.obx.core.backup.file.L.
run(Unknown Source)rn at com.ahsay.afc.util.h$1.run(Unknown Source)rn at
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)rn at java.
util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)rn at java.
This is a known issue with AhsayCBS / AhsayOBM version pre-18.104.22.168.
For files and folders on Google Drive with name containing any underscore ( _ ) (also called underline) character, for example:
The underscore ( _ ) characters are returned as slash ( / ) characters (which are incorrectly interpret as path separator):
cloud, file, google, drive, underscore, _, underline, cbs, obm