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 4.3 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 archiving Windows Server 2012 and later deduplicated files with FSA
Windows Server 2012 and later include a file-level data deduplication mechanism.
By default, FSA archives the deduplicated files. Options on the Archiving Rules tab and the Shortcuts tab of the Enterprise Vault FSA Volume policies and Folder policies enable you to turn off archiving or shortcut creation for Windows deduplicated files, if you want.
If you decide to turn off archiving or shortcut creation for the deduplicated files, bear in mind that Windows does not deduplicate files immediately. Enterprise Vault applies the deduplicated file policy settings to a file only if the file is in a deduplicated state when Enterprise Vault assesses it for archiving or for shortcut creation. The order of events can lead to different archiving outcomes. For example, suppose that you set the policy options for deduplicated files as follows:
[ Selected ] | Do not archive deduplicated files on Windows Server 2012 and later. |
[ Unselected ] | Do not create shortcuts for deduplicated files on Windows Server 2012 and later. |
The following scenario may then occur:
Enterprise Vault archives a file before Windows has deduplicated it. Since the file is not in a deduplicated state when Enterprise Vault assesses it, the policy setting for archiving the deduplicated files is not considered.
While the file awaits shortcut creation on the file server, Windows deduplicates it.
Enterprise Vault then creates a shortcut for the file, adhering to the policy setting for creating shortcuts for deduplicated files.
The same policy settings can have different results if the deduplicated file is modified before Enterprise Vault creates a shortcut for it. Once Windows has deduplicated the file, Enterprise Vault does not rearchive it, because of the policy setting for deduplicated files. Enterprise Vault does not create a shortcut for the modified file, because for shortcut creation Enterprise Vault requires the latest version of the file to be in the archive.