Veritas Enterprise Vault™ Reporting

Last Published:
Product(s): Enterprise Vault (12.1)
  1. About this guide
    1.  
      Introducing this guide
    2. Where to get more information about Enterprise Vault
      1.  
        Enterprise Vault training modules
  2. Introducing Enterprise Vault Reporting
    1.  
      About Enterprise Vault Reporting
    2.  
      About Enterprise Vault Reporting's reports
    3.  
      How Enterprise Vault Reporting works
    4. How FSA Reporting works
      1.  
        About the FSA Reporting proxy servers for non-Windows file servers
      2.  
        FSA Reporting proxy server requirements
      3. About the FSA Reporting databases
        1.  
          About maintaining the FSA Reporting databases
        2.  
          About the FSA Reporting user account
  3. Overview of implementing Enterprise Vault Reporting
    1.  
      Implementing Enterprise Vault Reporting
  4. Installing Enterprise Vault Reporting
    1.  
      Where and when to install Enterprise Vault Reporting
    2.  
      Prerequisites for Enterprise Vault Reporting
    3.  
      Enterprise Vault reports that require monitoring or auditing to be enabled
    4.  
      Preparing for the installation of Enterprise Vault Reporting
    5.  
      Installing the Enterprise Vault Reporting component
  5. Configuring Enterprise Vault Reporting
    1.  
      About configuring Enterprise Vault Reporting
    2.  
      Configuring Enterprise Vault Reporting
    3.  
      Checking that the configuration of Enterprise Vault Reporting was successful
    4.  
      Enabling the synchronization of Enterprise Vault RBA role membership
    5.  
      Reconfiguring the data access settings for Enterprise Vault Reporting
  6. Configuring FSA Reporting
    1.  
      Configuring FSA Reporting
    2. Preparing for an FSA Reporting proxy server
      1.  
        Preparing an EMC Celerra/VNX device to work with an FSA Reporting proxy server
    3.  
      Adding a file server as an archiving target with FSA Reporting data collection enabled
    4.  
      Enabling FSA Reporting data collection for an existing target file server
    5.  
      Enabling or disabling FSA Reporting data collection for a file server target volume
    6.  
      Setting the defaults for FSA Reporting data collection
    7.  
      Setting the storage location for FSA Reporting's temporary files
    8.  
      Verifying the placeholders on EMC Celerra/VNX devices
    9.  
      Including NetApp filer snapshot folders in FSA Reporting scans
    10.  
      Checking that the configuration of FSA Reporting was successful
  7. Accessing the reports
    1.  
      About accessing Enterprise Vault Reporting's reports
    2. Administrator roles that provide access to Enterprise Vault Reporting's reports
      1.  
        Administrator roles that provide access to Enterprise Vault Reporting's operation reports
      2.  
        Administrator roles that provide access to FSA Reporting's reports
    3. Accessing Enterprise Vault Reporting's reports from SQL Server Reporting Services Report Manager
      1.  
        About exporting Enterprise Vault Reporting reports from SQL Server Reporting Services Report Manager
      2.  
        About scheduling Enterprise Vault Reporting reports in SQL Server Reporting Services Report Manager
    4.  
      Accessing Enterprise Vault Reporting's reports from the Administration Console
  8. Managing FSA Reporting
    1.  
      Managing FSA Reporting
    2.  
      Viewing the status of FSA Reporting
    3.  
      Running an unscheduled FSA Reporting scan on a file server
    4.  
      Stopping FSA Reporting scans
    5.  
      Disabling all FSA Reporting data collection
    6.  
      Changing the default FSA Reporting data collection schedule
    7.  
      Changing a file server's FSA Reporting database
    8. Maintaining the FSA Reporting databases
      1.  
        Trimming the FSA Reporting database history tables
      2.  
        Determining whether an FSA Reporting database is in purging job maintenance mode
      3.  
        Changing the schedule for an FSA Reporting database purging job
      4.  
        Running the FSA Reporting database purging job manually
    9.  
      Changing the FSA Reporting proxy server for a non-Windows file server
    10.  
      Modifying the FSA Reporting data collection parameters
    11.  
      Obtaining data for a specific file type in the FSA Reporting reports
    12.  
      Upgrading the FSA Agent
  9. Troubleshooting Enterprise Vault Reporting
    1.  
      About troubleshooting Enterprise Vault Reporting
  10. Appendix A. Report overviews
    1. The Enterprise Vault Reporting operation reports
      1.  
        Archive Quota Usage report
      2.  
        Archived Items Access report
      3. Archived Items Access Trends report
        1.  
          Sample output from the Archived Items Access Trends report
      4.  
        Content Provider Ingest History report
      5.  
        Content Providers Licensing and Usage Summary report
      6.  
        Domino Mailbox Archiving Status report
      7.  
        Domino Server Journal Mailbox Archiving Health report
      8.  
        Domino Server Journal Mailbox Archiving Trends report
      9.  
        Enterprise Vault Server 24-hour Health Status report
      10.  
        Enterprise Vault Server Seven Day Health Status report
      11.  
        Exchange Mailbox Archiving Status report
      12.  
        Exchange Server Journal Mailbox Archiving Health report
      13.  
        Exchange Server Journal Mailbox Archiving Trends report
      14.  
        IMAP usage report
      15.  
        Items Archival Rate report
      16.  
        Move Archive report
      17.  
        Single Instance Storage Reduction by File Type report
      18.  
        Single Instance Storage Reduction per Vault Store Group report
      19.  
        Single Instance Storage Reduction Summary report
      20.  
        Vault Store Savesets report
      21.  
        Vault Store Usage by Archive report
      22.  
        Vault Store Usage by Billing Account report
      23.  
        Vault Store Usage Summary report
    2. The FSA Reporting data analysis reports
      1.  
        Archive Points Space Usage Summary report
      2.  
        Drive Space Usage on a Server report
      3.  
        Drive Space Usage Summary report
      4.  
        Duplicate Files on a Server report
      5.  
        Duplicate Files Summary report
      6.  
        File Group Space Usage on a Server report
      7.  
        File Group Space Usage Summary report
      8.  
        Inactive Files on a Server by File Group report
      9.  
        Inactive Files on a Server by User report
      10.  
        Inactive Files Summary report
      11.  
        Storage Summary report
      12.  
        Storage Trends report
      13.  
        File Space Usage on an Archive Point report
      14.  
        Largest Files Per Volume report
      15.  
        Largest Files of a Specified File Type Per Volume report
      16.  
        Top Duplicate Files Per Volume report

Trimming the FSA Reporting database history tables

You must trim the history tables for each FSA Reporting database regularly to keep the tables at a manageable size, while retaining recent and trend-related information. Enterprise Vault provides a trimming utility for this purpose. The utility removes data beyond a specified age, but it retains the data for the trend reports.

The trimming utility is named FSAReporting_TrimData.bat. It is located in the FSAReports subfolder of the Enterprise Vault program folder, for example:

C:\Program Files (x86)\Enterprise Vault\FSAReports

Note:

To execute the utility from the Enterprise Vault server, the SQL Server client tools must be installed on the Enterprise Vault server. Alternatively you can copy the utility to the SQL Server computer where the FSA Reporting database is located, and execute the utility from there.

For security reasons only the FSA Reporting user can execute the utility. The FSA Reporting user is the Windows user account that you specified for FSA Reporting to use when you ran the FSA Reporting Configuration wizard.

Note:

You cannot run the utility when the FSA Reporting database is in purging job maintenance mode. If you attempt to run the utility, it exits with an explanatory message.

To trim the FSA Reporting database history tables

  1. By default, the trimming utility trims the FSA Reporting data for all of the file servers for which the specified database holds data. To specify a list of file servers on which the utility is to act, place an XML file in the same folder as the trimming utility. The XML file must contain a single line in the following format:

    <FileServerList><FileServer Name=''Site\Domain\FileServer''/></FileServerList>

    where:

    • Site is the Enterprise Vault site that contains the file server.

    • Domain is the file server's domain.

    • FileServer is the local name of the file server.

    The file server name must use the format ''Site\Domain\FileServer'', even if the file server is specified in the Administration Console using an IP address. You must enclose the file server name in two pairs of single quotes as shown, not double quotes. The FSAReports folder contains an example XML file with a line in the required format.

    The following example specifies two file servers for which to trim FSA Reporting data. Remember, the text must be contained on a single line:

    <FileServerList><FileServer Name=''EVSite\MyDomain\Fileserver1''/><FileServer Name=''EVSite\MyDomain\Fileserver2''/></FileServerList>

  2. Log on as the FSA Reporting user.
  3. Open a command prompt window and change directory to the folder that contains the trimming utility.
  4. Enter the following command to run the trimming utility, all on one line:

    FSAReporting_TrimData.bat "SQL_Server" "FSAReportingDB_name" trim_period ["server_list"]

    where:

    • SQL_Server is the name of the SQL Server where the FSA Reporting database is located. Include the SQL Server instance name if appropriate, for example SQLServer1\instance1.

    • FSAReporting_db is the name of the FSA Reporting database that you want to trim.

    • trim_period is the period in days for which you want to retain data. Data older than the specified number of days is deleted.

    • server_list is the name of the XML file that specifies the list of servers. If you do not use an XML file, either specify ALL or omit the server_list variable, since the utility uses a value of ALL by default.

    Note that the parameters SQL_Server, FSAReporting_db, and server_list must be enclosed in double quotes.

    For example, the following command retains the last 30 days of data for all file servers whose data is saved in the database named FSAReporting1 on SQLServer1\instance1:

    FSAReporting_TrimData.bat "SQLServer1\instance1" "FSAReporting1" 30 "ALL"

    The following command retains the last 10 days of data for the file servers that are listed in the file fileserverlist.xml, in a database named FSARepDB that is located on SQLServer1:

    FSAReporting_TrimData.bat "SQLServer1" "FSARepDB" 10 "fileserverlist.xml"

  5. The utility logs its output to EV_FSAReporting_TrimOldData.log in the utility's folder. Examine this log file to check the results of running the utility.