We recommend that you do not include .PST files in FSA or CFSA scanning jobs. This is because .PST files can be very large and contain many individual items. This can cause scanning jobs to take a very long time to complete. It can even mean that the .PST contents are not fully analyzed. This can happen if a policy engine takes too long analyzing a .PST file and so exceeds the FSA's permitted analysis timeout. Consequently, the FSA flags the .PST file as a failure.
This recommendation is particularly important for FSA scanning jobs, which do not automatically exclude .PST files. Conversely, CFSA scanning jobs exclude PST files by default (included and excluded files are defined in the Data At Rest Protection folder in the local machine policy).
To apply policy to e-mails and attachments in .PST files, we recommend you run Import Policy jobs, using PSTFile parameters to configure the import job. For details of these parameters, see the Archive Integration Guide; search for 'Event Import, parameters'.
|
Copyright © 2014 CA.
All rights reserved.
|
|