Hi, we have a setup of 2 servers on both there is one bareos-sd. One SD provides a FileStorage and the other SD takes the stream from the first one and copies/migrates it to tape. In this setup sometimes there is a tape drive error. If this happens the corresponding copy/migrate-job hangs. We then use the setdevice command to remove this drive from autoselection and kill the job. The problem here is that the storage job in the FileStorage remains and cannot be killed (cancel storage=FileStorage jobid=xxx). This leads to a reservation of the virtual tape until we restart the SD which provides the FileStorage. As we have a huge amount of data with some jobs running for more than a week restarting the SD is a bad idea.
So my questions are: - Did I do something wrong? - Is there a configuration option to solve this? - Or is it maybe a bug? At the moment we are using 21.1.6 again as there was a crashing problem in 22(but same problem here) and 23 is not suitable for us because of the removed compatible mode as we have some solaris 10 servers which will hopefully turn off next near. With kind regards, Dennis -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/CABqFkupHwoXUUM8s9xWfkRg%3D-zv8k%3DPjnz86EYDurMjD8Dxi%3DA%40mail.gmail.com.
