TestConnection OK, backup fails:Unable to access remote path

[kc1]

I'm using FrontView to copy to NAS2 from NAS1 as a Remote NFS Server backup

One of the NAS1 paths is "backup\Air\Memeo\from 7 Nov 11\C_"

So using escape character in the backup source path field like this: "backup/Air/Memeo/from\ 7\ Nov\ 11/C_" , the Test Connection succeeds

So I'm wondering why the backup fails with: "Unable to access remote path"?

If I substitutes the spaces with something else, the backup succeeds but it's not a good option because the source is itself a series of backups of windows PCs, users of which have little sympathy for unix path recognition issues

[Amidala]

As your said,when I use the path :" backup/Air/Memeo/from\ 7\ Nov\ 11/C_" ,the Test Connection failed.
So this backup job could not run.

[Amidala]

I test this path :"picture/Air/Memeo/from7Nov11/C_" (no spaces ),the Test Connection succeeds.
And this backup job run normally.

--------------------------------------------------------------------------------
FULL Backup started. Mon May 28 00:27:03 PDT 2012

Job: 004
Protocol: rsync
Source: 10.40.1.82::picture/Air/Memeo/from7Nov11/C_
Destination: [backup]/


receiving incremental file list
./

sent 32 bytes received 60 bytes 61.33 bytes/sec


Backup finished. Mon May 28 00:27:04 PDT 2012

[kc1]

I test this path :"picture/Air/Memeo/from7Nov11/C_" (no spaces ),the Test Connection succeeds.
And this backup job run normally.

I know paths without spaces run normally. That's not the problem. the problem is you are supposed to be able to use the escape character to resolve paths that do have spaces, which works for the test but not for the backup.