Enterprise Vault™ Introduction and Planning
- About this guide
- Introduction
- Overview of Enterprise Vault
- How Enterprise Vault works
- About single instance storage
- About Enterprise Vault indexing
- About Index Server groups
- About Enterprise Vault Administration Console
- About Enterprise Vault sites, Directory, and Directory database
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Enterprise Vault Outlook Add-In
- About IMAP access to Enterprise Vault archives
- About the Enterprise Vault Client for Mac OS X
- About Microsoft Exchange forms
- About OWA Extensions
- About the Office Mail App for OWA 2013 and later and Outlook 2013 and later
- About Enterprise Vault extensions for Notes
- About Enterprise Vault Search
- About Enterprise Vault monitoring and reporting
- FIPS 140-2 compliance
- Enterprise Vault administration
- About Enterprise Vault administration
- Administration Console configuration of archiving
- Administration accounts and roles
- How to archive PST file contents
- How to archive NSF file contents
- How to export archived items
- Welcome message and other notifications
- About reporting and monitoring in Enterprise Vault
- How to script management tasks
- Checklist of day-to-day management tasks
- Exchange Server archiving
- Exchange Public Folder archiving
- File System Archiving
- About File System Archiving
- About File archiving policies
- About shortcut files with File System Archiving
- About setting up File System Archiving
- File System Archiving in a clustered environment
- The process of File System Archiving
- How File System Archiving handles older versions of archived files
- How File System Archiving synchronizes permissions
- File System Archiving reports
- How to restore files with File System Archiving
- About FSAUtility
- How to back up and scan shortcut files with File System Archiving
- Pass-through recall for placeholder shortcuts with File System Archiving
- Retention Folders and File System Archiving
- FSA Reporting
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Skype for Business Archiving
- Enterprise Vault Accelerators
- About the Enterprise Vault Accelerators
- Differences between the Enterprise Vault Accelerators
- About Compliance Accelerator
- About Discovery Accelerator
- Building in resilience
- Planning component installation
- About planning component installation
- About valid computer names for Enterprise Vault servers
- Prerequisites for Enterprise Vault components when planning installation
- Factors to consider when planning deployment of Enterprise Vault components
- Enterprise Vault Directory Service installation planning
- Where to set up the Enterprise Vault Services and Tasks
- How to plan installing Exchange Mailbox Archiving Tasks
- How to plan installing Exchange Journaling Tasks
- How to plan installing Exchange Public Folder Tasks
- How to plan installing Domino Journaling and Mailbox Archiving Tasks
- How to plan installing the Move Archive task
- How to plan installing the Storage Service
- How to plan installing the Indexing Service
- How to plan installing the Shopping Service
- How to plan installing File System Archiving
- How to plan installing SharePoint Archiving
- How to plan installing SMTP Archiving
- How to plan installing Accelerator Services
- Enterprise Vault databases and planning their installation
- Vault store groups and vault stores installation planning
- Administration Console installation
- Installation planning for client components
- Planning your archiving strategy
- About archiving strategies
- Where to define default settings for the Enterprise Vault Site
- How to allow users flexibility
- How to plan the types of items to archive
- How to define your archiving policy for user mailboxes
- How to plan the archiving policy for journal mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan an archiving strategy for FSA
- How to plan a strategy for SharePoint archiving
- How to plan settings for retention categories
- How to plan the automatic deletion of archived items
- How to plan PST migration
- How to plan NSF migration
- How to plan shared archives
- How to plan vault stores and partitions
- How to plan single instance storage
- About Enterprise Vault reports
FSA Reporting
FSA Reporting provides summary reports on the active data on your file servers, and on the data that has been archived from them. FSA Reporting's reports include data on a wide range of items including the following:
The number of archived files for each file server, and the space used and saved as a result of archiving. You can also view the 10 largest files in a volume.
Active and archived space usage by different file groups, per server and per archive point.
Numbers of unaccessed or duplicated files, and the space they are occupying.
Used and free space on the drives of each file server.
Many of the reports can provide either an overall view for all file servers with FSA Reporting configured, or a detailed view for a named file server.
In order to access FSA Reporting's reports, the Enterprise Vault Reporting component must be installed and configured on a computer with the required prerequisites, including Microsoft SQL Server Reporting Services. You use the SQL Server Reporting Services Report Manager web application to view the reports.
You must also configure FSA Reporting for each file server target for which you want to obtain reports. The Administration Console provides wizards to help you do the following:
The first time that you configure a file server target for FSA Reporting, a wizard helps you to set up an FSA Reporting database to hold the FSA Reporting scan data.
When you configure another file server target for FSA Reporting, you can assign the file server to an existing FSA Reporting database, or create another database. Multiple FSA Reporting databases can provide scalability if you obtain FSA Reporting data for many file servers.
For a Windows file server, install the FSA Agent on the file server if the agent is not already present
For a non-Windows file server, that is NetApp Filers and Dell EMC Celerra/VNX devices, select another server to act as the FSA Reporting proxy server. The FSA Reporting proxy server gathers the FSA Reporting data for one or more non-Windows file servers.
Any of the following can act as an FSA Reporting proxy server, subject to some additional prerequisites:
An Enterprise Vault server in the Enterprise Vault site.
A Windows server that is configured as a file server archiving target in the Enterprise Vault site.
A Windows server on the network.
Note:
To enable FSA Reporting on NetApp C-Mode filers, you must have the Enterprise Vault 11.0.1 or later FSA Agent installed.
For more information, see the Reporting guide.