Stored Data Integration Guide › Scanning Jobs › Scanning Job FAQs › Do I Use Multiple Scanning Jobs or Multiple FSAs?

Do I Use Multiple Scanning Jobs or Multiple FSAs?

The FSA is highly flexible. You can have a single FSA running many scanning jobs or multiple FSAs each running a few jobs. Which deployment is appropriate for you depends on the volume of data you need to scan, your network configuration, available hardware and so on. However, there are some practical considerations that can inform your decision:

• A single FSA running multiple scanning jobs is easier to deploy. But all scanned files that need policy processing are channeled through the same hub. Hub capacity is therefore a key determinant.
• Multiple FSAs permit load balancing and can share a SQL Server database server. Each FSA can use a separate database hosted in the same instance of a SQL Server database engine. Or each FSA can use a separate instance of SQL Server, with all instances hosted on the same machine. For further guidance, see the Database Guide; search for ‘shared database’.
• If you deploy multiple FSAs, each running local scans, then all scanned files are automatically associated with the source machine when the file event is stored in the CMS database.

More information:

What Happens If No Event Participant Is Specified?