Hi Bruno, thanks for your reply. I've got it in the end working with Device = "| magic script" I think, but unfortunately doesn;t solve the problem. I think with @| bareos will execute it only once at startup, because it's a config include, I needed it executed every time a resource is being used. Nevertheless, the problem is always the same, when bareos has more than 1 device to write to, the jobs fail with the "No volume name given error", see here : https://groups.google.com/forum/?fromgroups=#!topic/bareos-users/Nbv-_fRWxaY.
I tried 3 diff scenarios: 1. define multiple devices in storage resource, as recommended in bareos doku. 2. script the device definition as described above. 3. use a virtual autochanger as described here: http://blog.bacula.org/whitepapers/CommunityDiskBackup.pdf the problem is the volume selection I think, when more than 1 device is available in the storage. any clues how to solve this? thanks, Robert -- 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 post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
