On Thu, Jun 19, 2003 at 04:14:38PM -0700, Jay Lessert wrote:
> On Thursday 19 June 2003 14:09, Ean Kingston wrote:
> >I'm using Solaris and, according to the documentation, it should not
> > be using hardware compression unless I specify the 'compress'
> > device (/dev/rmt/0cn) as opposed to the on
On Thursday 19 June 2003 14:09, Ean Kingston wrote:
>I'm using Solaris and, according to the documentation, it should not
> be using hardware compression unless I specify the 'compress'
> device (/dev/rmt/0cn) as opposed to the one I did use
> (/dev/rmt/0n).
I'm not sure what documentation you're
On Thursday 19 June 2003 14:41, Tom Brown wrote:
>> I also have such a situation!
>>
>> if I try to relabel it, it say that the tape is already labeled.
>> But this
>
>is
>
>> probably
>> read from tapelist file and not really from the tape.
>>
>> version 2.4.4-20030605
>> chg-zd-mtx
>
>i have a th
On Thursday 19 June 2003 14:19, Tom Brown wrote:
>> Many drives have an led tally on the front to indicate when the
>> comnpressor is active.
>>
>> And no, amanda will not use it, and in fact cannot because once a
>> lock on the drive is obtained, its not released until done.
>> Turning it off is
On Thursday 19 June 2003 14:09, Ean Kingston wrote:
>> -Original Message-
>>
>> On Thursday 19 June 2003 11:51, Ean Kingston wrote:
>> >I couldn't find this one in the list archives, so here it is.
>> >
>> >I'm using 40GB DLT tapes (according to the label). Despite what
>> > the comment pro
On Thu, Jun 19, 2003 at 11:33:59PM +0200, Paul Bijnens wrote:
> However, the hardware compression algorithm seems to be a very
> good one: the measured capacity is still about 100 GByte.
> This means that the algorithm does not fall into the known pitfall
> of blindly imposing it's compression engi
Title: Nokibox
Merhaba,
Sizi bir konuda bilgilendirmek istiyorum, bugüne kadar Internetten
haftada 250$'a yakýn para kazanýyordum. Cebimde param vardý ama rahat
degildim. Çünkü Türkiye krizin içindeyken, insanlar evlerine yiyecek ekmek
götüremezken benim kazandýg
Title: Nokibox
Merhaba,
Sizi bir konuda bilgilendirmek istiyorum, bugüne kadar Internetten
haftada 250$'a yakýn para kazanýyordum. Cebimde param vardý ama rahat
degildim. Çünkü Türkiye krizin içindeyken, insanlar evlerine yiyecek ekmek
götüremezken benim kazandýg
Jon LaBadie wrote:
On Thu, Jun 19, 2003 at 03:21:12PM +0100, Tom Brown wrote:
define tapetype unknown-tapetype {
comment "just produced by tapetype prog (hardware compression on)"
length 100608 mbytes
Wow!!!
filemark 0 kbytes
speed 12899 kps
}
...
Is the comment correct, was HW compres
* Paul Bijnens <[EMAIL PROTECTED]> [20030619 16:43]:
> Joshua Baker-LePain wrote:
>
> >On Thu, 19 Jun 2003 at 4:57pm, Tom Brown wrote
> >
> >
> >
> >>>ISTR you saying this is Linux? If so, then 'mt compression 0' should do
> >>
Joshua Baker-LePain wrote:
On Thu, 19 Jun 2003 at 4:57pm, Tom Brown wrote
ISTR you saying this is Linux? If so, then 'mt compression 0' should do
it. You can check the status by pointing 'tapeinfo' (from the mtx
distribution) at the generic device associated with your tape drive.
It i
Ean Kingston wrote:
I'm using 40GB DLT tapes (according to the label). Despite what the comment produced says, I used the non-compressed device. I didn't give it an estimate for the tapesize.
Despite using the non-compressed device, I believe the comment :-)
Probably solaris, isn't it? You did m
On Thu, Jun 19, 2003 at 09:20:31AM +0200, Toralf Lund wrote:
> What is the right and proper way to unschedule the dump of a DLE? I
> thought the answer would be "amadmin delete, then remove DLE from
> disklist",
>From this I assume you mean: "stop backing up the DLE at all" (as
opposed to "don't
> I also have such a situation!
>
> if I try to relabel it, it say that the tape is already labeled. But this
is
> probably
> read from tapelist file and not really from the tape.
>
> version 2.4.4-20030605
> chg-zd-mtx
i have a theory to my problem but not 100% certain yet.
i have, today, run a
I also have such a situation!
if I try to relabel it, it say that the tape is already labeled. But this is
probably
read from tapelist file and not really from the tape.
version 2.4.4-20030605
chg-zd-mtx
regards,
gregor
> Many drives have an led tally on the front to indicate when the
> comnpressor is active.
>
> And no, amanda will not use it, and in fact cannot because once a lock
> on the drive is obtained, its not released until done. Turning it
> off is best done via the dip switch or jumper settings program
> -Original Message-
> On Thursday 19 June 2003 11:51, Ean Kingston wrote:
> >I couldn't find this one in the list archives, so here it is.
> >
> >I'm using 40GB DLT tapes (according to the label). Despite what the
> > comment produced says, I used the non-compressed device. I didn't
> >
On Thursday 19 June 2003 11:57, Tom Brown wrote:
>> ISTR you saying this is Linux? If so, then 'mt compression 0'
>> should do it. You can check the status by pointing 'tapeinfo'
>> (from the mtx distribution) at the generic device associated with
>> your tape drive.
>
>It is linux yes - will ama
On Thursday 19 June 2003 11:51, Ean Kingston wrote:
>I couldn't find this one in the list archvies, so here it is.
>
>I'm using 40GB DLT tapes (according to the label). Despite what the
> comment produced says, I used the non-compressed device. I didn't
> give it an estimate for the tapesize.
>
>Wr
> Was that the tape in the drive when you did your tapetypes?
ahhh - erm i can't remember actually yes i can and no it wasn't -
the last tape was as...
amcheck-server: slot 7: date 20030618 label gthost07 (first labelstr match)
amcheck-server: slot 1: not an amanda tape
the tape 07 was rea
On Thu, Jun 19, 2003 at 04:55:11PM +0100, Tom Brown wrote:
> I've got a bit of a strage issue here. All tapes have been labelled and i
> did a couple of test runs with all disks in the disklist commented out so it
> just ran through its cycle and all 7 tapes were fine.
>
> that was yesterday
>
>
> I am probably missing a clue in the configuration file. After trying
> to get any of the changers to work with both drives AND Barcode
> reader AND the robot my brain has been slowly oozing from my
ears.perhaps you need BOTH
offlinestatus=1OFFLINE_BEFORE_UNLOAD=1
Hello,I have been a long time user of amanda. I have just purchased an ADIC Scalar 100 with 2 LTO (LVD) drives. Amanda 2.4.4 is compiled (with some headaches) under Solaris 8. I have downloaded mtx and can drive the Scalar fine, however, the drive requires an mt command to properly eject the tape.
I had a quick look on the IBM site's for you - all the windoze configuration
info suggests that this is done with driver software - so hopefully you
won't need your tool kit.
Good luck.
Kevin
-Original Message-
From: Tom Brown [mailto:[EMAIL PROTECTED]
Sent: 19 June 2003 17:18
To: Kevin
> I had to rip my drive out to change some dip switches - have a look at the
> spec for the drive before you do anything as drastic as that.
I have used Joshua's suggestion of putting a mt -f /dev/nst0 compression 0
at the very top of my script that runs amdump.
So far so good
Tom
I had to rip my drive out to change some dip switches - have a look at the
spec for the drive before you do anything as drastic as that.
HTH
Kevin
-Original Message-
From: Tom Brown [mailto:[EMAIL PROTECTED]
Sent: 19 June 2003 16:57
To: Joshua Baker-LePain
Cc: Jon LaBadie; [EMAIL PROTECTE
On Thu, 19 Jun 2003 at 4:57pm, Tom Brown wrote
> > ISTR you saying this is Linux? If so, then 'mt compression 0' should do
> > it. You can check the status by pointing 'tapeinfo' (from the mtx
> > distribution) at the generic device associated with your tape drive.
>
> It is linux yes - will am
> ISTR you saying this is Linux? If so, then 'mt compression 0' should do
> it. You can check the status by pointing 'tapeinfo' (from the mtx
> distribution) at the generic device associated with your tape drive.
It is linux yes - will amanda use this command before writing to this device
when a
I've got a bit of a strage issue here. All tapes have been labelled and i
did a couple of test runs with all disks in the disklist commented out so it
just ran through its cycle and all 7 tapes were fine.
that was yesterday
today doing an amcheck i am told that tape01 is not am amanda tape when i
I couldn't find this one in the list archvies, so here it is.
I'm using 40GB DLT tapes (according to the label). Despite what the comment produced
says, I used the non-compressed device. I didn't give it an estimate for the tapesize.
Writing 256 Mbyte compresseable data: 34 sec
Writing 256 Mb
On Thu, 19 Jun 2003 at 4:46pm, Tom Brown wrote
> > Fuji's documentation for tapes shows two IBM models, the rated
> > speeds for the models are 7.5 and 15 MB/s.
> >
> > Your 12.9 seems reasonable. Far cry from the previous 2.9 :)
> >
> > Is the comment correct, was HW compression ON? Should not
> Fuji's documentation for tapes shows two IBM models, the rated
> speeds for the models are 7.5 and 15 MB/s.
>
> Your 12.9 seems reasonable. Far cry from the previous 2.9 :)
>
> Is the comment correct, was HW compression ON? Should not have been.
> A tapetype report should show the "native" capa
On Thu, Jun 19, 2003 at 03:21:12PM +0100, Tom Brown wrote:
> > > Possibly rerun amtapetype (as Paul suggested) with an reasonable
> estimate
> > so
> > > that it writes 100x fewer separate files and writes much larger files
> that
> > > stream for a longer time at full write speed.
> > >
> > > From
On Thursday 19 June 2003 08:44, Michael Packer wrote:
>I'm trying to break up a large disk into smaller sections when it
> does a backup.. I tried:
>
>localhost /sda5/other sda5 {
> exclude "./files"
> exclude "./snap"
> exclude "./web"
> always-full
>} 1
>
>but that doesn't
> > Possibly rerun amtapetype (as Paul suggested) with an reasonable
estimate
> so
> > that it writes 100x fewer separate files and writes much larger files
that
> > stream for a longer time at full write speed.
> >
> > From amanda's perspective it doesn't matter. The speed parameter is
> > printe
Michael Packer wrote:
I'm trying to break up a large disk into smaller sections when it does a
backup.. I tried:
localhost /sda5/other sda5 {
exclude "./files"
exclude "./snap"
exclude "./web"
always-full
} 1
You are using amanda 2.4.3 or above, I presume.
Is your bas
I'm trying to break up a large disk into smaller sections when it does a
backup.. I tried:
localhost /sda5/other sda5 {
exclude "./files"
exclude "./snap"
exclude "./web"
always-full
} 1
but that doesn't seem to be working how can I tell it to exclude those
three di
I can't flush data and amstatus reports 0% data.
I forgot to say this is:
redhat-release-8.0-8
amanda-2.4.3-2 ( built by myself )
The tape is: Vendor: HP Model: C1537A
tapetype HP-DAT3
I can't flush data and amstatus reports 0% data.
I got a server that someone forgot to load the tapes in.
So, the holding disk growed to 100%. Then I came to make
some flushing of the data. There are a lot of days
waiting to be flushed. One of them I thought it didn't
fit in the tape, so I wanted
its on Linux - and there is the scsi command to disable hardware compression
but thats before each write isn't it?
NTW i'm running amtapetype again with the estimate option.
so far we are at...
$ amtapetype -e 100gig -f /dev/nst0
Writing 1024 Mbyte compresseable data: 47 sec
Writing 1024 Mbyt
Tom Brown wrote:
do you know what settings on the drive can effect this? Its preyy much as it
was shipped. I'm investigating how to disable hardware compression but so
far the vendor has not supplied the required information.
That depends on the OS. Solaris? Linux? VMS? Dos?
(There are usually a
Gregor Ibic wrote:
round 13000kps
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Tom Brown
what kind of speed should it be and how can i increase this write speed?
That depends on your overall system. (bus, scsi host adapter etc, cpu)
The marketing 12Mbytes
I first taped some jobs with amanda and check the speed of the unit.
But Im not sure if speed parameter is used anyway.
regards,
gregor
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Tom Brown
Sent: Thursday, June 19, 2003 12:58 PM
To: Gregor Ibic; AMANDA
do you know what settings on the drive can effect this? Its preyy much as it
was shipped. I'm investigating how to disable hardware compression but so
far the vendor has not supplied the required information.
thanks
Tom
> round 13000kps
>
> regards,
> gregor
>
>
> -Original Message-
> Fr
round 13000kps
regards,
gregor
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Tom Brown
Sent: Thursday, June 19, 2003 12:31 PM
To: Gregor Ibic; AMANDA Users
Subject: Re: LTO1 tapetype
what kind of speed should it be and how can i increase this write spee
what kind of speed should it be and how can i increase this write speed?
> speed should be much higher
>
> regards,
> gregor
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> Behalf Of Tom Brown
> Sent: Thursday, June 19, 2003 11:37 AM
> To: Paul Bijnens
> Cc:
Toralf
anything in the /var/log/messages file (oe where ever the file lives).
Nothing related to the tape write operation there, I'm afraid...
what tape info (device etc) are you using in the amanda.conf
tpchanger "chg-zd-mtx"
tapedev "/dev/nrtape"
rawtapedev "/dev/tape"
(Yep, I have a changer, t
speed should be much higher
regards,
gregor
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Tom Brown
Sent: Thursday, June 19, 2003 11:37 AM
To: Paul Bijnens
Cc: AMANDA Users
Subject: Re: LTO1 tapetype
its finished!
define tapetype unknown-tapetype {
its finished!
define tapetype unknown-tapetype {
comment "just produced by tapetype prog (hardware compression on)"
length 104017 mbytes
filemark 532 kbytes
speed 2894 kps
}
does that look right for LTO1?
Tom
> Tom Brown wrote:
> > I didn't give it an estimate no - If i were to
Tom Brown wrote:
I didn't give it an estimate no - If i were to would i estimate the
'uncompressed' capacity, in this case 100gig?
yes.
I'm loathed to stop it now as its been running since yesterday afternoon and
is currently
Estimated time to write 2 * 1024 Mbyte: 174 sec = 0 h 2 min
This means t
Hello,
When I tried to labeled I had this error message :
amlabel robot DLT_02
labeling tape in slot 2 (/dev/nst0):
rewinding, reading label DLT_02
rewinding, writing label DLT_02, checking labelSegmentation fault
When I looked in the log file I found this log file :
chg-zd-mtx-stk-9730: debu
I didn't give it an estimate no - If i were to would i estimate the
'uncompressed' capacity, in this case 100gig?
I'm loathed to stop it now as its been running since yesterday afternoon and
is currently
Estimated time to write 2 * 1024 Mbyte: 174 sec = 0 h 2 min
wrote 3167649 32Kb blocks in 9687
Tom Brown wrote:
Does anyone have a tapetype for this drive? I'm running amtapetype but its
been running for about 20 hours and has not yet finished!
Did you specify an estimate for the capacity? This speeds the
process up considerably.
amtapetype -e 40g ...
The default estimate is 1Gbyte.
Does anyone have a tapetype for this drive? I'm running amtapetype but its
been running for about 20 hours and has not yet finished!
The drive is a
Vendor: IBM Model: ULTRIUM-TD1 Rev: 1CSG
thanks
Tom
Toralf
anything in the /var/log/messages file (oe where ever the file lives).
what tape info (device etc) are you using in the amanda.conf and do you
use the same one when doing other dumps? Have you tried dd -ing to the
device etc..
--
Martin Hepworth
Senior Systems Administrator
Solid Stat
Just got
*** A TAPE ERROR OCCURRED: [[writing file: I/O error]].
during a backup run. - Must be something wrong with the tape or tape
drive, I thought, but it turns out that
1. I get this error for various different tapes when trying to amflush the
dump to them.
2. I can write other dumps to th
Steven M. Wilson wrote:
That could very well be the problem I'm having since I just tried a df
on the client system and it ground to a halt trying to located NFS
mounts. We rely heavily on NFS here so I'll need to figure out how to
get around this problem in the future. Thanks for the info.
What is the right and proper way to unschedule the dump of a DLE? I
thought the answer would be "amadmin delete, then remove DLE from
disklist", but it seems to me that this will prevent me from amrecover'ing
the DLE from existing backups, which is something I want to be able to do.
Notice that
The addition of "autoflush" option in 2.4.3 was really very helpful, but
I'm still not satisfied. What I really want, is to autoflush when one or
two smallish DLE dumps are left on the holding disk, but not if the entire
taper operation failed due to tape error or something.
Comments?
--
- Tora
60 matches
Mail list logo
