Enterprise Vault™ Reporting

Last Published:
Product(s): Enterprise Vault (15.0)
  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 a 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 Dell 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.  
        SMTP Provisioning report
      21.  
        Vault Store Savesets report
      22.  
        Vault Store Usage by Archive report
      23.  
        Vault Store Usage by Billing Account report
      24.  
        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

About the FSA Reporting databases

An FSA Reporting database holds the FSA Reporting scan data for one or more file servers. FSA Reporting requires at least one FSA Reporting database per Directory database.

When you configure a file server for FSA Reporting, Enterprise Vault does as follows:

  • If there are no FSA Reporting databases associated with the Directory database, a wizard helps you to create an FSA Reporting database.

  • If at least one FSA Reporting database is already associated with the Directory database, Enterprise Vault gives you the following options:

    • Select an existing FSA Reporting database to hold the file server's data.

    • Create a new FSA Reporting database to hold the file server's data.

You can choose the name for each FSA Reporting database. The name must contain only alphanumeric characters and spaces. The name can be up to 25 characters long.

Multiple FSA Reporting databases provide the following benefits:

  • Multiple databases provide scalability. FSA Reporting can upload the data faster from multiple file servers to multiple databases, which can significantly reduce scan times.

  • Multiple databases let you segregate information, for example by geographical location.

A minor disadvantage of multiple FSA Reporting databases is that summary reports take longer to generate, because Microsoft SQL Server Reporting Services must gather the data from multiple databases.

When you assign FSA Reporting databases to your target file servers, take into account the following factors:

  • Where possible, assign to different databases the file servers with the most volumes that are enabled for FSA Reporting. The amount of data that FSA Reporting must upload from the scan of a file server increases with the number of archive points and volumes that require scanning.

  • A data upload bottleneck can result if you assign to the same database many file servers that have the same FSA Reporting scan schedule. Assign the file servers that have the same scan schedule to different FSA Reporting databases. Stagger the FSA Reporting scan schedules for the file servers that are assigned to the same FSA Reporting database.

You must maintain each FSA Reporting database to ensure that it does not become too large.

See About maintaining the FSA Reporting databases.