Backup operation is slow. How do I troubleshoot the slowness?

If you are experiencing performance issues during backup, you can troubleshoot them by enabling logging of performance details in the log files. These performance counters contain information that help in resolving the performance related issues during backups. The performance reports are generated and available at the following location on the MediaAgent computer:

· <software_installation_path>\Log Files\ResourceMonitor\PerfLog_CommVaultJobsStreamStats-1.0.csv

· <software_installation_path>\Log Files\CVPerfMgr.log For more information on viewing log files, see Viewing the Log Files of an Active Job.

Performance counters printed in the log files include:

Open File Time taken to open a file.

Read Time taken to read the file from a disk.

Buffer Allocation Time taken to assign or distribute the network buffers on the client computer.

Pipeline Write Time taken to write data in to the network buffers on the client computer.

The CVPerfMgr log file displays the time taken by a particular process. For example, a log snippet may look as follows:

|*4*|*Perf*|13| ----------------------------------------------------------------------------------------- |*4*|*Perf*|13| Perf-Counter Time(seconds) Size |*4*|*Perf*|13| ----------------------------------------------------------------------------------------- |*4*|*Perf*|13| |*4*|*Perf*|13| Windows File System Agent |*4*|*Perf*|13| |_Buffer allocation.......................... 144

|*4*|*Perf*|13| |_Read....................................... 156 5230734248 [4.87 GB] [112.42 GBPH] |*4*|*Perf*|13| |_Pipeline write............................. 69 5230942882 [4.87 GB] [254.18 GBPH] |*4*|*Perf*|13| |_Open File.................................. - |*4*|*Perf*|13| |_FSDM Load Library.......................... - |*4*|*Perf*|13|

You can also check the scan performance counters that are generated and available at the following location on your client computer:

You can also check the scan performance counters that are generated and available at the following location on your client computer:

<software_installation_path>\Log Files\FileScan.log

The FileScan log file displays the time taken for the scan operation. For example, a log snippet may look as follows:

5136 10bc 07/27 11:32:58 21077 Find::PostExecuteScan_Statistics(5449) - Total time for Optimal Scan (Data Classifier): 103.374705 5136 10bc 07/27 11:32:58 21077 Find::PostExecuteScan_Statistics(5450) - Generating tables: 4.885698 5136 10bc 07/27 11:32:58 21077 Find::PostExecuteScan_Statistics(5451) - QueryCallback: 0:20.619982, 241348 samples, 0:00.000085 average, 11704/second 5136 10bc 07/27 11:32:58 21077 Find::PostExecuteScan_Statistics(5452) - QueryIteration: 0:03.818934, 241357 samples, 0:00.000015 average, 63200/second 5136 10bc 07/27 11:32:58 21077 Find::PostExecuteScan_Statistics(5456) - IsFileFilteredOut: 0:05.813762, 241354 samples, 0:00.000024 average, 41514/second 5136 10bc 07/27 11:32:58 21077 Find::PostExecuteScan_SetJobInfo(5508) - Found 642 files and 391 folders (1033 total items) to back up 5136 10bc 07/27 11:32:58 21077 Find::PostExecuteScan_SetJobInfo(5538) - Updated TotalBytesToBackup Perfctr, TotalBytesToBackup=[0]

Recommendations:

· If multiple reads are enabled on the disk, verify that the hardware you use supports multiple reads else enabling multiple reads might degrade the disk read performance.

· You can use Raid disks or disks that allow multiple simultaneous reads which improves the performance of the backup job.