There are some cases where a restore from a backup stored on the new S3 Compatible Destinations can result in a Partially Complete Status and the following generic error:
[ERROR] Not all files restored correctly. Error: Some files where failed to downloadThis generic error occurs because JetBackup is unable to parse the exact error reported from the S3 Destination. In order to view the exact error message please check the following log via the terminal: /usr/local/jetapps/var/log/jetbackup5/s3/s3.log.
From here you will be able to see exactly which file/folder produced the issue during the restore. If it was a connection issue, then it can be intermittent and a retry may resolve. Otherwise, further investigation may be needed to resolve the issue.
One example we have seen is the following:
- S3 Log reported a file could not be downloaded:
ERROR: Can't open destination file for writing - Further investigation found that the file name was already being used as a Directory name in the same file path.
- Since the file was now a directory, trying to restore the original file with the merge option resulted in the error.
- The resolution was to remove the directory/change its name to allow the file to be restored.
