The Amazon S3 path is very sensitive to whether or not you include leading and/or trailing forward slashes.
Don't include leading /
If you enter this path: /production/ the backups will end up in the following path: "blank folder"/production the "blank folder" possibly being created because I assume the full path looks something like this: https://amazon.something/bucketName//production/
Must include trailing /
If you enter this path: test/production, the backups will end up inside the test folder with production as a part of the file name(s). Again, as the above statement, I assume this has to to with the composition of the path.
Paths in Settings
Specification of paths in settings have the same issue. Some paths require trailing slashes, some don't. Some require you to enter full path to executable, some require just the path to the location of the executable.
Amazon S3
The Amazon S3 path is very sensitive to whether or not you include leading and/or trailing forward slashes.
Don't include leading /
If you enter this path:
/production/the backups will end up in the following path:"blank folder"/productionthe "blank folder" possibly being created because I assume the full path looks something like this:https://amazon.something/bucketName//production/Must include trailing /
If you enter this path:
test/production, the backups will end up inside thetestfolder withproductionas a part of the file name(s). Again, as the above statement, I assume this has to to with the composition of the path.Paths in Settings
Specification of paths in settings have the same issue. Some paths require trailing slashes, some don't. Some require you to enter full path to executable, some require just the path to the location of the executable.