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
- Adding a Dell EMC Unity 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
About pass-through recall for placeholder shortcuts
You can configure the pass-through recall of placeholder shortcuts on Windows file servers, and for read-only file systems on NetApp filers that run Data ONTAP 8.0 or later. For Dell EMC Celerra/VNX devices, Enterprise Vault supports the Celerra/VNX pass-through facility.
Note:
Due to a NetApp restriction, pass-through is not supported for Data ONTAP 8.2 C-Mode.
If pass-through recall is configured, then on receipt of a read request for a placeholder Enterprise Vault passes the data directly through to the calling application. Enterprise Vault recalls the file to the file server, subject to permissions, only if the calling application makes a write request: for example if the application requires a writeable file, or if the user attempts to save changes to a file.
Note:
Some applications such as Excel always recall to disk even when pass-through recall is enabled.
Pass-through recall can be useful in the following circumstances:
With placeholders on read-only file systems, such as snapshots. A normal placeholder recall to a read-only file system fails because Enterprise Vault cannot write the recalled file to the file system.
With Windows file servers when there is limited space on the file server, or when users have strict quotas for space usage. Recalled files normally occupy space on the target file system, and therefore count towards a user's space quota.
Pass-through recall uses a disk cache to reduce recall times for large files. For Windows file servers the disk cache is located on the file server. For NetApp filers the disk cache is located on the Enterprise Vault server.
For Windows file servers you can enable or disable pass-through recall for each target volume.