- Check the br.log on the appliance. Look for an error message similar to this:
[03/16/15 12:42:15 0/3 backupDB.pl 18810] __DIE__ CHECK USERID "mtahlil.admin" AND PASSWORD (APPLICABLE FOR FTP PROTOCOL ONLY). IF USING SSH, CHECK THAT RSA PUBLIC KEY HAS BEEN GENERATED AND COPIED INTO TARGET SYSTEM (FOR MORE INFORMATION, CHECK "BACKUP AND RECOVERY" ONLINE HELP, STEP 3 "RSA AUTHENTICATION SETUP").
- Confirm the RSA key has been installed into the correct file which must be manually created in the home directory of he user defined in the back up configuration.
- The RSA Key must be generated and stored on the backup server before the backup procedure can execute. This is accomplished by adding the key to the
$HOME/.ssh/authorized_key
s file for the appropriate user account on the backup server.
- When you select and copy the key from the RSA key field to paste it into the authorized_keys file, be sure to select all characters in the string. It is good practice to compare the string in the RSA field and the authorized_keys file carefully to verify that the entire string is copied.
- Confirm the user account has RW rights to the designated back up destination directory.
- Consider deleting and recreating the backup configuration within the WebUI and re-test. Note: This action will generate a new SSH key therefore the authorized_keys file will need to be edited to reflect the new SSH key.