Hi everyone,
I'm trying to backup a postgresql database using backup jobs. The database is located inside a container and is running under docker.
I got the warning "Failed to execute pre-job script" (see the picture below). Otherwise the post-job script indicates "Post-job script has been executed successfully". Even I wrote a simple shell script (echo "Hello world" > newfile.txt) but still not working
That's why I don't think the problem is not related to docker or Postgresql db.
I'm using veeam agent (root privileges) with RHEL 7.9 on my remote server and I'm using Veeam Backup & Replication 12 with Windows on my Backup server.
N.B : When I try to run the same command line of the pre-job script directly through the terminal it works fine.
Please can you help me resolve this issue?
Thank you all.
Veeam Agent for Linux does not support containerized Postgresql databases.
Would you tell us more about your setup? Is THEL 7.9 running on a physical machine/VM, and the DB is running inside a container hosted on the same RHEL?
The remote server (RHEL 7.9) is running on a VM and the DB is running inside a container on the same host. Veeam Backup and Replication 12 is running on another Windows server. The communication is done through veeam agent. The scripts are uploaded from the "D:" drive with '.sh' extension (script.sh).
Sorry but I don't think the issue is related to the container or to Postgresql databases because as I said before even a simple script (outside container) is not working.
Example of script :
#!/bin/bash
echo "Hello world" > \home\mydirectory\newfile.txt
We strive to keep our documentation concise for better readability, and this particular case is not directly related to our product. Even when initiated manually, it did not work. Therefore, I would rather wait for more similar questions. If we receive enough similar requests, we can consider addressing it in our knowledge base (KB).
@karsten123
FYI: I have discussed this situation with my colleagues, and it turns out that this question arises occasionally. Therefore, it would make sense to include a note about it in our user guide. I will work on this with the technical writers team.
