Additional backup destinations cannot be configured to use absolute file paths via the user interface.
There have been some instances when the remote backup server cannot validate due to the path is not valid.
An example of a failure that has been seen that need the path to be adjusted from a relative to absolute path or vice-visa:
"Validation for transport “$BACKUP_NAME” failed: Could not delete the file we had uploaded onto the server: Couldn't delete remote file: Permission denied"
You will need to be able to SSH as root or sudo to root to perform these changes on the command line.
The backups configuration files are found in:
You will use your preferred editor (nano, vi, vim, etc.) to open the file. The file name is normally:
These changes can impact the backup GUI interface's functionality and make the settings uneditable from the interface. Reverting these changes will allow the interface to function once more.