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 File Blocking
The File Blocking feature for Windows file servers and NetApp filers prevents unwanted file types from being saved on monitored server volumes. File Blocking can be performed independently from archiving: a File System Archiving task can also process the volumes, but there is no requirement to do this.
You configure File Blocking at the volume level, by applying a volume policy in which you have defined File Blocking rules. The File Blocking rules determine the following:
Which files are blocked or allowed.
Which folders to monitor, or to ignore.
The actions to take when a policy violation occurs. For example, you can allow a file to be created, but send a warning message to the user and log an event in the event log.
The File Blocking rules enable you to block files according to:
File type. Inappropriate file types can be blocked immediately.
Content. Content-checking enables you to trap files that have been renamed to disguise their file types. File Blocking quarantines those files that are blocked as a result of content-checking. 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.
If required, you can edit the properties of the target file server to define a list of users whose files are never blocked.
The File Blocking rule enables you to configure a notification to send when the rule is broken. The following notification types are available:
Messenger Service messages (NET SEND)
Event log entries
Email
SNMP traps
More Information