Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > Deploying SRM Profiler > File Analysis

File Analysis

Table of contents
No headers

Updated: June 16, 2017

It is recommended NOT to use SRM Profiler server for File Analysis. You should instead use a SRM Profiler proxy agent. The proxy agent should be dedicated to running File Analysis and nothing else. This is because of heavy workloads that can be placed on the SRM Profiler proxy agent due to large file scans.

Determining how much File Analysis the SRM Profiler proxy agent can do is dependent on three things:

  • The number of files being scanned.
  • The rate at which the SRM Profiler proxy agent can process them. It is best for you to run test in your environment to determine your files per minute (Files/Min) rate. This result can be viewed in the File Analysis Stats Report located in Quick reports.
  • The time window that you have to process the files. This is generally a few hours to overnight if daily, or weekend if weekly. Ideally, File Analysis should not run on a single target for more than 24 hours.

The following formula will help determine if your current deployment of SRM Profiler can collect File Analysis in a timely manner.

Duration = Number of Files

           ===============
             Files/Min

If the duration is less than the time window, then you can do the File Analysis with one SRM Profiler proxy agent. If it is greater, you need to deploy another SRM Profiler proxy agent (and so on). For more information on File Analysis see Sett Up File Analysis.

 
Last modified
22:53, 11 Jul 2017

Tags

Classifications

Public