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
- Can you delete the last remaining backup, create another new backup task and try to run it?
If this fails, I would try an OS reinstall (using boot menu) vandermerwe wrote: Can you delete the last remaining backup, create another new backup task and try to run it?
If this fails, I would try an OS reinstall (using boot menu)
Thank you that seems to have fixed it!
edit 1: scratch that, after a few minutes it went from 'In Progress' to 'In Queue' even though it is the only backup job.
edit 2: okay, oddly enough the job finished while it was in the 'In Queue' phase, sent me an email with a log, and went back to 'complete' so it all seems good now.
------
Any idea why my rsync would be so horribly slow/never finish (on the nas only)? I tried doing a manual rsync through ssh as well and it was just as slow if not worse, it seemed to lock up when opened a directory with only a few hundred files in it.- I'm afraid I know little about rsync over ssh.
Rsync is quite processor intensive but 100mb per hour is very poor.
Are you saying you can do rsync pull from this same server to another remote device more quickly? vandermerwe wrote: I'm afraid I know little about rsync over ssh.
Rsync is quite processor intensive but 100mb per hour is very poor.
Are you saying you can do rsync pull from this same server to another remote device more quickly?
Yeah, I can do the same rsync to my desktop computer (same network as the nas) in a few minutes rather than hours and hours. The bulk of the data is already on the nas so it is just incremental downloads, it should go rather quickly. That said, there are about 1.5 million small files that it is syncing, maybe the processor just can't handle it?- Are you certain the rsync setup on the 102 is correct, ie it's not doing a full backup?
- It will do a full backup the first time, even if the files are already there.
- Riboflavin, when you say "the data is already on the NAS", did you actually get it there using the same backup task you are using now. StephenB is correct, newly created backup jobs will always do a full backup first time, then subsequently as you have set it up.
This is the reason you should try to do the first backup using nfs on the same lan, change the same task to use rsync, then resite the remote NAS. As the task will already have done a full backup, the next backup will be incremental. vandermerwe wrote: Riboflavin, when you say "the data is already on the NAS", did you actually get it there using the same backup task you are using now. StephenB is correct, newly created backup jobs will always do a full backup first time, then subsequently as you have set it up.
This is the reason you should try to do the first backup using nfs on the same lan, change the same task to use rsync, then resite the remote NAS. As the task will already have done a full backup, the next backup will be incremental.
I used an NFS transfer to get it there, but it was a different backup job because I had to delete it to fix my other problem. It isn't coming from another NAS by the way, it is coming from a web server running CentOS. Should I just let it run for a few days and see what happens? It seems weird it would take so long.- I would cancel it.
The backup job log will then indicate whether it was a full backup.
Has this new backup job ever completed. If not then it is still trying to do a full backup.
You'll need to do what I suggested,edt: unless you want to wait and the total amount to be backed up means it would complete in less time that it would take you to get the remote nas on site and start again. - 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?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
