NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS RN42200 hangs completely up during backup to RN31400
Hi everyone, I am trying now since already a year to do backups from my newer RN42200 (two 12TB Disks in RAID 1) to my older RN31400 (4 Disks, RAID 5). Both are on OS 6.10.3. I tried Backups via SMB,...
Hi Stephen, I think the MTU size (at 9000) was the root cause! After changing it on both boxes back to 1500 and a reboot everything worked. I successfully tried via NFS, SMB and Rsync.
But first I had to delete the existing backup-jobs and had to create new ones. The old ones were not working! Whyever...
Wow, this is really absolutely unexpected. Strange, because from all other devices on the network it was always working! No matter which OS, Windows as well as Linux.
However, many thanks Stephen for your help and especially also for your patience which I really appreciate. May be I get ometimes to opportunity to help you too!!!:smileyvery-happy:
Are the NAS on the same network?
I run daily backups - one for each share. These are all set up for rsync.
Can you provide more information on the backup settings you are using? One thing I suggest is using the IP address for the remote NAS - not the host name.
Thank you, yes they are both on same net. Static-IP: 192.168.1.8 and 192.168.1.20. Initially I had also an both of them the second NIC active in VLAN 192.168.50.0. But I deactivated them in the meantime.
I did a lot of tries. Also tried the Hostname and/or IP-Address. No change. I always deleted the faulty backup jobs after the tries. But to take the simple one (SMB):
- Created on both boxes new Share.
- I just copied a few files for testing into the source. (Via Webinterface)
- Only SMB active.
- No Snapshots, nothing else.
- User rights: Everbody: Read/Write.
- Source is Local. Target is Remote.
- No Schedule. Only one time run.
- Via Hostname: I searched for the other box via Admin/Password and it was found: NAS3-Worli.local. So chech of connection was always successful.
- Via IP: I entered it manually.
- Only when I tried to see the Shares on the Abkup-Box I didnt see one of the about 20 Shares.
Sometimes the Backup Job created several empty directories on the Back-Box and started in one of the Dirs with a file but it had always ZERO byte and stopped.
May be somethnig with the file permissions? (I did also Reset to Default on the Share.)
Kind regards, Worli
Personally I use Rsync. I run the backups on the destination NAS, and as noted earlier I use one backup job per share.
The settings I use are:
I use these on several NAS (running daily backups), and they run very reliably.
Can you tell us more about your network setup?
Hi Steven, Thank you. I tried now as you advised me to do. Negative. Tried to backup the share musik as in your example. Of course Rsync is activated on Source and I also added the IP of Target as allowed for Rsync. There was already the address of my Debian 10 Server in. With the Debian via Rsync it was always working fine.....
Also to say that before I got my RN4220 I had a ReadyNAS NVX and I did successfully Rsync-Backup from my RN31400 to the NVX!
On Network side I use four Ubiquity Switches, Unifi USG Secure Gateway and an Unifi Access Point. So nothing special, all locally in my appartment. Additionally a VLAN 50 for my Nextcloud Server which can be connected via Internet. The RN4220 is physically connected to first Switch after the USG. The RN31400 is on the last Switch. In the past I had both ReadyNAS connected to both VLAN (1+50). But during my tests I deactivated the second NIC on the ReadyNAS.Tomorrow I will also connect both ReadyNAS to the same switch and see what happens.
Hi Stephen, both NAS-boxes are now on the same Switch. Only one NIC active on both NAS-boxes.
But no change. Backup not successful. After 60 minutes:
- Rsync Backup terminated on Target-NAS with “Error during copying.”
- Target-Directory is still empty.
- Already a longer time before the backup job terminated the disks on Source-NAS went to „sleeping“, as configured. At this stage Backup-Job was still in status “Running” on Target-NAS.
Protocol of Backup-Job. (Shall I translate it?)
*-------- Informationen zum Sicherungsauftrag --------
Name des Sicherungsauftrags: job_001
Typ des Sicherungsauftrags: Inkrementell
Protokoll: rsync
Sicherungsquelle: [remote:rsync]/192.168.1.20::musik
Sicherungsziel: [temp]/
Startzeit der Sicherung: Do Apr 23 2020 8:56:35
Endzeit der Sicherung: Do Apr 23 2020 9:56:43
Sicherungsstatus: Fehlgeschlagen: Fehler während des Kopiervorgangs.The log looks like a normal backup job to me, so that part seems fine.
Are the file permissions set in Musik and Temp to allow full access?
Have you tried setting up a test share on the source NAS that uses default settings, then enable rsync for it? Then put a couple files into it for testing purposes?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
