High CPU Utilization during Backup

High CPU Utilization during Backup

Cause:

From 14740, below listed parameters will no longer be included in the command. As a result, when performing backups, 7-Zip utilizes a high number of CPU threads, leading to increased CPU usage.
  1. mmt - Sets number of CPU threads
  2. mmemuse  - Sets a limit(in percentage) on memory usage (RAM) for compressing and decompressing.
Note: Prior to 14740, the 'mmt' parameter was configured as Half of Total CPU Threads and the 'mmemuse' parameter was set to 50%.

Fix:

The Older Configuration has been retained.

Steps to apply the fix:

Refer the article : How to apply fjar ?

Jar Compatibility:

Build
Compatible Jar
14740
High_CPU_14740_Fix.fjar
14750, 14810
High_CPU_14750_Fix.fjar




      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • SQL Server High CPU - To collect queries consuming CPU resources

                      1. To get an idea of how much CPU the queries are currently using, out of overall CPU capacity, run the following statement: DECLARE @init_sum_cpu_time int, @utilizedCpuCount int --get CPU count used by SQL Server SELECT @utilizedCpuCount = COUNT( * ...

                    • How to take a backup in SDP-MSP

                      Note: In 10.6 when running a backup using backdata.bat/backdata.sh the backup file will be in .ezip format. Backup with .ezip format can be restored to the same database platform only. For example a backup with .ezip when taken from postgres DB ...

                    • Backup password protection

                      The application backup is protected with a password. The password is required to open the backup file / restore it. This password can be changed in the Admin-> Backup schedule page. Click Edit Scheduling and input the backup password to change the ...

                    • SQL Backup permission post 10.6 Upgrade.

                      Error on the logs: [20:00:50:193]|[04-25-2022]|[com.adventnet.taskengine.backup.DbBackupTask]|[INFO]|[124]: BackupStatus updated in DB :: <BackupStatus backup_id=1806 backupType="FULL_BACKUP" ...

                    • Scheduled Backup failure due to permission issue in pgsql folder

                      Error Traces: [com.adventnet.db.adapter.BackupRestoreUtil]|[WARNING]|[250]: pg_basebackup: could not get write-ahead log end position from server: ERROR: could not open file "./pg_hba.conf_3may23.bkp": Permission denied| ...

                      Related Products