NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Pull backup using Rsync over SSH. Log says Success but one home dir is empty!
NAS scenario
- New 626x got the disks from my old Pro 6 into it (same bays)
- Pro6 got two disks (new) and imported configuration from my previous backup-nas o(NR102 I think)
- Pro 6 runs the backup jobs on schedule in pull-mode
- 626X syncs to Azure cloud for backup
I was verifying my backups when I realized that my home dir (one of the 4) is empty in the backed-up location. Strangely, log simply says "Success". Files under /var/log/frontview/backup do not show any more information either. File-copy logs are truncated and do not list any of the files under /home/vamsi. All I get is the one entry for /home/vamsi/ with no information after it.
To simplify the logs, I did an initial backup (full backup), removed the empty `vamsi` directory under the backed up home and ran the backup again. I see this in the logs
Backup Job Name: home folders backup over rsync-over-ssh Backup Job Type: Incremental Protocol: rsync+ssh Backup Source: [remote:rsync+ssh]/vamsi-nas://home Backup Destination: [Backup]/HomeBackups Backup Start Time: Sun Nov 01 2020 10:05:31 AM Backup Finish Time: Sun Nov 01 2020 10:05:48 AM Backup Status: Success home/vamsi/ sent 12,945 bytes received 1,817,294 bytes 104,585.09 bytes/sec total size is 41,784,135,940 speedup is 22,829.88 ----------------------------------------
When I look under /var/log/frontview/backup
- backup_009_copy.1604253931.log shows the last three lines of the text in the log pasted above.
- backup_009_error.log is empty
backup_009.log shows
root@vamsi-nas-bkup:/var/log/frontview/backup# cat backup_009.log name: home folders backup over rsync-over-ssh full: no proto: rsync+ssh src: [remote:rsync+ssh]/vamsi-nas://home dst: [share:Backup]/HomeBackups start: 1604253931 finish: 1604253948 status: 0 log:
Does this give you any idea of where the problem might be ?
When I push from the 626X to the backup-nas however, all the home dirs come through. So atleast I have a full copy on the backup-nas. I however, want to move away from the per-share backup I am currently using (a new share was missed and I want to switch to a more fool proof scheme) and switch to rsync-over-ssh for the entire /data tree. Seeing how it is failing silently is scaring me and I want to try and figure out what is going on. Not being able to trust Nas backups is terrible.
One problem I have noticed with the 626X which might be relevant: when I ssh into the NAS, the SSH terminal frequently freezes! I type and nothing happens, a few seconds later, it starts working. Since rsync over ssh obviously uses ssh, I am wondering if there is an issue here. The Pro 6's SSH experience is flawless.
I'd appreciate any help from the gurus and jedis here!
readyjoove wrote:
Is there is a standard way to have the source-nas support rsync server for home folders ?
Not that I know of. It's not an issue for me, as I have the home folders turned off (no sharing protocols enabled at all). You might consider that. You can of course set up a public share with limited access. It just wouldn't have the same name as the user account.
If you plan to use ReadyCloud, the home folders have another disadvantage - you'd have two ReadyNAS accounts (one local, and one ReadyCloud), which pretty much makes the home folders worthless.
readyjoove wrote:Looks like push-based backups should work just as well but I was never clear on how to manage backup-nas power scheduling. Pushing to the backup-nas's rsync-server will not delay backup-nas shutdown right ?
...
Looks like push backup uses snapshots and maintains integrity better so definitely worth researching further.
Yes, that is the tradeoff. Push backups back up a snapshot, which gives you a coherent backup. But the receiving NAS can shutdown in the middle if it is on a power schedule. My own approach is share-by-share pull backup, with the backups running off hours.
But it would be nice if there was a way to use a power schedule with push-backup jobs.
9 Replies
Replies have been turned off for this discussion
I am a little confused on how share-by-share backup vs full NAS backup relates to this. But if you want to back up the full data volume in one backup job, then you will need to switch to push-backups from the 626x anyway, and that apparently is working.
What user account are you using for rsync-over-ssh? If you think ssh is a factor, you could try just using rsync and see if that behaves differently. IMO, if both NAS are on the same home network, there isn't much need to use rsync-over-ssh.
Thanks for responding Stephen! Much appreciated.
The goal is to perform full-nas backup. I wanted to replicate the share structure so I created the same shares on the backup nas and then the backup-nas would do a rsync pull for each share. The left over bits were the home-dirs which do not expose rsync (not over the GUI atleast). To back those up via pull, I am using rsync-over-ssh.
Is there is a standard way to have the source-nas support rsync server for home folders ? The rsyncd.conf only lists the shares and the GUI has no rsync options for home folders. Did I miss a config setting ?
rsync-over-ssh uses root as the user with the public-key from backup-nas imported into the source-nas.
readyjoove wrote:
Is there is a standard way to have the source-nas support rsync server for home folders ?
Not that I know of. It's not an issue for me, as I have the home folders turned off (no sharing protocols enabled at all). You might consider that. You can of course set up a public share with limited access. It just wouldn't have the same name as the user account.
If you plan to use ReadyCloud, the home folders have another disadvantage - you'd have two ReadyNAS accounts (one local, and one ReadyCloud), which pretty much makes the home folders worthless.
readyjoove wrote:Looks like push-based backups should work just as well but I was never clear on how to manage backup-nas power scheduling. Pushing to the backup-nas's rsync-server will not delay backup-nas shutdown right ?
...
Looks like push backup uses snapshots and maintains integrity better so definitely worth researching further.
Yes, that is the tradeoff. Push backups back up a snapshot, which gives you a coherent backup. But the receiving NAS can shutdown in the middle if it is on a power schedule. My own approach is share-by-share pull backup, with the backups running off hours.
But it would be nice if there was a way to use a power schedule with push-backup jobs.
I had used pull-based backups as that seemed to be a great way to handle schedules
- Backup-nas power scheduled to wake up on sunday
- Runs all the pull backup jobs (stays up as long as the backup jobs run or the whole day)
- Shuts down.
Looks like push-based backups should work just as well but I was never clear on how to manage backup-nas power scheduling. Pushing to the backup-nas's rsync-server will not delay backup-nas shutdown right ? I am moving the backup to a friend's place so am trying to avoid having it run all the time.
Looks like push backup uses snapshots and maintains integrity better so definitely worth researching further. Any help with the power scheduling aspects will be much appreciated. I searched for this a while back and while there were mentions of custom scripts, I didn't think there was a solution that'd survive firmware upgrades.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
