The Backup Manager has been installed to the /opt/MXB directory and started with the /etc/init.d/ProcessController startup script. The script started the /opt/MXB/bin/ProcessControllerbinary. ProcessController checks and restarts the BackupFP binary if necessary. You can specify UID and GID for the BackupFP in the /opt/MXB/etc/ProcessController.config file. It's root by default:


<param key="user" type="int">0</param>
<param key="group" type="int">0</param>

Please take a minute to verify that the BackupFP is initialized and bound to the rights ports. The first port is 5314 (same for all). The second one is 5000, 5001, or 4000 depending on your service provider.


# netstat -nlp|grep BackupFP

Here is a sample response:


tcp     0      0 0.0.0.0:5314         0.0.0.0:*       LISTEN      6586/BackupFP
tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 6586/BackupFP

The first part of the response displays a remote communication port for legacy devices powered by the desktop-based edition of the Backup Manager. The second part – for devices with a web interface.


If you get no response, it means that the BackupFP hasn't been initialized. In such a case it'll be necessary to look into your log files to investigate the issue.


The ports can be changed if your network requires it. You can do it through config.ini – a special configuration file located in the Backup Manager installation folder (learn more). Here is how to edit the file:



  • To the [General] section, add CommunicationPort=7777

  • In the [HttpServer] section, find the HttpServerPort parameter and edit is value.

  • Restart the Process Controller.


# /etc/init.d/ProcessController restart