Transfer files between two NWSP2 in the same LAN [SOLVED!]

[Jocko]

Ok Bozo29,

You must only create the share "fvdw" (no upper case) using the "file share management menu" from the web-interface where you try to execute a backup.

(Note : this share will be usefull for later (eg. firmware update)

[bozo29]

Only this? That is, create a folder and everything works?
It seems that right?
You are magic!

:punk :punk :punk IT WORKS , IT WORKS ! :punk :punk :punk

Thank you! :applause :applause :applause

In fact, I never doubted for a moment that it will. What I mean is that I was sure 100% that should work. :P

This firmware is great.

You may have a status of the operation? That should indicate somewhere the copy speed and time that's left to finish.
Do you have something like that on the todo list?
It's just a question. Whatever the answer, I am very pleased with how it works your firmware.

Thank you for your effort

[Jocko]

Glad to hear that your problem is solved :-D

But Now I have a bug to fix :crazy ( and after first tests, it seems hard to resolve...).

About your other questions :
Add a progress bar is not simple because there are difficulties to get the output of rsync whereas rsync is in background. :thinking

[bozo29]

Sorry to hear that. :(
If I can do something to help please tell me. :dontknow
Some tests? :dontknow
I have to do it with pleasure. Even if something can hurt my NAS's configuration, do not mind.
Even if I have to reinstall fvdw-sl does not bother me.
As long as data is not lost on sda8, everything is ok for me.

Thank you again and please tell me if I could do something.

[Jocko]

I found the cause ...

My Php code uses a function that does not know ... :shocked

I forgot to declare it. :corner
This function is used only when the share fvdw does not exist to create a folder where the rsync logs are saved.

Therefore creating the share,have resolved your problem.

[bozo29]

Glad to hear that.

I looked in the folder "fvdw" after copying is complete and I saw that there was created a ".log" file with operations that were performed.
So, in the next version of fvdw-sl, it will need to be created a folder "fvdw" as is created folder "public" on sda8, or you solve this problem in another way?

Good luck

[Jocko]

In fact, there is nothing to do. :scratch

Backup command already tests if the share "fvdw" exists. Look at the help (in the chapter F. Additional information ):

file.log:

/share/1000/fvdw/basename(source).log, if fvdw exist and backup not planned; /share/1000/cronjobs/basename(source).log, if backup will be planned

/tmp/var/log/rsync/basename(source).log, if fvdw doesn't exist

The issue was that the script failed to create the folder "rsync"...

[bozo29]

So, it's okay for me at least.

Folder "fvdw" will be created from the beginning, when installed firmware.
Do not forget to put that in "howto-guide", for not to ask someone else "Why the backup function not work?" :-D

[Jocko]

I will discuss with fvdw about your suggestion. (but Think that after fixing the bug in the next release, the backup command doesn't anymore fail.)