At the time of writing this article in June 2018, the most recent version of CrashPlan for save-to-NAS is 5.x.x, and it does not appear to be built for ARM. In fact, CrashPlan no longer has proper ARM support. CrashPlan 5.x.x was built using CPUs up to Skylake as well as Ryzen, Silvermont and Broadwell-U, and Intel Xeon Silver 4100 and 6000 series chips, and I do not know how far back Intel support goes.
Synology may restrict some public-facing ports and network configurations, but every Synology NAS I have ever had works properly when using any of its official supported protocols for file sync and remote backup. Even if you choose to browse the share network of the NAS device, you will still have access to the folders of that NAS through synchronised PCs and OSX, Linux, Android, iOS, or Windows phones and tablets. As of June 2018, you need to use your NAS's HTML interface to access these shares. If you have an older version of CrashPlan, or a NAS with a Deploy Station, or some other service is blocking HTML ports on your NAS, you may fail to be able to browse those folders. Take any NAS I have had in the recent last 10 years for example, older firmware ARM NAS running CentOS, you should be able to browse those folders just fine with any browser on any operating system.
It is wrongly suggested by CrashPlan that you can link the public directory with a network drive. There is no provision for such an option. I have never seen such a configuration work for other programmes.
In addition to CPU and RAM, I would strongly suggest that you over-engineer your NAS storage system. With 4TB of hard disk, you should not need to buy a new NAS device every few years. If your NAS is more than 4TB, you should at least be planning to replace it in a year, every few years. d2c66b5586