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
Installing the FSA Agent manually
Follow the procedure below to perform a manual installation of the FSA Agent and its prerequisites on a Windows server.
The FSA Agent supports AMD64 and Intel EM64T, but it does not currently support Intel Itanium.
To install the FSA Agent manually
- Find the FSA Agent files on the Enterprise Vault server. The files are in the
evpush\Agentfolder under the Enterprise Vault installation folder; for example,C:\Program Files (x86)\Enterprise Vault\evpush\Agent. Install the required Microsoft Visual C++ redistributable packages on the file server:
vcredist_x86.exevcredist_x64.exe
- Copy the
Enterprise Vault File System Archiving x64.msifile to the file server. - Log on to the file server with an account that is a member of the local Administrators group on the file server.
- For example, the following command performs a silent installation of the FSA Agent:
Perform an interactive installation or silent installation of the FSA Agent. With a silent installation, no notification messages appear on the console.
To perform an interactive installation, double-click the MSI file, or open a Command Prompt window and enter a command similar to the following:
msiexec.exe /i path_to_.msi_file /L*v logfilenameThe installer prompts you to specify the installation folder and the credentials of the user account that will log on to use this application. You must specify the name and password of the Vault Service account. The installer uses these credentials to configure the FSA services.
If you used an msiexec.exe command, any installation messages appear in the specified log file.
To perform a silent installation, open a Command Prompt window and enter a command similar to the following:
msiexec.exe /i path_to_.msi_file /L*v logfilename [INSTALLDIR=installpath] IS_NET_API_LOGON_USERNAME=Domain\Username IS_NET_API_LOGON_PASSWORD=password /qAny installation messages appear in the log file specified. Note that the logon user name must be the Vault Service account in the format Domain\Username.
You can use INSTALLDIR to specify an installation location other than the default path on the system drive, if required.
msiexec.exe /i "C:\TEMP\FSA\Agent\Enterprise Vault File System Archiving x64.msi" /L*v fsainstall.log IS_NET_API_LOGON_USERNAME=DOMAIN1\VSA IS_NET_API_LOGON_PASSWORD=Ev@ult-723 /q
When the installation of the FSA Agent is complete, start the following services from the Windows Services MMC snap-in, if they are not already started:
Enterprise Vault File Collector service
Enterprise Vault File Placeholder service