NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN102 - Backup job always stalls when it reaches 1.3TB - where to look?
Hi, I am usually running rsync to backup my one RN102 to my other RN102 (both 2x4TB WD Red in X-RAID, 1 volume, 10 shares). While most shares will backup fine, at one share (size ~1.8TB) the rsyn...
It's best to send logs to the mods ( JohnCM_S and Marc_V ), not to me.
FWIW, it is odd that a backup job would be giving you non-existent file errors on the backup source. And odder still that it is reaching files outside the share.
The backup job is running on NAS-Wettmar?
Dirk_ wrote:
Maybe I have to clean the old snapshot data? How can I do so?
You go into the shares page of the admin web ui. Click on the settings wheel for the share, and then choose recover. That will show you any snapshots that still exist. You select one or more snapshots, right-click, and then delete them. Be careful not to select rollback.
StephenB :
Yes the backup job is running on NAS-Wettmar.
The option "Recover " in the "Share" menu is greyed out, so no access.
Even if I go into settings in the "Share" menu and enable "Snapshot Access" in the snapshot tab,
the option "Revover" still stays greyed out.
BTW: When applying above, the system shows me "/data/Backup/snapshot" as directory and not /data/._snapshot/...
OK, I will send my logs to JohnCM_S in a PM.
Best regards
Dirk
Dirk_ wrote:
Even if I go into settings in the "Share" menu and enable "Snapshot Access" in the snapshot tab ...
BTW: When applying above, the system shows me "/data/Backup/snapshot" as directory and not /data/._snapshot/...
Normally the snapshots are in a hidden folder inside the share that is called .snapshots. In Linux systems, folders and files are hidden if their name starts with a period. Snapshots (like shares) aren't ordinary folders, they are btrfs subvolumes.
For instance, on my own system you can see 7 snapshots in the Backup share.
root@NAS:~# btrfs subvolume list /data | grep -i backup ID 278 gen 910448 top level 5 path Backup ID 279 gen 910457 top level 278 path Backup/.snapshots ID 29029 gen 909489 top level 279 path Backup/.snapshots/627/snapshot ID 29038 gen 909622 top level 279 path Backup/.snapshots/628/snapshot ID 29048 gen 909655 top level 279 path Backup/.snapshots/629/snapshot ID 29057 gen 909741 top level 279 path Backup/.snapshots/630/snapshot ID 29060 gen 909870 top level 279 path Backup/.snapshots/631/snapshot ID 29062 gen 910255 top level 279 path Backup/.snapshots/632/snapshot ID 29067 gen 910448 top level 279 path Backup/.snapshots/633/snapshot
If you make the snapshots accessibles to windows, then the folder is no longer hidden (so it is renamed to snapshots).
/data/._share is another hidden folder, which contains the configuration information for each share. (in this case the configuration is stored in /data/._share/Backup). It shouldn't contain a .snapshots subfolder.
I am thinking it might be useful if you tried setting up the backup job on NAS_Winsen instead (which would make NAS_Wettmar the remote source, and NAS_Winsen the local destination), and see if you get different results. If you try that, the source path is just the share name (with no slash). The destination path is blank. You can set the "schedule full backup" option on the options page to "never" - making the first backup incremental. Of course you'd also need to enable rsync on the backup share on NAS_Wettmar.
It might also be useful to look for errors on NAS_Winsen (in particular, for network issues). Those rx errors might be part of the puzzle.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
