You see in Tools > Backup and Restore > History Log EM page that some backup task has failed during execution.
Possible causes for the backup failure are:
Remote host name or IP address is incorrect or not accessible.
User credentials for remote host are incorrect.
Destination path does not exist or user has no rights to write data under it.
Remote host fingerprint is incorrect or not the top priority.
Resolving backup failures
Perform the following steps to find the cause of failure:
Enable debug logs in EM.
Run failed backup task again.
Download troubleshooting archive.
Extract the archive and open ElementManagerDebug.txt from it, then scroll to time of task execution and find output of pscp_mod tool.
Analyzing output and resolving issue
Check if the output contains one of the following:
Network error: No route to host – ip address or hostname of remote host you use for backup is incorrect or it may be down. Check that the host is correctly configured and alive.
Is not a valid format for a manual host key specification – check that the fingerprint that you have entered in the backup destination is correct.
Host key did not appear in manually configured list – fingerprint you used in configuration is not supported by pscp_mod or not the top priority. Use another fingerprint according to description of backup destination configuration.
Access denied – credentials you have entered are incorrect. Check that user login and password for remote server are valid and reconfigure destination with it.
Unable to open <destination path>/<backup file> – destination path you have entered does not exist on remote server. Create it manually or change to another existing path.
Unable to open <destination path>/<backup file> : permission denied – destination path you have entered exists, but account you use for backup does not have write permissions. Change directory permissions for user or use another path.
