This sounds right to me: the option to specify an alternative restore-to
client exists in the menus, but is simply absent from the command line
interface. It's also really weird that changing "Client" in the modify
job menu does something different than specifying client= on the command
line.
To recap, I'm trying to restore a job to a client other than where it
came from, and do this via a script that is fed into bconsole. In the
mean time, my stopgap solution is to make the script something more like
this, where "1" is the restore-to server ("Y")'s position in bacula's
client list:
[script]
restore jobid=X client=X file=<filelist where=/tmp/test
mod
5
1
yes
[end script]
bconsole <script
That seems to work, but seems really kludgy.
Thanks again! I'm still very impressed with Bacula.
Andy
Kern Sibbald wrote:
> The current behavior is really a sort of mini-kludge because it is not very
> evident to the user what is going on. Probably what we need is a different
> keyword for the input and output client. Also the code has evolved quite a
> lot over the past years, so all parts of it may not be totally consistent.
> Most of this code will be rewritten or reorganized during the GUI project
> after the release of 1.40.0
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
