This is a normal behavior, the copy job and the files associated become active only when the original media disappear (this is what a copy if normal for :-) ) So as you experiment, your copy jobs and your configuration is working as expected and documented. I didn't personnaly experiment too much if there special status of the media that would drive the database to shift and use the copy, but from memory this is not implemented. So try to trick the software and the way it behave normally finish in a worse situation ...
Did you have a useful use case of using the copy, if the local (original)one exist? On July 20, 2018 8:59:33 AM GMT+02:00, Nicolas Jovanovic <[email protected]> wrote: >Hello Bruno, > >Thanks for your message. > >In my case, I was able to restore files if my original media was not >available. My main concern (and I do not know if I misconfigure >something)is if both media (Original and Copy) are available, if I want >to restore files from the Copy (so the remote media) : I have an error >saying that no Volume Names were found. > >Ideally, I could use local or remote storage daemon without an issue... >But not in my actual configuration. > >Regards, > >Nicolas > >-- >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. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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.
