Veritas Enterprise Vault™ Introduction and Planning
- About this guide
- Introduction
- Overview of Enterprise Vault
- How Enterprise Vault works
- About Enterprise Vault indexing
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Enterprise Vault Outlook Add-In
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server archiving
- Exchange Public Folder archiving
- File System Archiving
- File Blocking with File System Archiving
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Enterprise Vault Accelerators
- About Compliance Accelerator
- About Discovery Accelerator
- Building in resilience
- Planning component installation
- Where to set up the Enterprise Vault Services and Tasks
- Installation planning for client components
- Planning your archiving strategy
- How to define your archiving policy for user mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan settings for retention categories
- How to plan vault stores and partitions
- About Enterprise Vault reports
File Blocking with File System Archiving
File Blocking monitors disk space in real time, according to the requirements that you define in a volume policy. File Blocking rules enable you to block files as follows:
By file type. Inappropriate file types are blocked immediately.
By scanning file content. This enables you to trap files that have been renamed to disguise their file types.
Additionally, it is possible to scan the contents of compressed files, such as ZIP files.
Note:
Files stored within .RAR and .CAB files cannot be blocked or quarantined. However, you can create rules to block .RAR and .CAB files.
You can also control monitoring as follows:
The volume policy enables you to specify folders that must not be monitored and folders that must be monitored.
You can edit the properties of a file server to define a list of users whose files are never blocked.
You can enable, for each file server, a quarantine location for blocked files. Files that are blocked as a result of content-scanning are moved automatically to the quarantine location. Files that are blocked because of their file type are never moved to quarantine. Optionally, you can define a central quarantine location that is used by all file servers.
Within a policy you can have many different rules. Each rule enables you to configure notifications that are sent when that rule is broken.