Getting In-Depth with Backup My Org's MAX_CONCURRENT_FETCH

Purpose: This article explains the MAX_CONCURRENT_FETCH property in the nodeconfig.json file for Backup My Org, its implications on system performance, and how to configure it appropriately based on various factors.

What is MAX_CONCURRENT_FETCH?

MAX_CONCURRENT_FETCH is a parameter in Backup My Org’s nodeconfig.json configuration file that controls the number of simultaneous fetch operations can be executed. Adjusting this parameter helps manage CPU utilization by balancing the CPU load from being overloaded. It also helps with network performance during backup and restore operations.

Default Setting

• Default Value: 5

Possible Range

• Minimum Value: 1

• Maximum Value: 20

Considerations for Configuration

CPU Utilization

• Monitor the CPU utilization on both the Backup My Org server and the Enterprise server.

• If CPU utilization is consistently low, you can consider slightly increasing MAX_CONCURRENT_FETCH.

• If CPU utilization on either the Backup My Org server or the Enterprise server plateaus at 100%, it indicates that the server is fully/over utilized, and should reduce MAX_CONCURRENT_FETCH to avoid overloading the system.

Network Errors

• Frequent 504 Gateway Timeout errors or other network-related issues can indicate that MAX_CONCURRENT_FETCH is set too high.

• In such cases, lower the MAX_CONCURRENT_FETCH value to reduce the load on the network and improve reliability.

 Steps to Adjust MAX_CONCURRENT_FETCH

1. Open the nodeconfig.json file located in your BMO installation folder

2. Locate the MAX_CONCURRENT_FETCH property.

3. Adjust the value with consideration to what has been mentioned in this article. (Default: 5, Range: 1 - 20)

4. Save the changes to the nodeconfig.json file.

5. From the Start menu, locate the Services application.

6. In Services, locate and select Backup My Org and restart the service for the changes to take effect.