On Saturday 09 April 2005 16:36, Alan Brown wrote:
> On Sat, 9 Apr 2005, Kern Sibbald wrote:
> > Well, 1.36.x does use PoolId, but version 1.37.x uses StorageId, which
> > ties it to the specific autochanger being used.
>
> Unless the StorageID is temporary and trashed each time update slots(*) is
Is there any compelling reason why "update slots" forces the drives to be
unloaded? "mtx status" usually(*) includes information about the
designated slot number for any tape in a drive.
Once you get past forced unloading happening, it should be possible to
make "mtx status" or an "update slots
On Sat, 9 Apr 2005, Kern Sibbald wrote:
Well, 1.36.x does use PoolId, but version 1.37.x uses StorageId, which
ties it to the specific autochanger being used.
Unless the StorageID is temporary and trashed each time update slots(*) is
run, this will be a really bad idea.
Tapes need to be freely s
On Sat, 9 Apr 2005, Arno Lehmann wrote:
It works for me... In your case, relying on pools might be more useful. After
all, at baculas current state, you need some difference between tapes in the
changers, and relying on MediaType is worse than Pool, if your drives do
accept the same Media...
I h
On Fri, 8 Apr 2005, Josh Lauricha wrote:
(please wrap your lines at ~76 cols, thanks)
On a restore the bacula-directory will
speend hours building the restore directory tree, however there is no
activity on my Bacula MySQL thread, so it's all internal.
Yup. BTDTGTTS (been there, done that, got th
On Fri, 8 Apr 2005, Slartibartfast wrote:
This morning I swapped out the tapes and tried again. Here is the
resulting error message. Question is; is this a tape media, or drive
error?
At the risk of stating the obvious:
Check ALL your scsi cables and terminators.
The single most common cause for
hi there!
somehow we missed our recycling of volumes date by 2 days...
it was needed that we intervene and append a new volume or purge an old
one so that backup could proceed...
one of our sysadmins dediced to restart the box in the mean time...
we were left with a backup job having a status R
On Saturday 09 April 2005 14:40, Arno Lehmann wrote:
> Hello.
>
> Kern Sibbald wrote:
> > Hello,
> >
> > On Friday 08 April 2005 23:17, Michael Joyner wrote:
> >>Confused.
> >>
> >>I have two stores configured, vxa-0, vxa-1
> >>when I run "update slots" vxa-0, it will mark all the tapes currently i
Hello.
Kern Sibbald wrote:
Hello,
On Friday 08 April 2005 23:17, Michael Joyner wrote:
Confused.
I have two stores configured, vxa-0, vxa-1
when I run "update slots" vxa-0, it will mark all the tapes currently in
the loader.
when I run "update slots" vxa-1, it will unmark all the tapes from the
vxa
Emery,
Emery Guevremont wrote:
Is there a way to compile bconsole for windows? Or even better, is there
a bconsole binary for windows that can be downloaded?
It's in the windows client package. At least here I got it like that.
Arno
--
IT-Service Lehmann[EMAIL PROTECTED]
Arno
Hi.
Slartibartfast wrote:
Running 1.36.2 on a CentOS 3.4 server connected via SCSI to an Overland
XpressLoader.
No worries... don't see why it shouldn't work.
btape test works fine with no errors.
Have been trying to run the btape fill, both single and multi. I ran a
successful single test yesterd
Hello,
On Friday 08 April 2005 23:17, Michael Joyner wrote:
> Confused.
>
> I have two stores configured, vxa-0, vxa-1
> when I run "update slots" vxa-0, it will mark all the tapes currently in
> the loader.
>
> when I run "update slots" vxa-1, it will unmark all the tapes from the
> vxa-0 storage
12 matches
Mail list logo
