If you are like me and have 100’s of 1000’s of files, such as photos, music, video, data, etc, then it is going to take a long, long, long time. For my first backup, it took a few days to get the 1.8 TB of data across to the WD My Book. Once that was done, the incrementals take 4 to 5 hrs to read through the disk and find the differences.
One of the issues is that the system get’s hosed by rsync which floods the disk. If you log in using SSH, run top and you will see:
top - 20:05:20 up 5 days, 22:36, 1 user, load average: 3.09, 3.16, 3.12
Tasks: 84 total, 1 running, 83 sleeping, 0 stopped, 0 zombie
%Cpu(s): 7.0 us, 20.6 sy, 0.0 ni, 69.2 id, 2.8 wa , 0.0 hi, 0.3 si, 0.0 st
KiB Mem: 232448 total, 175872 used, 56576 free, 4032 buffers
KiB Swap: 500672 total, 82496 used, 418176 free, 19456 cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2353 root 20 0 0 0 0 D 1.0 0.0 20:11.51 pfe_ctrl_timer
Look at the WA, that is the %WAIT state the CPU is in…When running rsync, this is sitting at 90%.
In version 3 of the system, this was not so much of a big deal and things ran smoothly.
In addition, the other reason why the system is not responsive is that it is running out of memory…Look at the SWAP above. There is 500 MB of swap with 82 MB used. I have already shutdown apache, wdmcserverd, wdphotodbmerger, and the base 256 MB of memory is still over committed.
With everything running, rsync will fail with Out Of Memory complaints.
So, since I use this for a file share as backup, the system is aways responsive when the other ancillary products are not running.
-Ben