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 adding target volumes, target folders, and archive points for FSA
You must add shares on a target file server as target volumes for FSA to process. You can use the New Volume wizard or the New-EVFSAVolume PowerShell cmdlet to add a volume.
When you add a target volume, you can specify the following:
The vault store to use for the files that are archived from the volume.
The File System Archiving task to use to process the volume.
The volume policy to apply when files are archived from the volume.
If FSA Reporting is configured, the New Volume wizard also lets you choose whether to enable FSA Reporting for this volume. For information on FSA Reporting, see the Reporting guide.
After you add a target volume you must add one or more target folders to control which folders FSA can archive from. You can use the New Folder wizard or the New-EVFSAFolder PowerShell cmdlet to add a folder.
When you add a target folder the New Folder wizard lets you do the following:
Specify the archiving policy to use for the target folder and its subfolders.
Create an archive point for the folder, and for each of its immediate subfolders, if required. Each archive point defines the top of a folder structure that Enterprise Vault archives within a single archive.
To create an archive point at the root of a target volume you can specify a backslash ( \ ) as the path to the target folder when you add the target folder.
If you want, you can choose to auto-enable the creation of archive points on the immediate subfolders of a target folder. The target folder is then referred to as an . When the File System Archiving task runs in normal mode it creates archive points for any new subfolders that are immediately below the auto-enabling folder. Auto-enabling can be useful for example when a target folder contains a subfolder for each user, and you want a separate archive for each user. When you add a subfolder for a new user, the File System Arching task creates an archive point on the subfolder during the next normal archiving run.
To ensure that an archive does not fill up too quickly you need to consider the size of the folder structure below each archive point.
When an archive point is created, it has no archive ID immediately assigned to it. An archive ID is normally assigned on the first occasion that a File System Archiving task processes the folder. When a File System Archiving task finds an archive point with no archive ID or an invalid archive ID it checks the Directory database to determine whether any archive IDs are already associated with the folder path. If the folder path has no associated archive IDs, Enterprise Vault creates an archive and assigns the archive ID to the archive point. If one or more archives already exist for the folder path, Enterprise Vault assigns the oldest existing archive to the archive point. In the case where multiple archives exist for a folder path, Enterprise Vault reports this fact.
See About the checks for existing archives for an FSA folder path.
By default the File System Archiving task gives an archive the same name as the folder to which the archive point applies. The site defaults are used to supply the other attributes of the archive. You can override these defaults if you want.