Veritas Enterprise Vault™ Setting up File System Archiving (FSA)
- About this guide
- About File System Archiving
- About FSA shortcut files
- Steps to configure File System Archiving
- Adding a Windows file server to File System Archiving
- About archiving from Windows Server 2012 file servers
- Permissions and privileges required by the Vault Service account on Windows file servers
- Adding a NetApp filer to File System Archiving
- Adding a NetApp C-Mode Vserver to File System Archiving
- Adding an EMC Celerra/VNX device to File System Archiving
- Configuring FSA with clustered file servers
- Troubleshooting the configuration of FSA with clustered file servers
- Installing the FSA Agent
- Defining volume and folder policies
- About selecting the shortcut type for an FSA policy
- About FSA policy archiving rules
- Configuring the deletion of archived files on placeholder deletion
- Configuring target volumes, target folders, and archive points
- About adding target volumes, target folders, and archive points for FSA
- About managing archive points
- Archive point properties
- Effects of modifying, moving, or deleting folders
- About deleting target folders, volumes, and file servers
- Configuring pass-through recall for placeholder shortcuts
- Configuring and managing retention folders
- Configuring File Blocking
- About File Blocking rules
- Configuring and running FSA tasks
- Using Run Now to process FSA targets manually
- Configuring file system filtering
- Managing the file servers
- PowerShell cmdlets for File System Archiving
- Appendix A. Permissions and privileges required for the Vault Service account on Windows file servers
- Permissions required by the Vault Service account for the FSA Agent
About configuring File Blocking
You can configure File Blocking for the following devices:
Windows computers. File Blocking is carried out by a File Blocking service that is installed on the Windows computer as part of the FSA Agent.
NetApp filers with Data ONTAP 8.0 or later, and Data ONTAP 8.2 (C-Mode) and Data ONTAP 8.3 (C-Mode). The File Blocking is carried out by a File Blocking service that runs on a Windows file server. When you configure File Blocking for a NetApp filer you must select a target Windows file server to perform the File Blocking. It is possible for a Windows file server to run File Blocking for more than one NetApp filer, but for best performance you are recommended to use a different Windows file server for each NetApp filer.
Note:
To use File Blocking on NetApp C-Mode Vservers, you must have the Enterprise Vault 11.0.1 or later FSA Agent installed. Enterprise Vault 12.1 supports the configuration of the data and management roles on separate LIFs. To use File Blocking on such NetApp C-Mode Vservers, you must have the Enterprise Vault 12.1 or later FSA Agent installed.
File Blocking quarantines those files that are blocked because of content-checking. As part of configuring File Blocking you must create quarantine locations as follows:
You must create a local quarantine location for each file server. For NetApp filers, the local quarantine location must be on the Windows file server that runs the File Blocking service for the NetApp filer.
Optionally you can define a central quarantine location. Enterprise Vault then uses the central quarantine unless the central quarantine location is not available. If the central quarantine location is not defined or is not available, Enterprise Vault uses the file server's local quarantine location.
Note that if the central quarantine location later becomes available, the files that are in local quarantine locations are not automatically moved to the central quarantine location.
If neither a central quarantine location nor the local quarantine location is available, Enterprise Vault logs an error in the event log, and the file is not quarantined.