On 9/25/25 11:14, Andreas Rogge wrote:
Am 24.09.25 um 12:09 schrieb Spadajspadaj:
For example, if I had a backup done with
Plugin = "bpipe:file=/_rpmlist_/rpm.lst:reader=/usr/bin/rpm
-qa:writer=/ bin/bash -c 'xargs dnf install -y'"
But tried to extract it to a FD with a job definition of
Plugin = "bpipe:file=/_rpmlist_/rpm.lst:reader=/usr/bin/rpm
-qa:writer=/ bin/bash -c 'cat > /tmp/rpm.lst'"
to just get the raw context of the stream (or you could replace cat
with dd or whatever.
Actually, talking about a list of packages done this way I'm not sure
if I wasn't simply able to restore the resulting stream on another FD
_without_ the plugin as just a file.
Changing the FileSet has no effect on restore. The Plugin options are
recorded during backup and these recorded options are used on restore.
You have two options to make this work:
* override plugin options during restore
* disable plugins on the FD so it will restore plugin data as a file
Nevertheless, for this specific case, I'd got with a client-side
RunScript that creates the file and then back that up.
Just for the sake of completness. I did some testing and it seems my
previous statement about restoring to file was a mistake because for
some nodes I do backup using two separate methods and apparently I was
restoring using that other method (and mixed those two while writing to
the list).
So yes, you cannot just write straight to a file from a bpipe backup.
Cheers,
MK
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/c6097c8f-0c2f-47f6-ae13-da01138cd7b9%40gmail.com.
