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 j...
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 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.
StephenB wrote:But it would be nice if there was a way to use a power schedule with push-backup jobs.
The ability of a backup job to send a WoL to the remote NAS and a shut-down at the end would certainly help. Of course, if there were a scheduled or manual shut-down on the remote NAS, that would override.
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!
