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
The format of the Web Access application URL in the Celerra/VNX fs_dhsm command
When you configure the Celerra/VNX connection to use for FSA recall requests, one of the required parameters to the fs_dhsm command is:
-secondary ev_url
Where ev_url is the URL of the Enterprise Vault Web Access application.
The format of ev_url is as follows:
https://server_name/EnterpriseVault
Where server_name is the name of the Enterprise Vault server that hosts the Storage service for the Celerra/VNX archiving target, as specified in the ComputerEntryTable of the Directory database. This name is the same as the display name of the Enterprise Vault server in the Administration Console.
You can determine the server_name from the Administration Console as follows:
In the Administration Console, expand under the site container in the left pane.
Identify the Enterprise Vault server that hosts the Storage service for the Celerra/VNX archiving target.
server_name is the display name of the Enterprise Vault server as shown under the node. For example, if the file server name is shown as , then server_name is .
The Celerra/VNX is case-sensitive, so make sure that you supply the URL in the correct case.
Note:
If the Celerra/VNX fails to find a connection with the server name that you specify in the URL, the files are archived but no placeholders are created. The File System Archiving task report's "Shortcut status" column then shows the error "NO_MATCHING_CONNECTION".
You cannot include a port number in the URL. For example, if you use a non-default port such as port 8080 for the Web Access application, do not attempt to specify the port as follows:
-secondary http://evserver.demo.local:8080/EnterpriseVault
If you attempt to include a port number, the fs_dhsm -connection command fails with a message similar to the following, and the archiving and recall of files on the Celerra/VNX will fail:
Error: The host name in the secondary url evserver.demo.local:8080 is either missing or formatted incorrectly.
If the Web Access application uses a port other than the default port (port 80 for HTTP, or port 443 for HTTPS), use the -httpport or -httpsport parameter of the fs_dhsm command to specify the port number.