"Failed to validate remote location" error when configuring backups from the Operations Console (Maintenance
> Backup and Restore
> Manage Backups
selecting Windows Shared Folder as a backup location.
System log show the following error:
15-04-15 11:37 ERROR 26113 Create backup via OC Operations Console administrator “RSAAdmin”
attempted to create a backup at “\\sample.com\RSA_Backup\201504151135.RSAbackup”
Failure Unexcepted exception caught RSAAdmin UNEXPECTED_EXCEPTION testAM81pri.kangnet.local
10.10.10.1 10.10.10.2 .admin.impl.OCManageBackupImpl$1CreateBackupThread \\sample.com\Share\201504151135.RSAbackup
There might be multiple causes to such error message:
- Local security policy or group policy requires NTLMv2 on the network refusing LM and NTLMv1 (Note: RSA Authentication Manager 8.1 SP1 patch 1 included NTLMv2 support).
- DNS resolves the Windows server where hostname is used.
- Directory has correct permissions.
Multiple things can be tried to see what the issue is:
- Check if the remote location is pinging from the appliance. From the Operations Console select Administration > Network > Network Tools).
- Try mounting the remote share manually, by executing the following steps:
- SSH into Authentication Manager primary.
- Change to root using the command:
sudo su -
- Create a test directory under /opt/rsa/am/backup to see if the Remote Shared Folder can be mounted to it.
- Try mounting the Remote Shared Folder to the newly created directory.
mount.cifs <Remote_Share> /opt/rsa/am/backup/test -o user=<Share_User>,domain=<Name>
- Provide the remote share password when prompted.
- If the command in step 4 didn't work, please try with sec option as below for NTLMv2:
mount.cifs //sample.com/Share /opt/rsa/am/backup/test -o user=<Share_User>,domain=<Name>,sec=ntlmssp
mount.cifs //sample.com/Share /opt/rsa/am/backup/test -o user=<Share_User>,domain=<Name>, sec=ntlmsspi
- If the mount in step 2 worked, try to create a file on the mounted Remote Folder to check the permissions.
- Create a file to validate the user has write permissions:
- Validate test.txt file created in the Remote Location.
- If step 1 fails, then there is a connection problem.
- If step 2 fails, then there is a mount issue and a mount error will appear clearly.
- Lastly, if step 3 fails, then the user used for mounting the remote folder does not have sufficient permissions.
After identifying the issue, then it can be resolved much easier.