On 11/27/23 15:26, MylesDearBusiness via Bacula-users wrote:
Hello, Bacula experts.My cloud provider offers only curlftpfs based storage, which I have enabled and secured. I created a username “backupuser” and a system service that launches the service, effectively mounting the remote storage to /mnt/my_backup and running the userspace curlftpfs command as the user “backupuser”. This user has demonstrable read/write privileges in the file system as expected. So far so good.I installed bacula on my Ubuntu 22.04.3 LTS server and got bacula-dir, bacula-fd, and bacula-sd all running. In summary, when I try to run my backup job I get an error: Device is BLOCKED waiting for mount of volume ChatGPT4 doesn’t know nearly as much as this august body, I’m hoping a kindly member may be able to give me a hand up. More details:https://gist.github.com/mdear/99ed7d56fd5611216ce08ecff6244c8b Thanks, <Myles>
What does this show?: # ls -la /mnt/khapbackup/backup/bacula/archive Is there a Bacula File volume named `Vol-0014` in there? Is it rw for the `bacula` user which the SD (normally) runs as?If it is not there, but you know where it is, them you must move it there, and set the ownership to `bacula:disk` and the permissions to allow the bacula user to, well... Read and write to it. :)
It is just a guess, but is it possible that this Bacula file volume lives under a directory which you mounted `/mnt/khapbackup/backup/bacula/archive` on top of, so it exists, but is not visible currently? This is just a guess, but it is also a common mistake. :)
If you truly do not know where this Bacula file volume is, then you need to delete it from the catalog so the director no longer thinks it is accessible:
* delete yes volume=Vol-0014 Might want to run the bconsole `query` command and select option 14 to be sure there are no jobs on it that you might need.Once deleted from the catalog, the Director should select a new volume (or create a new one if `LabelFormat = yes` is set in the Pool `File` and `LabelMedia = yes` is set in the SD's Drive devices writing to this directory.
Alternately, you can just disable the volume in the catalog: * update volume=Vol-0014 volstatus=DisabledAlso, consider that the ownership and permissions that you set on the mount point for the user `backupuser` will not allow the SD running as the user `bacula` to read/write there - unless you dis something like make the bacula user a member of the backupuser's group, and you gave the group read/write permissions into that directory tree.
Hope this helps! Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
