I'll attach the relevant config files, stripped of the unnecessary comments, etc., and with passwords redacted. Here's the general structure:
Host: backupdir - backup director, running `bacula-dir`
Host: backupsddemo{1,2} - running both `bacula-sd` and `bacula-fd`
Both `backupsddemo*` hosts have a single local disk pool stored at
`/backupdata`. There are 2 pools defined as "FullPool" (on
`bacupsddemo1`) and "IncPool" (on `backupsddemo2`). I was able to run a
Full and an Incremental for job `Test-backupsddemo1`. I wrote a file
between the Full and the Incremental, so I could do the restore for each
type and differentiate. The restores went perfectly, and I could tell
by the presence/absence of that file, that it restored the correct one.
When I try to run the VirtualFull, though, it fails. The relevant error seems to be the following, taken from the director running with `-d 200`:
backupdir-dir: msgchan.c:297-14 Rstore=backupsddemo2-sdbackupdir-dir: msgchan.c:308-14 rstore >stored: use storage=backupsddemo2-sd media_type=File2 pool_name=IncPool pool_type=Backup append=0 copy=0 stripe=0 wait=1backupdir-dir: msgchan.c:315-14 >stored: use device=FileStorage-demo2-dev1 backupdir-dir: getmsg.c:152-14 bget_dirmsg n=-1 msglen=-6 is_stop=0:backupdir-dir: getmsg.c:152-14 bget_dirmsg n=106 msglen=106 is_stop=0: 3924 Device "FileStorage-demo2-dev1" not in SD Device resources or no matching Media Type or is disabled.backupdir-dir: msgchan.c:321-14 <stored: 3924 Device "FileStorage-demo2-dev1" not in SD Device resources or no matching Media Type or is disabled.
For reference, the corresponding SD running with `-d 200` is showing no output at all when the VirtualFull tries to run, but does show output for things like `status storage...`, and when I do the Incremental to it, or the restore from it.
At this point, I'm confused by the "3924 Device "FileStorage-demo2-dev1" not in SD Device resources or no matching Media Type or is disabled.". As far as I can tell, the Media Type ("File2"), the pool ("IncPool") and the device ("FileStorage-demo2-dev1"), are all correct for that SD.
If there were any evidence that it was failing because it was trying to read the Full backup (or the corresponding `Full-*` file) from SD2, that would make sense, and confirm that I can't do the VFs this way. But that's not the evidence I'm seeing.
Thanks, Lloyd On 4/8/26 13:24, Lloyd Brown wrote:
Hey, all. I'm in the middle of designing the next generation of our backup system, which will likely be based on Bacula 15. This time, we'll be using both disk and tape, vs the disk-only we've run before, which brings up a question or two that I haven't encountered before.When running VirtualFull jobs, does the source material (previous Full, latest Differential, subsequent Incrementals), need to all reside in the same Pool? In multiple pools but available to the same SD?For this system, we're planning on 2 SD hosts, with local disks, and a tape library attached to one of them. We thought that we could keep the Fulls/VFs entirely on tape, only store the incrementals on disk, and write new VFs directly to tape. As a result, we trimmed down the size of our disk pool for cost reasons (HDDs and SSD are both crazy expensive right now). I don't think I'll have enough space in the disk pool to store Incrementals *and* a previous Full/VF. If that's true, I need to re-think my design a bit. It may mean we just do true Fulls to tape, and Incrementals on disk, and not get to use VFs at all.Thanks, Lloyd
-- Lloyd Brown HPC Systems Administrator Office of Research Computing Brigham Young University http://rc.byu.edu
bacula_demo.tar.gz
Description: application/gzip
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
