How to configure Network File System (NFS) for backup on RSA Authentication Manager 8.x; error "failed to validate the remote share location"
Originally Published: 2015-01-06
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
Resolution
1. Create a directory anywhere on the file system. In the following example the backup directory will be at the root level of the drive (/) and created with the root user. After creating the directory, chmod the permissions. The backup folder must have read, write and execute permissions, else the validation to the share will fail. Case sensitivity needs to be noted here. If you setup a share on the RHEL server called Backups, then when configuring the share name in the Operations Console GUI, the share name must be Backups, not backups.
-bash-3.00$ pwd / -bash-3.00$ mkdir Backups -bash-3.00$ chmod 777 Backups
2. Make a copy of the original /etc/exports file
-bash-3.00$ cp /etc/exports /etc/exports.bak -bash-3.00$ vi /etc/exports
3. Edit /etc/exports to add the following information: /<the_name_of_the_directory_created_in_step_1> <the_IP_address_of_the_primary_Authentication_Manager_server>n.n.n.n(rw,sync). For example,
/Backups 86.75.30.9(rw,sync)
.4. Reload the NFS configuration by running the command below. Every time a change is made to the /etc/exports file, this command must be run for the changes to take effect.
-bash-3.00$ /sbin/service nfs reload
.5. Check the NFS configuration with the command below, with expected output showing the IP address of the primary Authentication Manager server:
-bash-3.00$ exportfs -v /backups 86.75.30.9(rw,wdelay,root_squash,no_subtree_check)
Should there be syntax error(s) in the exports file, check the entry in the exports file and run through the configuration again.
How to setup NFS for backups with RSA Authentication Manager 8.x where the NFS is on Windows Server
In Windows Server machine
1. Make sure that File Services Server Role is installed and running. It can be created on Windows Server using Add Roles.
2. Configure a NFS share folder
Create a new folder for your NFS share. It can be done on default Windows Drive(C:)
Right-click the folder and click Properties.
Select the NFS Sharing tab.
Under the NFS Sharing tab, click the Manage NFS Sharing… button
Check the Share this folder check box.
Enter a name into the Share name text field. This will be used when a user connects to your NFS share.
Click the Permissions button.
Click Add and then enter the IP address or hostname of the client(s) you want to allow connections to. When added, select they have read write access. Check Allow root access box.
Click OK.
Click Apply and then OK.
3. Allow Group/Users to access NFS Shared Folder.
Right-click the folder and click Properties.
Select Security.
Click Edit... Button
Click Add.. Button
Enter 'Authenticated Users' in "Enter the object names to select" box and click on Check Names button
Once it is selected and highlighted, click OK.
Select "Authenticated Users" in Group or user names section and In Permission section select "Read & execute" and all below permissions.
click Apply and OK button.
In RSA AM Operations Console
4. In Back Up Now or Schedule Backups page, under Backup Location, make sure NFS(Network File System) shared Folder is selected.
5. Under NFS Shared Folder, enter
<NFS_Windows_Server_ip>:/NFS_Shared_Folder
Perform Backup Now or Schedule backup to make sure it backs up successfully.
Please note that 'Authenticated Users' group and 'Read & execute' permission is the least lower group and permission required Windows NFS to work with RSA Authentication Manager NFS backup.
Notes
NFS folder name - /backups/RSABackups
Permissions on /backups:
drw-rw-rw-. 3 root root 4.0K Dec 23 10:12 backupsPermissions on RSABackups should be as follows:
drwxrwxrwx. 2 root root 4.0K Dec 23 10:31 RSABackupWe need 'rw' and 'x' or the share will fail to validate the backup location. Also, the /etc/exports file should reflect the sub folder path.
NAS Storage Device Notes
The above permissions and notes should still apply if you are using a NAS device as they tend to be typically running Linux or Unix operating systems. In cases where you do not have direct access to the NAS operating system then speak with an administrator/operator for that product and refer them to the above information. They should be able to get the settings right on the NAS device so the backups are created and stored properly.
At the current time RSA Authentication Manager 8.1 does not support username/password for NFS server. That being said, access control is performed via an IP address, as noted above. We do have a feature request for enhancement (RFE) in place for using a username/password with NFS share usage for Authentication Manager backups.
NFS 3.0 supports access control via IP address.
Related Articles
Failed to validate remote location error when configuring backups to Windows Shared Folder in RSA Authentication Manager 8.x 1.44KNumber of Views How to Configure Database Backups to write to an NFS File Share instead of Local Directory '/home/oracle/AveksaExportImpor… 434Number of Views Authentication Manager: Backup failed to Windows Share (cifs) 164Number of Views Failed to create a backup on Windows shared folder for RSA Authentication Manager 8.1 289Number of Views RSA Authentication Manager 8.x backups fail to a Windows Share where SMBv1 is disabled 829Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Deploying RSA Authenticator 6.2.2 for Windows Using DISM Downloading RSA Authentication Manager license files or RSA Software token seed records
Don't see what you're looking for?