Within the Synology interface, open the package manager, select the Crashplan package, then stop and restart the service.

Note that the prompt says ‘DSCP decimal value’.Īfter making this change you must restart the service for it take effect. From previous experience with Crashplan on windows, I tried an DSCP decimal value of 10. I’ll skip the predefined options for now, and select the DSCP option. This should be straightforward – configure the Crashplan desktop client to connect to our headless NAS, and change the QoS settings: See previous post of how to do this with a Draytek SOHO router. This then allows you de-prioritize Crashplan traffic at your router and so leave you internet connection fast and responsive for other clients and applications. This post explores how to work around a serious bug (again!) in the Crashplan QoS settings, monitor the traffic via ssh and finally being able to successfully set the Differentiated Services Code Point (DSCP) values for upload traffic for QoS. Shortly afterwards I again needed to tag the crashplan traffic with a DSCP value so that the bulk upload traffic could be deprioritized to prevent it crippling my internet connection for other contending devices.

In other words, I never found a way to make the Crashplan setting work, but the work around was pretty solid.Įarlier this year I acquired a Synology DS415Play diskstation, a decent NAS which could store the constant accumulation of photos, video clips and music, but I also installed the excellent Crashplan package from PCLoadLetter on it in ‘headless’ fashion using Scott Hanselman’s guide. Way back in June 2012 I wrote about how you could set QoS (Quality of Service) DSCP values on Crashplan traffic on Windows, not by using the ineffective settings within Crashplan, but by using the group policy tool to tag traffic coming from the CrashplanService.exe process itself.

Crashplan synology nas