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
Granting the required permission on each Vserver
Before you add a NetApp C-Mode Vserver as an FSA target, you need to grant permission to a domain user to register the FPolicy on the Vserver.
You can configure only one user account per Enterprise Vault site for all the Vservers. If you change the user account details, you must ensure that this user has ONTAPI permissions on all the Vservers. Refer to the NetApp documentation for more information.
Note:
Ensure that you use a user account other than the Vault Service account to grant ONTAPI permissions to.
To grant the required permission on the Vserver
- Log on to the cluster console as a cluster administrator.
- To create a role with specific privileges on the NetApp Vserver, type the following commands at the command prompt:
security login role create -role rolename -vserver vservername -cmddirname "vserver cifs" -access all
security login role create -role rolename -vserver vservername -cmddirname "vserver cifs share" -access all
security login role create -role rolename -vserver vservername -cmddirname "volume" -access all
security login role create -role rolename -vserver vservername -cmddirname "vserver fpolicy" -access all
security login role create -role rolename -vserver vservername -cmddirname "version" -access all
security login role create -role rolename -vserver vservername -cmddirname "network interface" -access readonly
security login role create -role rolename -vserver vservername -cmddirname "vserver fpolicy enable" -access all
security login role create -role rolename -vserver vservername -cmddirname "vserver fpolicy disable" -access all
security login role create -role rolename -vserver vservername -cmddirname "vserver fpolicy policy" -access all
security login role create -role rolename -vserver vservername -cmddirname "vserver " -access readonly
Where:
rolename is the name of the new role that you want to create and assign the specified privileges to.
vservername is the name of the Vserver.
- To grant the new role to a domain user, type the following at the command prompt:
security login create -vserver vservername -username DomainName\UserName -application ontapi -authmethod domain rolename
Where:
vservername is the name of the Vserver.
-usernameis DomainName\UserName, where DomainName is the Active Directory domain of the user account.
Note:
The value that is specified in -username is case-sensitive.
rolename is the name of the role that you created in the previous step.