On Fri, 24 Aug 2001 [EMAIL PROTECTED] wrote:
> When Amanda (2.4.2+) uses a changer script/program, it first calls it with
> the "-info" option. One of the pieces of information Amanda is looking for
> is whether the changer is "searchable". If the changer indicates that it is
> searchable, Ama
Hi all. Posted this a few days ago but got no replies so I'll try again
with the hope that my message just didn't get through the first time.
I've compiled and been running amanda 2.4.2p2 on hp-ux 10.20 and 11.0
for some time with no probs. But now that we have a new file server with
hp-ux 11i (1
Mark Holm wrote:
[...]
> I am going to have to dig into the source to see how
> it passes parameters to the changer script when two drives are defined.
> Experimentation is now in order, unless of course you are already using your
> Qualstar with Amanda and have a working script?
Actually, my l
John W. Price <[EMAIL PROTECTED]> wrote:
> amrecover: amandaidx/tcp unknown protocol
something is missing in your /etc/services.
On Fri, 24 Aug 2001 [EMAIL PROTECTED] wrote:
> Storage Element 1:Full :VolumeTag=DLT000
> Storage Element 2:Full :VolumeTag=DLT001
> Storage Element 3:Full :VolumeTag=DLT002
Now this is interesting. Do you know anything about these VolumeTag
fields? I haven't seen this befo
Ben,
Thanks. I see the difference now in the listing and should have before as
well. The tapes are listed as Data Transfer Elements (DTE) and the slots are
Storage Elements (SE), so the numbering does overlap some. The part I was
overlooking is that the MTX program defaults to drive 0 (DTE 0) and
Hi all:
I've been backing up my system with amanda for the last week, and now
I'm doing the acid test: I'm trying to restore the backup to my laptop
computer, having upgraded to a larger disk. The backups seem to go
fine, according to the reports I've been getting. However, the restore
isn't go
> Unless I miss my guess, when the second drive is added it will show up as 1
> and the rest of the slots will move up one. MTX currently identifies the
> tape drive as slot 0, the holding slots as 1-20, the cleaning cartridge
> slots as 21-22, and the I/O port as 23. The only other option would
unsubscribe amanda-users
In a message dated: Fri, 24 Aug 2001 10:06:25 CDT
[EMAIL PROTECTED] said:
>> Can anybody tell me if amanda supports backup images larger than the tape
>> drive.
>
>No, it does not. The feature is being actively worked on, but no working
>code exists as of yet.
>
>Of course, the fact that it ha
Your welcome. I am now starting down the path of making it actually backup
something and immediately stepped into the morass of tight permissions (even
trying local), sigh! That's the hurdle for today...
As to the conflict, it might be as simple as setting up another check for
changer_online simi
Hello,
You wrote
> Can anybody tell me if amanda supports backup images larger than the tape
> drive. The readme file explicitly states that it does not, but then the
> file amanda-2.4.2p2/docs/Multitape talks about a need for this feature in
> version 2.2.
No, it does not. The feature is b
On Thu, 23 Aug 2001, Mark Holm wrote:
> Your hints were right on target. I converted your Perl to Bourne Shell and
> finished converting the script to work with the Qualstar. It is now working
> very well. Thank you!
Well, thank you! I was hoping to find time to tear into this next week
and c
ing strange.
I have looked too at the file amdump.1 and I have found this:
driver: send-cmd time 3.500 to taper: PORT-WRITE 00-1
volinux.ayto.es
/home/sanzm 0 20010824
driver: result time 3.500 from taper: PORT 1073
driver: send-cmd time 3.500 to dumper0: PORT-DUMP 01-2 1073
volinux.ayto.e
driver: send-cmd time 3.500 to taper: PORT-WRITE 00-1 volinux.ayto.es
/home/sanzm 0 20010824
driver: result time 3.500 from taper: PORT 1073
driver: send-cmd time 3.500 to dumper0: PORT-DUMP 01-2 1073
volinux.ayto.es /home/sanzm 0 1970:1:1:0:0:0 GNUTAR
|;bsd-auth;index;exclude-list=/usr/
15 matches
Mail list logo
