Re: Restoring a client root partition
John W. Price [EMAIL PROTECTED] writes: Hi all: I am trying to learn how to restore a backup with amanda (v2.4.2p2). I am using my laptop (running linux) as a guinea pig for this, under the assumption that if it doesn't work, I haven't lost too much. As I'm planning to use this to upgrade my laptop disk to a larger disk (i.e., use amanda to back up the smaller disk, install the larger disk, and restore), this assumption seems valid. My laptop disk has three main partitions: /boot, swap, and /. I created backup images of /boot and /, then swapped the disks. At this point, the RESTORE file in /usr/local/amanda-2.4.2p2/docs says (under client machine fails, system critical disk): ...boot off the CD, and reinstall the system critical partition, restoring it to vendor supplied state. Does this mean: 1. Use fdisk or a similar program to *create* the partition? If so, then how to I get this computer (which currently has no networking capability) to restore the files? Yes, if you use tar doing the grunt work for Amanda. Partition size does not matter (as long as all data fits in). It may be different if you use dump. As it essentially backs up Inodes it may cause trouble if you don't have an identical replacement disk. 2. Restore the entire /boot partition from the CD? If so, this is also suboptimal, since the boot files have changed since the CD was burned (kernel upgrades and such). Most likely, I'm missing something simple here, but I haven't done this enough to know yet what that is. I'd like to find out, however, before I need to know... You just need a network connection to get at the data to restore and to access the amanda binaries. This prelimary installation is overwritten by the restore procedure. AFIK you could even use a rescue system in RAM with network and disk/(tape) support for your hardware. Johannes Niess
Re: Restoring a client root partition
Hi, the steps to do are (i think, correct me someone if I'm wrong) 1.) have a rescue-disk/cd with a minimal linux-system that supports your network-hardware, and the amanda-client utilities needed for restore. 2.) boot with this medium, 3.) configure your networkinterface to be able to connect to your amanda-server 4.) re-create your partititions, and mount them somewhere 5.) use the amanda-tools to reach out to your amanda-server and get your data back to the new partititions. 6.) make the system bootable 7.) reboot and you should be in buisines Hope it helps Christoph John W. Price schrieb: Hi all: I am trying to learn how to restore a backup with amanda (v2.4.2p2). I am using my laptop (running linux) as a guinea pig for this, under the assumption that if it doesn't work, I haven't lost too much. As I'm planning to use this to upgrade my laptop disk to a larger disk (i.e., use amanda to back up the smaller disk, install the larger disk, and restore), this assumption seems valid. My laptop disk has three main partitions: /boot, swap, and /. I created backup images of /boot and /, then swapped the disks. At this point, the RESTORE file in /usr/local/amanda-2.4.2p2/docs says (under client machine fails, system critical disk): ...boot off the CD, and reinstall the system critical partition, restoring it to vendor supplied state. Does this mean: 1. Use fdisk or a similar program to *create* the partition? If so, then how to I get this computer (which currently has no networking capability) to restore the files? 2. Restore the entire /boot partition from the CD? If so, this is also suboptimal, since the boot files have changed since the CD was burned (kernel upgrades and such). Most likely, I'm missing something simple here, but I haven't done this enough to know yet what that is. I'd like to find out, however, before I need to know... John -- John Price *** ** ** *** [EMAIL PROTECTED] Where there is no solution, there is no problem. -- John G. Price (my father), ca. 1975.
Re: Restoring a client root partition
I use the Super Rescue CD to do amanda restores. It's basically a Redhat 7.0 installation on a single CD. It includes the normal Amanda tools and ssh. You just boot up the system with the CD, get the networking going, and then use SSH and Amrestore to bring the data over from the amanda server to the local machine. Works great. It also comes with some semi-functional scripts for rebuilding the CD with your own changes thrown in. The scripts needed a little massaging to get them to work properly but it's possible. http://www.kernel.org/pub/dist/superrescue/v2/ Johannes Niess wrote: John W. Price [EMAIL PROTECTED] writes: Hi all: I am trying to learn how to restore a backup with amanda (v2.4.2p2). I am using my laptop (running linux) as a guinea pig for this, under the assumption that if it doesn't work, I haven't lost too much. As I'm planning to use this to upgrade my laptop disk to a larger disk (i.e., use amanda to back up the smaller disk, install the larger disk, and restore), this assumption seems valid. My laptop disk has three main partitions: /boot, swap, and /. I created backup images of /boot and /, then swapped the disks. At this point, the RESTORE file in /usr/local/amanda-2.4.2p2/docs says (under client machine fails, system critical disk): ...boot off the CD, and reinstall the system critical partition, restoring it to vendor supplied state. Does this mean: 1. Use fdisk or a similar program to *create* the partition? If so, then how to I get this computer (which currently has no networking capability) to restore the files? Yes, if you use tar doing the grunt work for Amanda. Partition size does not matter (as long as all data fits in). It may be different if you use dump. As it essentially backs up Inodes it may cause trouble if you don't have an identical replacement disk. 2. Restore the entire /boot partition from the CD? If so, this is also suboptimal, since the boot files have changed since the CD was burned (kernel upgrades and such). Most likely, I'm missing something simple here, but I haven't done this enough to know yet what that is. I'd like to find out, however, before I need to know... You just need a network connection to get at the data to restore and to access the amanda binaries. This prelimary installation is overwritten by the restore procedure. AFIK you could even use a rescue system in RAM with network and disk/(tape) support for your hardware. Johannes Niess -- -- Aaron Smith vox: 616.226.9550 Network Directorfax: 616.349.9076 Nexcerpt, Inc. [EMAIL PROTECTED]
[OT] SDT-5000 DDS2 Tape drive
Hi, I'm sorry for this slightly OT question. As in subject, I've a SONY DDS2 tape drive with 90m DDS tapes which behaves in a very strange way. I've loaded a tape and issued: tar cvf /dev/nst0 /stuff tar doesn't complains. After, I rewind the tape, extract the archive and verified that data is stored correctly. Now comes the tricky part. If I eject the tape, Voila', the tape is unreadable. I get after loading the tape: mt -f /dev/nst0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN mt -f /dev/nst0 rewind (just to be sure) tar: /dev/nst0: Cannot read: Input/output error tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now mt -f /dev/nst0 status SCSI 2 tape drive: File number=0, block number=-1, partition=0. Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN I get same I/O error if issue mt fsf 1 from a rewound tape. If I overwrite the tape with a new tar i'm again able to read the content but unless tha tape in not ejected. Has anyon e seen this before? The same kernel/st handles properly an SLR-100. Needless to say that i face the same problem running amcheck. TIA for any suggestion(s), -m
FW: amrecover
AMRECOVER Version 2.4.2p2. Contacting server on mail.daml.org ... amrecover: Unexpected server end of file In addition to what Bernhard suggested, what's in amindexd*debug on mail.daml.org (in /tmp/amanda)? Brandon Amundson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] I am not getting a amindexd*debug written to tmp/amanda here is what is written and also a look at my inetd.conf . I have also viewed the article on faq o matic (http://amanda.sourceforge.net/cgi-bin/fom?file=173showLastModified=show) but found that it was not my problem, although it reports the same error. root@maills amandad.20010820110251.debug amrecover.20010817140841.debug killpgrp.20010815140839.debug amandad.20010820110317.debug amrecover.20010817145258.debug killpgrp.20010815140843.debug amandad.20010820110413.debug amrecover.20010820111008.debug killpgrp.20010815140851.debug amandad.20010820110447.debug amrecover.2001082054.debug killpgrp.20010815140859.debug amcheck.20010820103748.debug amrecover.20010820111217.debug killpgrp.20010815140911.debug amcheck.20010820103855.debug amrecover.20010820111235.debug killpgrp.20010815140918.debug amcheck.20010820104009.debug amrecover.20010820111612.debug selfcheck.20010820110251.debug amcheck.20010820105901.debug amrecover.20010820114613.debug selfcheck.20010820110447.debug amcheck.20010820110055.debug amrecover.20010820115545.debug sendbackup.20010815140926.debug amcheck.20010820110251.debug amrecover.20010820124828.debug sendbackup.20010815141552.debug amcheck.20010820110252.debug amtrmidx.20010815151904.debug sendbackup.20010815142516.debug amcheck.20010820110317.debug amtrmlog.20010815151904.debug sendbackup.20010815144439.debug amcheck.20010820110413.debug killpgrp.20010815140759.debug sendbackup.20010815151247.debug amcheck.20010820110447.debug killpgrp.20010815140809.debug sendbackup.20010815151403.debug amlabel.20010815123014.debug killpgrp.20010815140823.debug sendsize.20010815140759.debug amrecover.20010817140833.debug killpgrp.20010815140834.debug and a look inside amrecover .. root@mailmore amrecover.20010820114613.debug amrecover: debug 1 pid 19812 ruid 0 euid 0 start time Mon Aug 20 11:46:13 2001 amrecover: stream_client: connected to 4.22.162.122.10082 amrecover: stream_client: our side is 0.0.0.0.553 and the inetd.conf #AMANDA Network Backup Utility # amanda dgram udp wait amanda /usr/local/libexec/amandad amandad amandaidx stream tcp nowait amanda /usr/local/amanda/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/amanda/libexec/amidxtaped amidxtaped Thanks..
Proper procedure for archiving tapes
Hi, Amanda's been running smoothly for months now. It uses 6 tapes to back up our network. I was thinking it's about time to take a snapshot of the network, and preserve the current 6 tapes, and start using a new set of 6. The old ones can be an off-site backup. Here's what I was thinking of doing; I'd like some feedback if this is the best solution. 1. Get 6 more tapes, and amlabel them identically to the old ones: DailySet000 through DailySet005. 2. Wait a few days until I'm asked to insert tape DailySet000, then take the old DailySet000, pop it into my drawer, and instead insert the new blank DailySet000. Continue this process with DailySet001 through DailySet005. 3. Now my drawer is full of the old tapes, and I can take them home. Is this a good plan? --- Eric
Re: Proper procedure for archiving tapes
Hello... Eric Wadsworth wrote: Hi, Amanda's been running smoothly for months now. It uses 6 tapes to back up our network. I was thinking it's about time to take a snapshot of the network, and preserve the current 6 tapes, and start using a new set of 6. The old ones can be an off-site backup. Here's what I was thinking of doing; I'd like some feedback if this is the best solution. 1. Get 6 more tapes, and amlabel them identically to the old ones: DailySet000 through DailySet005. 2. Wait a few days until I'm asked to insert tape DailySet000, then take the old DailySet000, pop it into my drawer, and instead insert the new blank DailySet000. Continue this process with DailySet001 through DailySet005. 3. Now my drawer is full of the old tapes, and I can take them home. Is this a good plan? No. you will overwrite the database of which file to which tape. (I can't remember the correct file/term) What I would do is label the next six tapes DailySet0[06..11] run 'amadmin DailySet no-reuse DailySet00[0-5]' this means, don't reuse these then you could run amrecover and set the date to one that is on one of those tapes. On the next amdump run it will ask for DailySet006 ... Oh, the taking them home part _is_ good though :) --- Eric -- Christopher McCrory The guy that keeps the servers running [EMAIL PROTECTED] http://www.pricegrabber.com I don't make jokes in base 13. Anyone who does should get help. --Douglas Adams
Re: Amanda Question.
Hello... Brandon Amundson wrote: Hello, Do you run amanda on Linux or Solaris? I am having a problem using amrecover. I have sent it to [EMAIL PROTECTED] but not received an answer. Can you help? I run amanda on linux. check your '.amandahosts' on the _server_. make sure there is a host.domain root entry. Also check the forward and reverse DNS entries. IIRC, the .amandahosts file uses the FQDN and it _must_ match the reverse DNS. how are you (full line) calling amrecover? Brandon Amundson BBN Technologies LAB: 703 486 4567 Office: 703 486 4555 [EMAIL PROTECTED] -- Christopher McCrory The guy that keeps the servers running [EMAIL PROTECTED] http://www.pricegrabber.com I don't make jokes in base 13. Anyone who does should get help. --Douglas Adams
Re: [Amanda-users] [OT] SDT-5000 DDS2 Tape drive
maybe a retension would help! just a thought :-P On Wed, Aug 22, 2001 at 04:37:33PM +0200, Matteo Centonza wrote: Hi, I'm sorry for this slightly OT question. As in subject, I've a SONY DDS2 tape drive with 90m DDS tapes which behaves in a very strange way. I've loaded a tape and issued: tar cvf /dev/nst0 /stuff tar doesn't complains. After, I rewind the tape, extract the archive and verified that data is stored correctly. Now comes the tricky part. If I eject the tape, Voila', the tape is unreadable. I get after loading the tape: mt -f /dev/nst0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN mt -f /dev/nst0 rewind (just to be sure) tar: /dev/nst0: Cannot read: Input/output error tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now mt -f /dev/nst0 status SCSI 2 tape drive: File number=0, block number=-1, partition=0. Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN I get same I/O error if issue mt fsf 1 from a rewound tape. If I overwrite the tape with a new tar i'm again able to read the content but unless tha tape in not ejected. Has anyon e seen this before? The same kernel/st handles properly an SLR-100. Needless to say that i face the same problem running amcheck. TIA for any suggestion(s), -m ___ Amanda-users mailing list [EMAIL PROTECTED] http://mail.topic.com.au/cgi-bin/mailman/listinfo/amanda-users -- Jason Thomas Phone: +61 2 6257 7111 System Administrator - UID 0 Fax:+61 2 6257 7311 tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81 1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/
Re: [OT] SDT-5000 DDS2 Tape drive
Just a suggestion, having never seen a SDT-5000, can you do a status just after you've written it, and see what density code it thinks it is? You might need to set the density (mt setdensity on Linux) before you can read the tape(?!?) On Wed, 22 Aug 2001, Matteo Centonza wrote: Date: Wed, 22 Aug 2001 16:37:33 +0200 (CEST) From: Matteo Centonza [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [OT] SDT-5000 DDS2 Tape drive Hi, I'm sorry for this slightly OT question. As in subject, I've a SONY DDS2 tape drive with 90m DDS tapes which behaves in a very strange way. I've loaded a tape and issued: tar cvf /dev/nst0 /stuff tar doesn't complains. After, I rewind the tape, extract the archive and verified that data is stored correctly. Now comes the tricky part. If I eject the tape, Voila', the tape is unreadable. I get after loading the tape: mt -f /dev/nst0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN mt -f /dev/nst0 rewind (just to be sure) tar: /dev/nst0: Cannot read: Input/output error tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now mt -f /dev/nst0 status SCSI 2 tape drive: File number=0, block number=-1, partition=0. Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN I get same I/O error if issue mt fsf 1 from a rewound tape. If I overwrite the tape with a new tar i'm again able to read the content but unless tha tape in not ejected. Has anyon e seen this before? The same kernel/st handles properly an SLR-100. Needless to say that i face the same problem running amcheck. TIA for any suggestion(s),
RE: Solaris 8 Server hangs during backup
Bill, Thanks for your reply. We have done some more investigation and have determined that the problem is with sendbackup. It does ufsdump | sed | ufsrestore. When this starts it takes the CPU to 100% and stays there. The performance monitoring soon quits updating. Log messages indicate that sendmail sees the load average too high and quits processing the queue. The only recovery is to turn the machine off and back on. The data on the largest partition was slightly greater that 1 GB. We had 2 holding partitions, each slightly less than 1 GB. We tried combining the 2 partitions with DiskSuite to get a larger volume, but this did not fix the problem. The only patch on the web site for 2.4.2p2 seems to be for IRIS and TRU64, not Solaris. Eva Freer -Original Message- From: Bill Carlson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 15, 2001 10:16 AM To: Eva Freer Cc: [EMAIL PROTECTED] Subject: Re: Solaris 8 Server hangs during backup On Tue, 14 Aug 2001, Eva Freer wrote: We have a highly subnetted configuration of Solaris 8 and 2.6 boxes, mostly E220R's. The subnets are connected via firewalls. Each subnet has its own Amanda server with an Exabyte Mammoth tape drive. We use hardware compression only. The Amanda is 2.4.2p1 on most nodes. Originally, we seemed to have a problem with only one subnet, with a Solaris 2.6 server, 2 Solaris clients, and 1 Solaris 8 client. The server would hang during the backup and required a poweroff reboot. Part of the backup would !?! I've never seen anything with amanda that actually killed the machine. A heavily overloaded machine will seem dead, but should eventually respond. The problem now affects at least 2 of the subnets. In both cases, the Amanda server is Solaris 8 with 1 Solaris 8 client and 2 Solaris 2.6 clients. One server hangs every night while the other is intermittent. Both are configured to use 2 ~1 GB holding partitions. Eliminating the holding partitions did not prevent the hangup. The largest disk backed up contains slightly more than the capacity of 1 of the holding partitions. The server How full is the largest partition? For holding disk purposes, the important part is how much actual data you have, not the size of the filesystem. than the usual OS stuff. The 2.6 clients are dual processor Sun E220R webservers with no activity during the backup period. The 8 client and server are single processor E220R LDAP servers with no activity during the backup period. Perfmeter analysis indicates that the CPU usage goes to 100% shortly after the backup starts and stays there. Do you have debug turned on for all clients and servers? The first thing I'd want to see is the debug output and then the actual logs. When the CPU starts spinning at 100%, what process is the culprit? We need more info here. Are you using ufsdump or tar? Any patches to amanda? Bill Carlson -- Systems Programmer[EMAIL PROTECTED] | Anything is possible, Virtual Hospital http://www.vh.org/ | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. |
No Subject
Hi I have just installed Amanda 2.42 on a Linux server running Red Hat 7.1. I have done the configuration and followed the instruction provided as best as possible. I am having a problem it trying to label a tape drive and I keep getting this error amlabel dailyset dailyset111 rewinding, reading label, not an amanda tape rewinding, writing label, daily111 checking label amlabel o label found are you sure /dev/st0 is non rewinding the tape drive is a quantum dlt2000 attached to scsci id 0 I have looked up the man pages for amlabel and there was a error description for the above and it says its might haveto do with misconfiguring Amanda with a rewinding tape device instead of a non-rewinding device name fortape How do I check this. Thanks Chandra
unsubscribe
please can someone tell me the website to unsubscribe from t he list? thank you,
Qualstar TLS-4220 problems
Hi everyone! I am a new Amanda user and am trying to get it setup and
working. I am setting up my backup machine which is configured as follows:
K6-3 500Mhz w/256Mb of Ram
2 SCSI Hard Drives - 8Gb as a boot disk and a 34.6Gb as a
backup/data disk
iWill SIDE-2936UW-E SCSI Adapter
Qualstar TLS-4220 Tape Jukebox with 20 slots and 1 AIT-1 tape drive
I have made no patches to the operating system as it was distributed from
RedHat except to Run Bastille to harden it's security. The version of Amanda
I am running is 2.4.2p2 and is the compiled version from RedHat. I also
installed the mtx utility from the RedHat distribution as well.
The first thing I tried to do was interface the Jukebox with the system. It
comes up fine as SCSI id 1 for the Changer and SCSI id 4 for the tape drive.
RedHat configured them as /dev/st0 and /dev/sg3 respectively. I was able to
use the mtx utility to move the tapes around in the slots, out the I/O
Port, and in and out of the tape drive. I identified that I needed to eject
the tape from the drive as it was not automatically down when you told the
changer to move media out of the drive.
I started out trying to use the chg-scsi interface program as the control
for the tape drive, but have found that any time that I had to do a tape
eject, and then move, such as telling it to label a second tape after it
already had one in the tape drive, it would lock up the jukebox. Sometimes I
could do a mtx unload command and clear it, but sometimes it required a
complete reboot of the system just to release the command.
I then shifted to the chg-mtx script, and after porting it to recognize
RedHat 7.1 and the Qualstar, found I had a similar problem, without the
lockup. If you issue an amlabel command designating a slot, it will move the
tape into the drive, drive would stabilize (all lights appropriately green),
then tell me that the tape was not on-line. Issue the command again and it
would complete without error. Issue it again with another slot defined and
it would switch tapes and again tell me the tape was off-line. Rinse and
repeat. If I scripted in a whole list of commands to happen one right after
the other, essentially issue amlabel twice for each slot, it will move the
tapes, but gives I/O errors every time it tries to rewind or write to the
tape. It appears as if the changer mechanism and the tape drive are not
releasing the SCSI bus in a timely manner to allow the commands to complete
when you switch devices.
Has anybody else seen this behavior? How do I fix it? Does anybody else have
a Qualstar working with Amanda on RedHat 7.1?
I am attaching my amanda.conf, chg-scsi.conf, and the modified chg-mtx
script in case anybody needs to see them.
Any help appreciated!
markh
===
Mark A. Holm - Director of Network Engineering Operations
Inherent.com, Inc.
2140 SW Jefferson St. Phone: (503) 224-6751
Suite 200 extension 236
Portland, OR 97201 Fax: (503) 224-8872
http://www.inherent.com mailto:[EMAIL PROTECTED]
amanda.conf chg-mtx chg-scsi.conf
begin 600 amanda.conf
M(PT*(R!A;6%N9$N8V]N9B`M('-A;7!L92!!;6%N9$@8V]N9FEG=7)A=EO
M;B!F:6QE+B`@5AIR!S=%R=5D(]F9B!L:69E(%S#0HC(`@(`@(`@
M(`@(`@=AE(%C='5A;!C;VYF:6@9FEL92!I;B!UV4@870@0U,N54U$
M+D5$52X-B,-B,@268@6]UB!C;VYF:6=UF%T:6]N(ES(-A;QE9P@
MV%Y+`B8W-D(BP@=AE;B!T:ES(9I;4@;F]R;6%L;'D@9V]EPT*(R!I
M;B`O971C+V%M86YD82]CV0O86UA;F1A+F-O;F8N#0HC#0H-F]R9R`B26YH
M97)E;G0N8V]M(@D)(R!Y;W5R(]R9V%N:7IA=EO;B!N86UE(9OB!R97!O
MG1S#0IM86EL=\@(F)A8VMU'-`:6YH97)E;G0N8V]M(@D)(R!S%C92!S
M97!AF%T960@;ES=!O9B!O5R871OG,@870@6]UB!S:71E#0ID=6UP
M=7-EB`B86UA;F1A(@DC('1H92!UV5R('1O(')U;B!D=6UPR!U;F1E@T*
M#0II;G!AF%L;5L(#0)2,@;6%X:6UU;2!D=6UP97)S('1H870@=VEL;!R
M=6X@:6X@%R86QL96P-FYE='5S86=E(`V,#`@2V)PPDC(UAEM=6T@
M;F5T()A;F1W:61T:!F;W(@06UA;F1A+!I;B!+0B!P97(@V5C#0H-F1U
M;7!C6-L92`R('=E96MS2,@=AE(YU;6)EB!O9B!D87ES(EN('1H92!N
M;W)M86P@9'5M!C6-L90T*G5NW!EF-Y8VQE(#$P(`DC('1H92!N=6UB
M97(@;V8@86UD=6UP(')U;G,@:6X@9'5M-Y8VQE(1A7,-G1A5C6-L
M92`R,!T87!EPDC('1H92!N=6UB97(@;V8@=%P97,@:6X@F]T871I;VX-
M@D)2,@-!W965KR`H9'5M-Y8VQE*2!T:6UER`U('1A5S('!EB!W
M965K(AJ=7-T#0H)0DC('1H92!W965K9%YRD@QUR!A(9E=R!T;R!H
M86YD;4@97)R;W)S('1H870-@D)2,@;F5E9!A;69L=7-H(%N9!S;R!W
M92!D;R!N;W0@;W9EG=R:71E('1H92!F=6QL#0H)0DC()A8VMU',@5R
M9F]R;65D(%T('1H92!B96=I;FYI;F@;V8@=AE('!R979I;W5S#0H)0DC
M(-Y8VQE#0HC(R,@(R,C(,C(PT*(R!705).24Y'.B!D;VXG=!UV4@8EN
M9B@9F]R('1A5C6-L92P@:70GR!BF]K96XA#0HC(R,@(R,C(,C(PT*
M#0IB=6UPVEZ92`R,!-8@D)(R!M:6YI;75M('-A=FEN9W,@*'1HF5S:]L
M9D@=\@8G5M!L979E;`Q(T^(#(-F)U;7!D87ES(#$)2,@;6EN:6UU
M;2!D87ES(%T(5A8V@@;5V96P-F)U;7!M=6QT(#0)2,@=AR97-H;VQD
M(#T@8G5M'-IF4@*B!B=6UP;75L=%XH;5V96PM,2D-@T*971I;65O=70@
M,S`P0DC(YU;6)EB!O9B!S96-O;F1S('!EB!F:6QEWES=5M(9OB!E
MW1I;6%T97,N#0HC971I;65O=70@+38P,`D)(R!T;W1A;!N=6UB97(@;V8@
MV5C;VYDR!F;W(@97-T:6UA=5S+@T*(R!A('!OVET:79E(YU;6)EB!W
configuration
Is it me or is amanda a little short on documentation? What is the best source to get it up and running? Ken
Re:
In your amanda.conf file, change tapedev to the non-rewinding device, /dev/nst0: tapedev /dev/nst0 Ryan From: chandra [EMAIL PROTECTED] Hi I have just installed Amanda 2.42 on a Linux server running Red Hat 7.1. = I have done the configuration and followed the instruction provided as = best as possible. I am having a problem it trying to label a tape drive = and I keep getting this error amlabel dailyset dailyset111 rewinding, reading label, not an amanda tape rewinding, writing label, daily111=20 checking label amlabel o label found are you sure /dev/st0 is non rewinding the tape drive is a quantum dlt2000 attached to scsci id 0 I have looked up the man pages for amlabel and there was a error = description for the above and it says its might have to do with = misconfiguring Amanda with a rewinding tape device instead of a = non-rewinding device name for tape=20 How do I check this. Thanks Chandra
Re: [Amanda-users] unsubscribe
www.amanda.org On Wed, Aug 22, 2001 at 09:30:23PM -0400, rek2 wrote: please can someone tell me the website to unsubscribe from t he list? thank you, -- Jason Thomas Phone: +61 2 6257 7111 System Administrator - UID 0 Fax:+61 2 6257 7311 tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81 1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/
RE: configuration
There is actually a really good write-up online or you can purchase the O'Reilly Book Unix Backup Recover. It was enough for me to at least get started... markh -Original Message- From: Ken [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 22, 2001 6:44 PM To: amanda-users Subject: configuration Is it me or is amanda a little short on documentation? What is the best source to get it up and running? Ken
No Subject
I have progressed from tape labeling to amcheck. At the moment I am using root as a backup user for testing just to get it right. I have done the entries for services and xinetd.conf and restart xinetd. Now when I run amcheck I get the following error. ERROR: localhost: [access as amanda not allowed from root@localhost]amandahostauth failed The reason I am using root as a testing is because I cannot get to do the test as amanda su amanda "amcheck DailySet" comes up with error Chandra
