Resolve OOM issues on a Cloud Backup client - Cloud Backup

If an out of memory (OOM) issue occurs on the PC where a Cloud Backup client resides, the backup job fails. To resolve OOM issues, you can increase CPU and memory resources, split the source path into multiple directories, configure bandwidth throttling, and reduce the resource usage of the Cloud Backup client. This topic describes how to resolve OOM issues.

Background information

When you use a Cloud Backup client to back up an excessively large amount of data whereas the system resources are insufficient, the Cloud Backup client may consume a large number of system resources. In this case, the backup process may trigger an OOM issue and then is terminated by the system, resulting in a backup failure.

Important

If you encounter an OOM issue, you can expand the memory or CPU capacity of the PC where the Cloud Backup client resides, or try to resolve the issue by referring to this topic. For more information about common backup failures, see How do I resolve backup failures?

Method 1: Split the source path

Split the source path in a backup plan into multiple directories.

In the same backup plan, backup jobs for the split directories are run in series. The amount of data in each split directory is reduced compared to the original path. Therefore, the resources consumed by each backup job are also reduced. The following example shows the source path in your backup plan:

-/backup
--/path1
--/path2
--/path3

You can split the source path into three directories.

Note

After the splitting, the backup plan is executed based on the split directories. The original backup and restore jobs are not affected.

-/backup/path1
-/backup/path2
-/backup/path3

拆分目录

Method 2: Configure bandwidth throttling for a backup plan

In the Cloud Backup console, find the backup plan corresponding to the data source, modify the backup plan, enable bandwidth throttling, and then configure the related parameters.

Method 3: Reduce the resource consumption of the Cloud Backup client

You can modify the configuration file of the Cloud Backup client to limit the number of concurrent files. This way, the memory resources consumed by the Cloud Backup client can be reduced.

Important

This method does not apply to the backup of anti-ransomware files on Security Center servers.

Log on to the host from which files are backed up.
Find and open the installation path of the Cloud Backup client.
- Linux
  - The default installation path for the new Cloud Backup client is /opt/alibabacloud/hbrclient.
  - The default installation path for the old Cloud Backup client is /opt/alibabacloud/hbr/.
- Windows
  - The default installation path for the new Cloud Backup client is C:\Program Files\Aliyun Hybrid Backup Service Client.
  - The default installation path for the old Cloud Backup client is C:\Program Files\Aliyun Hybrid Backup Service.
If the hbr.config file does not exist, create the hbr.config file in a subdirectory of the client folder.
Note
The hbr.config file must be at the same directory level as the ids file.

Configure the following parameters in the hbr.config file.

You can modify the configuration file of the Cloud Backup client to limit the number of cache files and concurrent files. This reduces the memory usage during file backup. For more information about the memory required for file backup, see What are resource requirements for backup?

The following example shows the configurations of the hbr.config file:

max_file_workers=5
max_blob_uploader=16

You can click here to download the hbr.config file.

Parameter	Description
max_file_workers	The maximum number of files or directories that can be concurrently backed up. Default value: 10.
max_blob_uploader	The maximum number of data blocks that can be concurrently uploaded. Default value: 32.

References

Important

If the issue persists, submit a ticket.