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 File System Archiving task reports
A File System Archiving task can create reports for the following:
Archiving runs
File version pruning runs
Runs to delete archived Celerra/VNX files whose placeholders have been deleted
For archiving runs and file version pruning runs you can use the settings on the Reports tab of the File System Archiving task's properties to control the logging level and the number of reports to keep.
You can also use the options in the list of File System Archiving settings on the Advanced tab of the site properties to control how you want Enterprise Vault to store and retain reports. You can choose whether to retain the report files on the server for a specific number of days, set a new location to store the reports, and configure a rollover size for each report file.
The reports are generated in the following places under the Enterprise Vault installation folder:
Reports for pruning runs and Celerra/VNX file deletion runs are generated in the
Reports
subfolder.Reports for archiving runs are generated in the
Reports\FSA
subfolder.
Within Reports\FSA
there is a subfolder for the task, with further subfolders to indicate the mode in which the task was run.
You can change the location of the reports by editing Location of the report in the list of File System Archiving settings on the Advanced tab of the site properties.
Until the task has finished processing all its targets, the task keeps the reports in a folder that is called InProgress
. When the task has finished processing, it moves the reports to a subfolder that is underneath the Completed
folder. The subfolder name is the date and time that task completed its processing.
For example, if task 'ArchiveTask1' is running in normal, scheduled mode, but has not finished processing, the report files could be in the following folder:
C:\Program Files (x86)\Enterprise Vault\Reports\FSA\ArchiveTask1\ArchiveScheduled\InProgress
If task 'ArchiveTask1' completes its processing on 20-Feb-2011 at 12:29.07, the report files are moved to the following folder:
C:\Program Files (x86)\Enterprise Vault\Reports\FSA\ArchiveTask1\ArchiveScheduled\Completed\2011-02-20 12-29-07
Table: File System Archiving task archiving run modes and their associated folder names lists the folder names that are used for the different archiving run modes.
Table: File System Archiving task archiving run modes and their associated folder names
Run mode | Folder name |
---|---|
Normal, Scheduled | ArchiveScheduled |
Normal, Run Now | ArchiveRunNow |
Normal, Run Now, Create shortcuts only | ArchiveRunNowCreateShortcuts |
Report, Scheduled | ReportScheduled |
Report, Run Now | ReportRunNow |
Report, Run Now, Create shortcuts only | ReportRunNowCreateShortcuts |
The report files are named as follows:
TaskName_RunMode_RunNumber.txt
Where:
TaskName is the name of the File System Archiving task.
RunMode is the mode in which the task was run.
RunNumber is the sequence number of the run.
It may take many runs before the File System Archiving task has completely processed its target volumes. The task creates a report file for each run. The report for the final run has '_FINAL' added to the name to indicate that processing is complete.
For example, if 'ArchiveTask1' processes according to its schedule, in normal mode, the file names of successive reports could be as follows:
ArchiveTask1_ArchiveScheduled_001.txt ArchiveTask1_ArchiveScheduled_002.txt ArchiveTask1_ArchiveScheduled_003_FINAL.txt
When custom filters are configured for File System Archiving, report files include information about the filters and the files that the filters have processed.
When a File System Archiving task processes a folder that has an archive point with no archive ID or an invalid archive ID, Enterprise Vault performs a check for existing archives for the folder path. If the check identifies that multiple archive IDs are associated with the folder path, the task report lists the archive ID of each archive that is associated with the folder path, and indicates which archive will be used for archiving.