One other thing to note -- sometimes the tape drive will improperly
determine the tape size for whatever reason. I have had experience with
a DLT7000 drive that, for whatever reason, initialized a tape to 15GB.
After that, I had to manually set the drive to 35GB and re-initialize
it. After that, no problem.
Just stuff to look out for.
Anwar Ahmad wrote:
Hi Phil,
No worries, I've checked that both are DLT2 drives. Specifically they
are HP SureStore Autoloaders. Both were bough at the same time from HP
directly. They were also configured identically. We initially had a
bunch of DLT tapes around (10 or so) from our old HP server which had
an inbuilt DLT drive. This was DLT1.
When we purchased the 2 Autoloaders we wanted to reuse some of the old
tapes rather than junk it since we're using bacula as network backup.
We also purchased well over 30 DLT 40/80 tapes.
Interestingly, I've relabeled a 40/80 tape that was originally in the
pool that backed up from pool1 (the one with the problem) and put it
into pool2 (working normally) and it works correctly. I thought about
the physical tape drive causing the problem but I've nowhere to check?
Is there any way to check using software?
I'm not certain how this actually works out. Since both autoloader are
bought together and are from the same batch, 1 couldn't have been DLT1
while the other DLT2. I ruled out the autoloader as the source of the
problem since it's still working. It's unlikely a hardware fault could
cause something like that... however I could be wrong. I'd like to
explore software configuration issues before accepting the drive is
faulty. From my previous experience, the drive either works or don't.
I've never encountered an issue where it slows down but still works....
Thanks!
Kind Regards,
Anwar
Phil Stracchino wrote:
Anwar Ahmad wrote:
Hi All,
I have this problem where I've got a mix of 20/40GB and 40/80GB DLT
tapes that are in 1 pool configured to backup using 1 tape drive. The
problem is, all of them seem to be acting like 20/40GB tapes including
the higher capacity ones. I've not been able to get the 40/80GB tape to
store even remotely near 40GB let alone the compressed capacity of
80GB.
I was wondering whether anyone had similar problems before...
The funny thing is, I've got a another pool that uses another tape
drive
that all backup correctly. Most backup are close to around 68-72GB,
which I believe is fine. I've configured both pools & devices similarly
but don't know why 1 only backs up to around 34GB (acting like a
20/40).
Both tape drives were bough at the same time and are identical models.
Is the mix of tapes causing the problem?
They are currently listed as /dev/nst0 and /dev/nst1 respectively. Is
there any configuration files in outside of bacula-dir that I need to
configure or perhaps in Linux system files perhaps, although I don't
recall any configuration files other than the bacula conf files where
done back during the initial setup.
This may be a silly question, but ......
You've stated you have a mixture of DLT1 (20/40GB nominal) and DLT2
(40/80GB nominal) tapes. Are your drives DLT1 or DLT2? A DLT1 drive
will only get 20/40GB capacity from a DLT2, DLT3 or even DLT4 tape.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
