NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Backup BROKEN after failed rsync
RN102 running 6.1.6
I had an rsync backup setup to pull from a remote server over SSH. This backup was taking forever (~24 hours) and didn't seem to be making much progress at all, maybe 100mb per hour even though rsyncing to any other machine on the network goes extremely quickly (is rsync always slow/unusable on RN102?). After about 24 hours of this slow rsync chugging away, the status went from 'In Progress' to 'Ready'. I have no idea what this means, because it did not complete the rsync (or if it did, it didn't end the backup properly). I can't start any other backups, they all remain 'In Queue' because it thinks this rsync is still going even though it was stuck at 'Ready'. I tried removing the rsync backup from the backup list, restarting the NAS a few times and nothing works. I only have one backup job now, a simple copy from a desktop machine to the NAS but it is stuck 'In Queue' because of this broken rsync. Any ideas? Thanks
I had an rsync backup setup to pull from a remote server over SSH. This backup was taking forever (~24 hours) and didn't seem to be making much progress at all, maybe 100mb per hour even though rsyncing to any other machine on the network goes extremely quickly (is rsync always slow/unusable on RN102?). After about 24 hours of this slow rsync chugging away, the status went from 'In Progress' to 'Ready'. I have no idea what this means, because it did not complete the rsync (or if it did, it didn't end the backup properly). I can't start any other backups, they all remain 'In Queue' because it thinks this rsync is still going even though it was stuck at 'Ready'. I tried removing the rsync backup from the backup list, restarting the NAS a few times and nothing works. I only have one backup job now, a simple copy from a desktop machine to the NAS but it is stuck 'In Queue' because of this broken rsync. Any ideas? Thanks
15 Replies
Replies have been turned off for this discussion
StephenB wrote: If it is a new backup job, then it will do a full backup. There might be a way to trick it with ssh, but I don't know how it detects it is the first run,
If it is successfully copying files, I would probably leave it for a few days. You can see if it is running if you enable ssh and run top.
How big is the share?
It is about 300gb (1.5million files). There really should be a way to disable full backups entirely, that sort of thing pretty much defeats the purpose of using something incremental like rsync. I think I'm just going to have to do manual rsync commands over SSH to a non-share directory, doing any rsync stuff through the frontend panel seems unbearably slow/unreliable with no stats/output.Riboflavin wrote: There really should be a way to disable full backups entirely, that sort of thing pretty much defeats the purpose of using something incremental like rsync.
On the old OS4 devices, you can create a backup job that backs up just a tiny portion of your data; running that satisfies the "first backup is always a full backup" rule, and then you can adjust all the backup parameters the way you really want them, and subsequent backups are then incremental. Maybe it works the same way on OS6.fastfwd wrote: Riboflavin wrote: There really should be a way to disable full backups entirely, that sort of thing pretty much defeats the purpose of using something incremental like rsync.
On the old OS4 devices, you can create a backup job that backs up just a tiny portion of your data; running that satisfies the "first backup is always a full backup" rule, and then you can adjust all the backup parameters the way you really want them, and subsequent backups are then incremental. Maybe it works the same way on OS6.
I'm going to give that a shot next. Unfortunately my NAS is running really slowly right now, not really sure what is going on.
Does anyone else have experience with large rsync commands (1M+ files) on these less powerful devices (RN102)? Is it normal for the incremental file list to take hours and hours to build?- The other way is to set up the backup job so that it will fail, usually by creating a destination like a USB port that does not have a disk in it. Run the backup, let it fail, then change the settings to the correct ones.
This does work on OS7. - I found another post that suggested moving the files from /var/log/frontview/backup to a different folder (or delete them if you are an adventurous risktaker). Moving the files worked for me (then I deleted them).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
