Backup not complete again

Did you analyze what was missing?

How have you ruled out the possibility that the problem is with the Javelin?

StephenB wrote:
Did you analyze what was missing?

Not extensively. The RN104 copied ~850 files, a mix of DVD iso files and the small data files, out of the 1800+ that were in the source folder. And it would not resume backup until I changed the source folder. I hope that by removing the small data files (which are easy to move around) the iso files will all get copied.
I have checksums turned on from yesterday morning. And today I turned on NFSv4, it was turned off by default.

StephenB wrote:
How have you ruled out the possibility that the problem is with the Javelin?

In the past I have moved about 3TBs from the PC to and from the Javelin without issue. So I rate that at a low possibility. The backup job is running again and has copied another 1TB since this morning, so it looks ok.
I spent the morning looking for NFS info and it appears the 8 thread count started when NFS came out. In general you need more threads with more users. So whether the issue is NFS thread count or not, I am getting the files copied.

Moving forward, what is needed to trigger the RN104 to do an incremental backup? Is changing 1 file enough?

Well the backup will run on schedule even if no files change. Any new file, or file with a new size or date should be copied.

I'd edit the backup job and change from NFS to rsync once you get the initial files copied.

I ran into a similar problem. Netgear support told me that NFS isn't reliable if you have a large number of files in a folder and are using different file systems between the devices. They said that rsync or windows/nas (cifs) would work better in this situation.

What I ended up doing was letting the NFS backup job complete, and running a folder compare utility and manually copy over the missing files. Then you should be able to setup an rsync job that will keep things updated.

StephenB wrote:
Well the backup will run on schedule even if no files change. Any new file, or file with a new size or date should be copied. I'd edit the backup job and change from NFS to rsync once you get the initial files copied.

The backup of the iso files completed in good order.
I copied the ~1200 small files back and started the frontend backup job again. It ran for a bit and completed. I checked the directory listings against each other and not all of the files copied over.
There are 606 *.metathumb files and 388 copied over.
There are 607 *.xml files and 431 copied over.
I switched the backup job to remote: Rsync Server. It ran quickly and did not change any results. I moved the metathumb out, ran the backup again, results did not change.
One of the files that did not copy was XX_2013.metathumb. So I copied and pasted it back with Win7 to add a file XX - Copy.metathumb to the source folder. The remote: Rsync Server backup job did not pickup the change and did not copy the new file. That is in addition to the other files it will not copy (see above). I added another file XXX_2008 - Copy.metathumb, the original file did copy to the backup folder. The new XXX_2008 - Copy.metathumb file was not copied
The remote: Rsync Server backup job has some blind spots. I deleted the *.metathumb and *.xml files from the RN104 and ran the remote: Rsync Server backup job again. It did not notice the files were missing from the backup folder.

update time.
When I switched the backup job to rsync, it removed the path. So when I tested the connection, it was good, but didn't move any files.

I can get the nfs to connect to my video source folder, but when I switch to rsync server (and restore the path) I get a cryptic:
Unable to connect to host.
Code:7077010011
I am using the same user name and password that was good with nfs. Please advise where I am going wrong.

Trying to connect with Windows/NAS I get the same as above with a 707010020 error.

update time again.
I finally was successful getting the remote: Window/NAS backup to connect. AND it did a complete backup without missing any files.
Originally I was following the instructions from: http://kb.netgear.com/app/answers/detail/a_id/23424/~/how-do-i-configure-the-remote-source-or-destination-for-a-job-on-my-readynas-os, that says:

8. In the Path field, enter the folder path. If you select a Windows protocol, use a forward slash (/) to separate directories, for example: /<share name>/<folder name>

Which does not work...

I searched and found this: http://www.readynas.com/forum/viewtopic.php?f=31&t=42226, which says:

agree documentation is very poor given it is a key feature, end result user is left to trial and error. I got this working for my PCs including 64bit windows 7: host can be ip address or computer name path should start without / username / password should be a user on the PC in question with admin privilige. I didn't need to fiddle with the homegroup settings either as indicated elsewhere. example: host = 192.168.11.4 path = Users/PC/Documents/Paul/CV user = johnsmith password = example

Which worked!!!

I found your source path suggestion solved my inability to get the backup to execute. I was following the Netgear documentation (useless) and the youtube video by Mammoth Jerk titled "How to set a Backup with a Netgear ReadyNAS step by step guide". For the path source, he uses only the source folder share name but I would get "Access denied: invalid username or password. Code 7077010013" when I tested the connection. I don't use a administrator password on my computer so I thought that might be the problem although Mammoth Jerk indicated it wouldn't be a problem as long as the Network Access and Sharing password settings were correct. Since some users indicated that the backup would execute even though the "test connection" failed, I attempted to run the backup job but it failed saying "source cannot be mounted on the system". Changing the source path using your suggestion resulted in a successful test connection (the entire Windows path without the leading / as you suggested) and the backup job would successfully complete. I have one last problem however - nothing was backed up to the destination share folder. The backup job completes in less than two seconds. Since I've already spent 3 days attempting to get this to work, I guess I still need to attempt all permutations and combinations (read as trial and error). But a BIG thanks for getting me one further step down this painful path. Ken Goodwin, Houston.

I may have a problem with your source folder path statement. Using an extensive path name for the source folder like Users/Myname/SourceFolder does get the Test Connection to pass but after a few days I find that I can get the same result without even having to specify a SourceFolder. When I run my backup job with an extensive path, the backup successfully executes but produces no output. It works exactly the same if I specify a non-existent SourceFolder; in fact, exactly the same without any SourceFolder being delineated at all! In the YouTube video by Mammouth Jerk, "How to set a Backup with a Netgear ReadyNAS step by step" he uses only the Share Folder name in the path statement, e.g., SourceFolder. When I attempt this, the Test Connection results in a Username or Password fail and the Backup job can't mount the source folder when executed. The ReadyNAS OS 6.2 manual states one should use the Browse/pull-down menu to select the source folder but for the OS 6.2.2 remote source settings, the pull-down menu is greyed out so the only way I can specify a source is to type it in. The pull-down menu for the local destination shares folder works as advertised. So I have been unable to get a Backup job to correctly execute (no output in the Destination folder) although I have no trouble using the ReadyCLOUD app interface to create a successful backup job. The only problem with the ReadyCLOUD app interface is that one can't specify a source folder below Users/Myname directory level (the My Documents / DOCUMENTS directory level). Currently I am refusing to completely reorganize my computer's file organizational structure having been at it since the days of DOS and having gotten use to it!!

Using the example above (/Users/PC/Documents/Paul/CV) - maybe try sharing the CV folder (full access to everyone) on the PC, and then simply use /CV as the path.

What is the actual path you are trying to back up?