We are running into a problem with on of our DA servers and their backups.
Local (storage) backups run fine but FTP back-ups fail.
we've set a custom TMP path for the backup.
Normally the TMP path looks like: /mnt/tmpstorage/tmp/admin.pid
which works ok.
but with the FTP backup the tmp path looks like this:
/mnt/tmpstorage/tmp/admin.25720.pxHnsB7peOvbs0VItgNWXzFpXjqL3Urq/EHzuoryWr6GIUdAmSAxCHfOHDIoDky5y
Notice that behind the PID there are two seemingly random strings separated by a "/"
Since the backup script issues a mkdir command this will never work when creating two folder levels at once, we at least need to use "mkdir -p"
My question is why does the ftp backup add add two seemingly random string after the PID to the tmp folder and secondly where can I find the script direct admin uses to create the backup statement/process so I can debug/resolve this.
Error message (redacted)
n.b.
please note that the folder rights are correct and the same tmp path is used for the local storage backup which runs fine.
the two random string after the PID change every backup task just like the pid.
We've got 6 other servers running a similar configuration (disk and ftp backup) and they don't show similar behaviour.
Local (storage) backups run fine but FTP back-ups fail.
we've set a custom TMP path for the backup.
Normally the TMP path looks like: /mnt/tmpstorage/tmp/admin.pid
which works ok.
but with the FTP backup the tmp path looks like this:
/mnt/tmpstorage/tmp/admin.25720.pxHnsB7peOvbs0VItgNWXzFpXjqL3Urq/EHzuoryWr6GIUdAmSAxCHfOHDIoDky5y
Notice that behind the PID there are two seemingly random strings separated by a "/"
Since the backup script issues a mkdir command this will never work when creating two folder levels at once, we at least need to use "mkdir -p"
My question is why does the ftp backup add add two seemingly random string after the PID to the tmp folder and secondly where can I find the script direct admin uses to create the backup statement/process so I can debug/resolve this.
Error message (redacted)
n.b.
please note that the folder rights are correct and the same tmp path is used for the local storage backup which runs fine.
the two random string after the PID change every backup task just like the pid.
We've got 6 other servers running a similar configuration (disk and ftp backup) and they don't show similar behaviour.