Enterprise Vault™ Setting up File System Archiving (FSA)
- About this guide
- About File System Archiving
- About FSA shortcut files
- Steps to configure File System Archiving
- Adding a Windows file server to File System Archiving
- About archiving from Windows Server 2012 or later file servers
- Permissions and privileges required by the Vault Service account on Windows file servers
- Adding a NetApp filer to File System Archiving
- Adding a NetApp C-Mode Vserver to File System Archiving
- 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
- Troubleshooting the configuration of FSA with clustered file servers
- Installing the FSA Agent
- Defining volume and folder policies
- About selecting the shortcut type for an FSA policy
- About FSA policy archiving rules
- 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
- 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
- Using Run Now to process FSA targets manually
- 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
- Permissions required by the Vault Service account for the FSA Agent
About the checks for existing archives for an FSA folder path
Under some circumstances an FSA folder path can become associated with more than one archive.
When a File System Archiving task processes a folder that has an archive point with no archive ID or an invalid archive ID, it checks the Directory database records to determine whether any archive IDs are already associated with the folder path. It then proceeds as follows:
If no archive ID is associated with the folder path, Enterprise Vault creates an archive and assigns the archive ID to the archive point.
If one archive ID is associated with the folder path, Enterprise Vault assigns that archive ID to the archive point.
If more than one archive ID is associated with the folder path, Enterprise Vault does the following:
Assigns the archive ID of the oldest existing archive to the archive point.
Indicates the existence of multiple archives for the folder path in the File System Archiving task report. The report lists the archive IDs of the multiple archives, and indicates that the oldest archive will be used for archiving.
Generates a warning event with event ID 41484 in the Enterprise Vault event log. The event lists the archive IDs of the multiple archives for the folder path, and indicates that the oldest archive will be used for archiving.
After Enterprise Vault has assigned an archive ID to the archive point, no further warnings are issued about the existence of multiple archives for the folder path.
Note:
When Enterprise Vault checks for existing archives for a folder path, the check is restricted to the records from vault stores that belong to the Enterprise Vault storage server that hosts the vault store for the target volume.