Well after purchasing a WD MyCloud Mirror I found myself on these forums as the product does not work well out of the box and requires a bit (A LOT) of refinements to get it operating optimally. This thread is intended to outline what I’ve done to set my box up and thre issue I see. Perhaps it will help others.
Out of the box - executing a simple backup script to save Documents and Pictures files took several hours using rsync. This led me to look into various possible issue.
Testing with Black Magic Disk Speed Test - I was getting speeds under 1 MB/s which is clearly unsatisfactory.
Identified issues where that this type of copy had the CPU running at 100%.
Physical Network speed
Generally speaking - given the mixed and old network that I have intitally I thought that I had an issue with my router. I have an older Speedport 723 (Lan speed is 100Mbits/s) and decided to first connect it directly to the Mac and set the speed on the WD to 1000Mb. This improved things, a little. But clearly, seeing the the CPU was still running at 100% during saves and that the network was still very slow, was not the issue.
Various sites and thread discuss issues with different NAS and the protocol used. After testing with my setup (and contradictory to what some people report) I found that, for me, mounting the shared drives with the afp:/server-name was faster than smb: or cifs: . A slight improvement. Still not acceptable.
The best improvement to date, that I’ve seen, in terms of reducing CPU usage and fastest transfer speeds is to use the WD control panel and under Settings/General turning off Cloud Access. (And I’ve also turned off Media/DNLA Server and Media/ITunes). This delivers around 75-90 MB/s read/writes which is acceptable with my network.
Unfortunately, this is an unacceptable compromise as this NAS was intended to allow remote backups and turning off the Cloud Access permanently is not a solution.
The issue has been processes running on the the WD that use 100% CPU - SMDB, convert & wdphotodbmerger.
I’ll probably end up stopping these prcoesses during backup scripts - as briefly outlined here:
But frankly a conmsumer product that needs me to ssh over to do that? (shaking my head)
I’ll keep reporting to this thread as I find solutions.
(Firmware is 1.053)