RSync Backups won't start

[Pinion_King]

Hi,

I am trying to setup an RSync backup from one ReadyNAS to another. I have configured all the settings, the test connection is positive.

When I click to start the backup, the status changes from Ready to Starting then a few seconds later back to Ready. Nothing gets backed up, nothing is entered in the logs.

Not sure what is going on. Have recreated the job, recreated the shares at both ends.

[de_niro]

no such issue on my 104 and 314,both OS6 are 6.1.4,I configured user and password protection on the destination share,everything goes well,can you please post configuration here?

[Pinion_King]

If I create the same backup on the backup box and set the source as the main box and destination as backup box it works.

[hexmode]

I'm having the same sort of issue with my system. Posted about it here: http://www.readynas.com/forum/viewtopic.php?f=4&t=73884

[_frantic_]

I too have this problem: rsyncs on my new RN104 will run only once.
Scheduled rsyncs do not work, when I try to start a rsync backup manually, nothing happens.

I have similar rsync backup jobs ( = same target) on my old ReadyNASduo - no problems there.
Therefore for me this looks like a problem on the RN104 itself.

I took a look in /var/log/frontview/backup. There are only old files from the first runs.
I have no idea, where to find more logs.

[hexmode]

I found that if backups have stopped, I can log in as root and restart them with:

# systemctl restart fvbackup-q

[_frantic_]

ah, interesting. I was not aware of the systemctl utility.

I tried:
root@ReadyNAS104:~# systemctl status fvbackup-q.service
...could not see any problems here.

Then:
root@ReadyNAS104:~# systemctl restart fvbackup-q.service
...and instantly my scheduled rsync backup started working.

Thanks for the tip!

Hopefully the ReadyNAS people will look into this.

[_frantic_]

Restarting fvback-q.service did work for the first backup job run only.
Any further backups got stuck again.

I took the following command from /etc/cron.d/frontview-backup and tried to run it in the foreground:
/frontview/bin/fvbackup 001
...nothing happens, it just hangs.

Using username "root".

Welcome to ReadyNASOS 6.1.4

root@ReadyNAS104:~# ps aux | grep fvbackup
root      1726  0.0  0.3  11944  1928 ?        S    00:05   0:00 /frontview/bin/fvbackup 001
root      5042  0.0  0.3  11944  1928 ?        S    04:05   0:00 /frontview/bin/fvbackup 001
root      8357  0.0  0.3  11944  1928 ?        S    08:05   0:00 /frontview/bin/fvbackup 001
root      9174  0.0  0.3  11944  1928 ?        S    09:05   0:00 /frontview/bin/fvbackup 002
root     12118  0.0  0.3  11944  1928 ?        S    12:05   0:00 /frontview/bin/fvbackup 001
root     12587  0.0  0.3  11944  1928 pts/2    S+   12:25   0:00 /frontview/bin/fvbackup 001
root     12703  0.0  0.1   4092   780 pts/3    S+   12:28   0:00 grep fvbackup
root     27046  0.0  0.3  20844  1636 ?        Ssl  Nov18   0:01 /frontview/bin/fvbackup-q
root@ReadyNAS104:~#

...so the scheduler works as expected, but fvbackup just hangs. I can not find any output / messages.

[Pinion_King]

Same for me, the service restart only works for the first backup.

[_frantic_]

I tried this:

systemctl stop fvbackup-q.service
killall fvbackup
/frontview/bin/fvbackup-q -d

-d = start by command line for debug
In this mode no more stagnations occurred.

I then stopped this (Ctrl+C) and restarted the service:

systemctl start fvbackup-q.service

...and voila! No more stagnations.

Well, I don't get it: there permanently was an error and now it's gone.


Since that, new difficulties occurred: on the rsync target, files no longer are being updated, deleted or created.
I never had such problems when my old ReadyNASduo was the source.

I will start over from the beginning: I have deleted the two backup jobs on the 104 and recreated one of them.
Let's see, what happens...

[Pinion_King]

I tried what _frantic_ did in their last post.

Seems to have done the trick for me, all the backups are copying, updating, deleting correctly.