TCP packet QoS settings not applied to the CrashPlan app

Overview

This article describes the solution for a known issue in which the CrashPlan app does not apply the TCP packet QoS priority settings.

Affects

Code42 environments that both:

• Use IPv4 (or a mix of IPv4 and IPv6)
• Use CrashPlan app version 4.7.0 or later

Considerations

• This solution is only available for devices using CrashPlan app version 4.7.0 and later.
• You must repeat these steps each time you upgrade the CrashPlan app. These changes are reverted during the upgrade process.

Before you begin

For customers with an on-premises authority server, you must upgrade your Code42 environment to Code42 server version 5.3.0 and CrashPlan app 4.7.0 or later.

Recommended solution

To enforce the TCP Packet QoS setting:

1. On the device where the CrashPlan app is installed, navigate to the CrashPlan app configuration file:
   • Windows
     • Installed for everyone: C:\Program Files\CrashPlan\CrashPlanService.ini
     • Installed per user: C:\Users\<username>\AppData\<Local|Roaming>\Programs\CrashPlan\CrashPlanService.ini
   • OS X
     • Installed for everyone: /Library/LaunchDaemons/com.crashplan.engine.plist
     • Installed per user: ~/Library/LaunchAgents/com.crashplan.engine.plist
   • Linux: /usr/local/crashplan/bin/run.conf
2. Open the file in a text editor.
3. Edit the file:

• Windows
  Add this line to the end of Virtual Machine Parameters:-Djava.net.preferIPv4Stack=true
• OS X
  Under the line <string>-Djava.awt.headless=true</string>, paste the following line:
  <string>-Djava.net.preferIPv4Stack=true</string>
• Linux
  Add this line to the end of SRV_JAVA_OPTS:
  -Djava.net.preferIPv4Stack=true

4. Save your changes.
5. Restart the device.

Related topics