Veritas Enterprise Vault™ Setting up File System Archiving (FSA)
- About this guide
- About File System Archiving
- About File System Archiving
- About using FSA with clustered file servers
- About setting up File System Archiving
- About FSA policies
- About target volumes, folders, and archive points
- About client access to FSA-archived items
- About archived file permissions
- About FSA shortcut files
- About the FSA Agent
- About retention folders
- About File Blocking
- About FSA Reporting
- About FSAUtility
- Steps to configure File System Archiving
- Adding a Windows file server to File System Archiving
- Adding a Windows file server to File System Archiving
- Using FSA with the Windows Encrypting File System (EFS)
- About archiving from Windows Server 2012 file servers
- Account requirements for managing FSA with Windows file servers
- Permissions and privileges required by the Vault Service account on Windows file servers
- Configuring a file server's firewall for FSA
- Adding a Windows file server as an archiving target
- Adding a NetApp filer to File System Archiving
- Adding a NetApp C-Mode Vserver to File System Archiving
- Adding a NetApp C-Mode Vserver to File System Archiving
- Permissions and privileges required by the Vault Service account on NetApp C-mode Vservers
- Granting the required permission on each Vserver
- Configuring the FPolicy server details
- Adding a NetApp C-Mode Vserver as an archiving target
- Points to note about File System Archiving on NetApp C-Mode file servers
- Adding an EMC Celerra/VNX device to File System Archiving
- Configuring FSA with clustered file servers
- About configuring FSA with clustered file servers
- Steps to configure FSA with clustered file servers
- Preparing to set up FSA services in a cluster
- Adding the Vault Service account to the non-secure VCS cluster for FSA high availability
- Adding the virtual file server as an FSA target
- Configuring or reconfiguring the FSA resource
- Removing the FSA resource from all cluster groups
- Troubleshooting the configuration of FSA with clustered file servers
- Installing the FSA Agent
- Defining volume and folder policies
- About defining FSA volume and folder policies
- Creating FSA volume policies and folder policies
- About FSA volume policy and folder policy properties
- About selecting the shortcut type for an FSA policy
- About FSA policy archiving rules
- About options for archiving files that have explicit permissions, and files under DAC
- 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
- Adding a target volume for FSA
- Adding a target folder 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 configuring File Blocking
- Steps to configure File Blocking
- Defining a local quarantine location for File Blocking
- Defining a central quarantine location for File Blocking
- Specifying the mail notification delivery mechanism for File Blocking
- Including File Blocking rules in a policy
- About File Blocking rules
- Exempting File Blocking for specific users
- Troubleshooting File Blocking in a clustered environment
- Configuring and running FSA tasks
- About configuring and running FSA tasks
- Adding a File System Archiving task
- Scheduling a File System Archiving task
- Setting the FSA folder permissions synchronization schedule
- Scheduling the deletion of archived files on placeholder deletion for EMC Celerra/VNX
- Configuring FSA version pruning
- Using Run Now to process FSA targets manually
- About File System Archiving task reports
- About scheduling storage expiry for FSA
- 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
- About the permissions and privileges required for the Vault Service account on Windows file servers
- Group membership requirements for the Vault Service account
- DCOM permissions required by the Vault Service account
- WMI control permissions required by the Vault Service account
- Local security user rights required by the Vault Service account
- Permissions required by the Vault Service account for the FSA Agent
- Permissions required by the Vault Service account to support the FSA resource on clustered file servers
- FSA target share and folder permissions required by the Vault Service account
File Blocking rule: Notification message variables
You can insert variable information into a File Blocking notification message, such as the path to the file that was blocked. The variables are replaced with the details that are current at the time the message is sent.
Table: Notification variables describes the variables that you can use.
Table: Notification variables
Variable name | Description |
|---|---|
[USER] | Current user who caused the action. Includes domain information. |
[USER NO DOMAIN] | Current user who caused the action without the domain information. |
[USER MAIL ID] | Email ID of the user who caused the action. This ID is taken from Active Directory. Use this variable if the user's logon and email names might be different. |
[DOMAIN] | Domain name. |
[FILE SPEC] | File path and name that caused the action. |
[FILE NAME] | Name of the file that caused the action. |
[POLICY NAME] | Name of the policy that is applied to the managed resource. |
[OBJECT NAME] | Name of the resource that caused the action. |
[OWNER NO DOMAIN] | Name of the owner of the file that caused the action without domain information. |
[OWNER] | Name of the owner of the file that caused the action. Includes domain information. |
[SERVER NAME] | Name of the server where an alarm has been activated. |
[OBJECT NAME SHARE] | Shared name of the resource. For example, you can enter "H" as in "H:\MyDrive" and the share name is inserted. |