I don't know if this is the correct list to post this to but...
I ran tapetype on the following drivves:
define tapetype adr50 {
comment OnStream Model: ADR50 Rev: 2.39
length 21077 mbytes
filemark 29 kbytes
speed 547 kps
}
define tapetype vxa1 {
comment ECRIX Model: VXA-1
P.S. I failed to take HW compression into account in the entries
below. I have changed them as follows:
define tapetype adr50 {
comment OnStream Model: ADR50 Rev: 2.39 w/HW Compression
length 42000 mbytes
filemark 29 kbytes
speed 547 kps
}
define tapetype vxa1 {
comment
On Fri, 18 Jan 2002 at 10:10am, Robert Kearey wrote
It seems that the setup I've inherited has no indexing enabled, and
I'm at a loss to understand why given the advantages. Is there some
compelling reason to have indexing off? Can I just turn it on?
Not really. Yes.
About the only
Good morning,
I'm trying to dump a file system /opt, its contains is this
#ls
BSCW3 SUNWahwja SUNWrtvcbackonline
S SUNWconnSUNWsymon lanman
SUNWAhwde SUNWdat SUNWvts lost+found
SUNWAhwes
[EMAIL PROTECTED] schrieb:
Hi,
When i execute this
amrecover sethost frostis.cf.jcyl.es
200 Dump host set to frostis.cf.jcyl.es.
amrecover ls
Must select a disk before listing files
amrecover setdisk /dev/dsk/c0t0d0s3
200 Disk set to /dev/dsk/c0t0d0s3.
amrecover history
200- Dump
On 18 Jan 2002 at 2:15pm, [EMAIL PROTECTED] wrote
Load tape DGQ974 now
Continue? [Y/n]: Y
EOF, check amidxtaped.debug file on wendy.
Did you check amidxtaped.debug on wendy? It's in /tmp/amanda.
Can you see the data on the tape via mt/dd? There are instructions in
docs/RESTORE.
--
I don't know if this is the correct list to post this to but...
Thanks for posting the information.
The correct place to do this is on the FAQ at www.amanda.org. You
can add your own entries there.
BTW, you might want to look through the mailing list archives (also
linked from the Amanda web
This would be a more accurate test:
dump 0sf 1048576 - /dev/sda5 | (restore -tvf - ; cat /dev/null)
Suprisingly that ran fine:
Not terribly surprising, but it shows the dump - restore pipeline is
not the problem. Now try this:
/sbin/dump 0sf 1048576 - /dev/sda5 | /bin/gzip -dc | cat
EUREKA! Thanks, Mark! Your script is working like a charm.
Jenn
Mark Holm wrote:
AIT and DLT tape drives take longer to come on-line than the original
chg-*-mtx scripts expected. I have attached the version that I modified to
work with my QualStar that has a wait loop built in to get past
You're right. I wasn't thinking... I guess it should be:
define tapetype V10 {
comment V10 in ECRIX Model: VXA-1 Rev: 2959 w/HW compression
length 55000 mbytes
filemark 1931 kbytes
speed 2024 kps
}
define tapetype vxa1 {
comment ECRIX Model: VXA-1 Rev: 2959
John R. Jackson wrote:
This would be a more accurate test:
dump 0sf 1048576 - /dev/sda5 | (restore -tvf - ; cat /dev/null)
Suprisingly that ran fine:
Not terribly surprising, but it shows the dump - restore pipeline is
not the problem. Now try this:
/sbin/dump 0sf 1048576
It is my understanding that this drive was delivered with HW compression
enabled. I have done nothing to disable it.
After visiting their web site I see the problem...
The tape is a V17. I did not recall, so I simply assumed that when you
mentioned the V10, that it must have been the correct
Robert Kearey wrote:
It seems that the setup I've inherited has no indexing enabled, and
I'm at a loss to understand why given the advantages. Is there some
compelling reason to have indexing off? Can I just turn it on?
I have indexing enabled but I never make use of it. I'm either
13 matches
Mail list logo
