Hi,
Is there a way to limit what is considered a 'copied' job? I recently
enabled a copy-job which I had in place for ages and just decided to
activate. Unfortunately it wants to copy a few hundreds of jobs going back
months, which is not very useful.
How can I mark jobs as already copied? I
OK, so I've gone through my drives, mounting and unmounting from within
Bacula and then checking those results in MTX to see if there are any
discrepancies.
I should note that I modified my SD config file to change the device names
to match the drive index. Maybe I should have waited to make
Hi Patti,
My server is running Ubuntu 16.04.2 LTS (64bit), Bacula v7.4.7 and mtx tools
are at v1.3.12.
As I mentioned in my other post, in reply to Kern's response, I've managed to
fix the issue by installing full set of magazines into the changer's carousel.
This immediately caused mtx to
Hi Kern,
On Wednesday, June 28, 2017 11:01:01 AM Kern Sibbald wrote:
> Hello,
>
> I think this is what we politely call a "pilot error/misunderstanding".
Which one? I do not see any error I might have made, certainly nothing that
would require strong words ;-)
> From what you have described,
Kern - thank you for referring me to the white paper. I wish I had been
able to read that about nine months ago - it would have saved me a lot of
time in getting my gateway setup. However, after reading the white paper I
didn't see anything which seemed to speak to my particular challenge.
Patti
Luke,
This usually happens when the path to the device in Bacula does not line up
with the OS. For each drive one at a time, mount a volume in bconsole and
verify with mtx status that it is where it is expected to be. Release the
volume and verify that it has returned to its slot. Go
Hello,
Try reading the Object Store white paper posted on the web site.
It discusses the use of the AWS storage gateway.
Best regards,
Kern
On 06/28/2017 07:23 PM, Luke Salsich
wrote:
Hello everyone,
Ivan,
You’ve not indicated what OS that you are using – it’s somewhat difficult to
say whether your mtx package has a bug. I’ve never had this issue with mtx
running on RHEL6. I don’t see your I/E slot being identified as the I/E slot,
just a regular slot, which can be done if slots are
Hello everyone,
I'm really struggling to solve a problem with my bacula setup and I could
use some guidance or helpful comments, PLEASE PLEASE. I've been using
Bacula for about six months with an AWS storage gateway with success, but
still have so much to learn. I would welcome any help!!
Hello,
You are running on a very old Bacula, so VolErrors probably does not
have any significant meaning. The concept is that when the Storage
daemon sees an error with a volume, it will increment that field. If
you want to see what is implemented, you will need to look at the
Hello all,
We are using version bacula_5.2.6+dfsg-9 of bacula for our
environment. Our setup up till recently was saving backups to disk
files. We have introduced a TS4500 library recently and we have
experienced the following problem.
For one of the tapes of the TS4500 library, there is a
Hello,
I think this is what we politely call a "pilot error/misunderstanding".
From what you have described, mtx is behaving correctly. Normally I
turn off the mail slot (aka import/export slot) on my autochanger and
the problem goes away. It is my understanding that Bacula can be used
12 matches
Mail list logo
