312 6.0.6 - Issue 'Error backup job "ZZZ". source cannot

hello all

First of all, I have to say that I am very disappointed with the interface to post a new topic in this forum. After 30 minutes writing the post, it just blew away for I do not know what reason about the login and bla bla bla. It is ok than you ask for the password again if I was spending too much time writing the post. I understand. But could you please just SAVE IT AS A DRAFT meanwhile so when I am actually login in again I will not have to write it back from scratch? Thank you.

Second, I know I am not wise about linux and Mac. It is ok. But I do know how to use a web application, what FrontView actually is. And I cannot understand why I just can't create a backup job to just backup some folders from my Mac 10.8 into the NAS (312 6.0.6) and do not understand what are the next steps I shall be doing to fix the issue. I just want to set some backup jobs using the Mac as the source and the NAS as the destination, using FrontView. Mac as source, NAS as destination, backup job running on the NAS. However, something that shall be easy to accomplish using FrontView, i just cannot understand where the mistake I am undoubtedly making is, as FrontView is returning cryptic error messages and misleading information to me.

I will try to describe (again) the issue I am experiencing:

I've shared some folders in my Mac, and I gave permission to an specific user to access them in read-only mode. I've verified that the folders are correctly shared connecting to them from a laptop running W7. I am able to access them and browse the content.

I've set a direct connection between the mac and the NAS via Ethernet. I've verified their connectivity running a ping from both ends. OK.

I am using FrontView to set a backup job to backup the folder "Music" in my mac to a share named "Music" in my NAS. It shall be easy, right?

SCENARIO 1: SOURCE remote: Windows/NAS (Timestamp). HOST IP: 192.168.192.3 (mac). Path: (empty). User/password: xxx/yyy. Test connection: "Error connection to folder: 7077010020". OK, clearly I've done something wrong. So:

SCENARIO 2: SOURCE remote: Windows/NAS (Timestamp). HOST IP: 192.168.192.3 (mac). Path: Music (First uppercase). User/password: xxx/yyy. Test connection: "Succesfully connected to //192.168.192.3/Music". OK, clearly I've fixed it. Let's run the backup job:

******
Backup Job Name: MUSIC
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [remote:cifs]///192.168.192.3/Music
Backup Destination: [Music]/
Backup Start Time: Wed May 22 2013 22:13:46
Backup Finish Time: Wed May 22 2013 22:13:47
Backup Status: Fail: source cannot be mounted on the system.
*******

Ok, I do not know the reason why something that I was able to connect to, it cannot be mounted on the system. Ok, let's try something different:

SCENARIO 3: SOURCE remote: Windows/NAS (Timestamp). HOST IP: 192.168.192.3 (mac). Path: music (lowercase). User/password: xxx/yyy. Test connection: "Succesfully connected to //192.168.192.3/music". Olé! The "Test connection" feature does not care about upper/lowercase. Me neither. So let's try to run the backup job:

*********
Backup Job Name: MUSIC
Backup Job Type: Full
Protocol: cifs
Backup Source: [remote:cifs]///192.168.192.3/music
Backup Destination: [Music]/
Backup Start Time: Wed May 22 2013 22:17:37
Backup Finish Time: Wed May 22 2013 22:17:37
Backup Status: Fail: source cannot be mounted on the system.
*********

OK, I am in an dead-end from an end-user perspective, since I cannot play with the upper/lowercase with the IP number x)

Let's try then changing the backup type:

SCENARIO 3: SOURCE remote: Windows/NAS (Archive Bit). HOST IP: 192.168.192.3 (mac). Path: Music. User/password: xxx/yyy. Test connection: "Succesfully connected to //192.168.192.3/Music". OK:

********************
Backup Job Name: MUSIC
Backup Job Type: Full
Protocol: cifs-ab
Backup Source: [remote:cifs-ab]///192.168.192.3/Music
Backup Destination: [Music]/
Backup Start Time: Wed May 22 2013 22:22:58
Backup Finish Time: Wed May 22 2013 22:22:58
Backup Status: Fail: failure during copy.


Copied 0 files and directories
----------------------------------------

And now it says "IN PROGRESS" in the front view. Here we go!. But it finished really soon, so I doubt anything was copied. I re-run it and got:

Backup Job Name: MUSIC
Backup Job Type: Full
Protocol: cifs-ab
Backup Source: [remote:cifs-ab]///192.168.192.3/Music
Backup Destination: [Music]/
Backup Start Time: Wed May 22 2013 22:27:48
Backup Finish Time: Wed May 22 2013 22:27:49
Backup Status: Fail: failure during copy.


Copied 0 files and directories
----------------------------------------


So now it fails during the copy, OK, shall I understand that this is related to the "Destination" permissions? But If I am running the FrontView as an administrator, what permissions? OK, I'll check it later. Let's see what happens if I switch it to "lowercase":

SCENARIO 4: SOURCE remote: Windows/NAS (Archive Bit). HOST IP: 192.168.192.3 (mac). Path: music (lowercase). User/password: xxx/yyy. Test connection: "Succesfully connected to //192.168.192.3/music". OK, running the job again:

Backup Job Name: MUSIC
Backup Job Type: Incremental
Protocol: cifs-ab
Backup Source: [remote:cifs-ab]///192.168.192.3/music
Backup Destination: [Music]/
Backup Start Time: Wed May 22 2013 22:29:19
Backup Finish Time: Wed May 22 2013 22:29:19
Backup Status: Fail: failure during copy.


Copied 0 files and directories
----------------------------------------

I went to the share and modified the NFS and AFP permissions, EVERYONE READ/WRITE, and re-run the job:


Backup Job Name: MUSIC
Backup Job Type: Full
Protocol: cifs-ab
Backup Source: [remote:cifs-ab]///192.168.192.3/music
Backup Destination: [Music]/
Backup Start Time: Wed May 22 2013 22:33:10
Backup Finish Time: Wed May 22 2013 22:33:10
Backup Status: Fail: failure during copy.


Copied 0 files and directories
----------------------------------------

So, it does not seem to be something related to the "destination" share's permissions. I give up with Windows. Let's try with NFS, then.

SCENARIO 5: SOURCE remote: nfs. HOST IP: 192.168.192.3 (mac). Path: music (lowercase). User/password: xxx/yyy

I read somewhere that non-root users could not access NFS shares in Mac OS 10.8. So I modified the plist "/System/Library/LaunchDaemons/com.apple.nfsd.plist" including:

<array>
<string>/sbin/nfsd</string>
<string>-N</string>
</array>


And I created the file "etc/exports" with:

Users/myuser/Music -ro -mapall=nobody -alldirs

I modified the source in the backup job to be "remote:nfs" and left everything the same way. When testing the connection, it says: "unable to connect to host: 7077001011", so here finished my adventure :(



I know I could be funny. And now that I've read again the post, it is fun, somehow. But behind my smile, I am really angry for not being able to achieve a simple task like creating a backup job using the FrontView interface. And with a lot of quite important data needed to be backed up.

Please, could anyone help me? I will really appreciate it.

Thank you so much in advance.

Ps.- Yes, I copied the whole post in a textpad before I resubmitted it again. Just in case :)