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 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
Troubleshooting the configuration of FSA with clustered file servers
If you experience problems when you configure FSA clusters, try the following troubleshooting steps.
To troubleshoot the configuration of FSA with clustered file servers
- Verify that you have installed and configured the FSA services on each node to which the cluster group can fail over.
- Ensure that the ClusSvc service (for Windows Server Failover Clustering) or Had service (for Veritas Cluster Server) is configured and running on the file server.
- Check the log files. The FSA Cluster Configuration wizard stores details of the changes that it has made in the file
FSACluster.log
, which is located in the\Utilities\FSA Cluster
subfolder of the Enterprise Vault program folder (for example,C:\Program Files (x86)\Enterprise Vault
).The wizard creates additional log files on the individual cluster nodes when you configure a group for FSA services high availability. These log files are named
FSA-MSCSType.log
orFSA-VCSType.log
, depending on whether you are using Windows Server Failover Clustering or Veritas Cluster Server, and they are stored in the FSA Agent installation folder.The LogLevel registry value determines the level of logging. This registry value is located under the following registry key:
On a 32-bit installation of Windows:
HKEY_LOCAL_MACHINE \SOFTWARE \KVS \Enterprise Vault \FSA
On a 64-bit installation of Windows:
HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault \FSA
LogLevel can have a value in the range 0 through 5, where 0 or 1 records critical messages only, whereas 5 records debug and diagnostic messages.
- You can run DTrace on the FSA Cluster Configuration wizard - on the Enterprise Vault server that hosts the Enterprise Vault Administration Console, run DTrace on FSAClusterWizard.
You can also run DTrace on the FSA cluster node - on the FSA cluster node where the FSA resource is online, run DTrace on FSAClusterAssist and the Placeholder service.
If the DTrace view command does not include FSAClusterWizard or FSAClusterAssist in the list of processes that are available to monitor, register the file with DTrace as follows:
Enter the following command from DTrace:
set FSAClusterWizard.exe
or
set FSAClusterAssist.exe
Then register the name when DTrace prompts you.
For more information on DTrace, see the Utilities guide.