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 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 or later 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 a 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 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 Dell 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
 
 
Configuring Celerra/VNX pass-through behavior for placeholder shortcuts
You can use the Dell EMC Celerra/VNX read policy override with placeholder recalls, if required. The Celerra/VNX -read_policy_override parameter determines how a read request is handled for a file in secondary storage. For example, you can opt to pass a file directly through to the client without recalling it to the Celerra/VNX. The Celerra/VNX Network Server then recalls the file only if a write request is received.
For pass-through, the Celerra/VNX uses the same cache on the Enterprise Vault server that you set up for Enterprise Vault to use when retrieving files for the Celerra/VNX.
Note:
If you configure Celerra/VNX pass-through, do not configure the Enterprise Vault option to delete archived files on placeholder deletion, as this combination can lead to data loss.
To configure the Celerra/VNX pass-through behavior, include the -read_policy_override parameter in one of the following commands:
The fs_dhsm -connection command to define the HTTP or HTTPS connection that the Celerra/VNX uses for recall requests. This method sets the pass-through behavior for all the placeholders that are created through the connection.
The fs_dhsm -modify command to configure a Celerra/VNX file system. This method sets the pass-through behavior for all the placeholders on the file system.
The syntax of the -read_policy_override parameter is as follows:
-read_policy_override [none | full | passthrough | partial]
The effect of the values is as follows:
none (the default value). The setting has no effect.
full. Recall the whole file to the Celerra/VNX on read request before the data is returned.
passthrough. Retrieve the data without recalling the data to the Celerra/VNX.
partial. Retrieve only the blocks that are required to satisfy the client read request.
Note the following:
If you do not set a read policy override for either the file system or the connection, the Celerra/VNX uses a value of passthrough by default.
The Celerra/VNX uses a value of passthrough if the Celerra/VNX file system is read only.
The Celerra/VNX uses a value of passthrough if attempts to recall data produce an error that is due to insufficient space or quotas.
For example, the following command syntax configures pass-through for a file system:
fs_dhsm -modify fs_name -read_policy_override passthrough
Where fs_name is the name of the file system on the Celerra/VNX.