No Subject
unsubscribe
new tapes
Hi! I have here a tape-changer from Overland with 10 Tapes. All Tapes are labeled corectly (Daily00 - Daily09). All tapes are working fine, but safely i will change the tapes, call i will using new tapes. I put the tapes in the changer and i will label the tapes with amlabel. I will label the tapes Daily00 - Daily09 But amlabel brings an error: reading label label, tape is active Tape label appears to already be part of this Amanda configuration and active, i.e. has valid data on it. Can't i label the tapes exact the other tapes? Must i am using new names (Daily10 - Daily19) ? Bye Juergen
Re: amrecover problem
Hi John! extracting files using tapedrive 0 on host fileserver Note the tapedrive 0. That can't possibly the path to your tape drive. You probably need to put -d /dev/whatever on the amrecover command line. For security: My NoRewinding device ist /dev/nst0. Shall i take this device for my changer? When i take amrecover -d /dev/nst0 or amrecover -d /dev/st0 and i become the same error, but sorry, i forgot to post a message called: WARNING: not on root of selected filesystem, check man-page! I think the $CWD mount point is not set correct. The files will be restored in /drives/drives2/projekte/Online-Marketing/customer/april after checking from me. My mountpoint for the scsi drive are /dev/sdb1 /drives/drive2ext2defaults 1 2 /dev/sdc1 /drives/drive3ext2defaults 1 2 etc. When i go to /drives/drive2 and start amrecover, the Warning Message don't come and restore works (i hope so) When i go to /drives/drive2/Online-Marketing/customer/April the warning message is coming and the restore failed. Where must i go to use the right $CWD mount point? My idea is, a seperate directory for restore files, so that i can check the files after restoring before i move the files to the working directory. But this directory called restore is not a mount point. Thanks a lot and Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrecover problem
Am Mittwoch, 20. Juni 2001 22:17 schrieben Sie: Hi John! For security: My NoRewinding device ist /dev/nst0. Shall i take this device for my changer? It should be the tape device name. Whether it is also your changer device name depends on your hardware. When i take amrecover -d /dev/nst0 or amrecover -d /dev/st0 and i become the same error ... Using /dev/nst0 should have worked. I'm not sure I understood your last sentence. Did -d /dev/nst0 fail? What messages did you get? In particular (if it failed), what was in /tmp/amanda/amidxtaped*debug? sorry, i forgot to post a message called: WARNING: not on root of selected filesystem, check man-page! I think the $CWD mount point is not set correct. You didn't post the important message that comes out right before this: $CWD '/some/path' is on disk '/some/disk' mounted at /some/mount/point'. Seeing that would help understand the problem. That's fine. When i go to /drives/drive2 and start amrecover, the Warning Message don't come and restore works (i hope so) But the files replace the originals, right? right, but before it comes a warning message that the files exists. When i go to /drives/drive2/Online-Marketing/customer/April the warning message is coming and the restore failed. What do you mean by the restore failed? I don't no, amrestore is quiting with no comment. Where must i go to use the right $CWD mount point? When I do restores, I create a directory at the top of the file system that was backed up, e.g. /drives/drive2/.bkrest, then cd to there and start amrecover. If you cd to /drives/drive2/Online-Marketing/customer/April and run amrecover from there, files will be restored relative to that point. For instance, restoring Online-Marketing/customer/April/JJ would come back as: /drives/drive2/Online-Marketing/customer/April/Online-Marketing/customer/Ap ril/JJ which is probably not what you want (although you could rename it, of course). That's why I create the temp area at the top of the mount point so there is only one extra directory layer involved. well, i made a directory so you've written, i used the /dev/nst0 and the recovery is working fine. Thank you very much for your Info. That helps! Thanks a lot. Bye Juergen -- Dies ist eine Microsoft freie Mail!
amrecover problem
Hi! After a backup i need to restore some files from tape. I changed into a directory and give amrecover as root. Amrecover Version 2.4.2p2. Contacting Fileserver ... 200 DISK is set to sdb1 WARNING: not on root of selected filesystem, check man-page! amrecover is starting, i can select files to be restore, and than i said extract. extracting files using tapedrive 0 on host fileserver The following tapes are needed: Daily07 Restoring files in directory /home/amanda Continue [Y/n]: i pressed Y load Tape Daily07 now continue [Y/n]: i pressed Y EOF, check amidxtaped.debug file on fileserver amrecover: Can't read file header extract_list - child returned non zero status:1 Continue [Y/n]: i pressed Y amrecover Who can tell me what's wrong? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: Problem with device sg*
Hi! Host: scsi0 Channel: 00 Id: 08 Lun: 00 Vendor: QUANTUM Model: DLT8000 Rev: 0119 Type: Sequential-AccessANSI SCSI revision: 02 Here's a thought. Are you sure everything on that bus is wide SCSI? Yes! You cannot have ID's = 8 on narrow SCSI. Maybe somthing is wrapping that back around to SCSI ID zero? Hm... i have deinstalled the new harddrive and changed the config files and then i started all procedures to run the changer, but nothing. The same error. Well, i will make a new install from the Server ant than i will looking if amanda works fine. I think that i can make it next weekend. Aftert the new installation i will mailing you the result. Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: Problem with device sg*
Hi! Host: scsi0 Channel: 00 Id: 08 Lun: 00 Vendor: QUANTUM Model: DLT8000 Rev: 0119 Type: Sequential-AccessANSI SCSI revision: 02 Here's a thought. Are you sure everything on that bus is wide SCSI? yes, i'm shure, because the system was running before i installed a new scsi hard drive. BYe Juergen -- Dies ist eine Microsoft freie Mail!
Re: Problem with device sg*
Hi! I'm not sure where the problem is, so I suggest a few steps to find what's working and what's not. First see if the Tapedrive is found at all. Cat /proc/scsi/scsi and see if you find a device of type Sequential-Access like this: cat /proc/scsi/scsi brings: Host: scsi0 Channel: 00 Id: 08 Lun: 00 Vendor: QUANTUM Model: DLT8000 Rev: 0119 Type: Sequential-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 09 Lun: 00 Vendor: OVERLAND Model: LXB Rev: 0518 Type: Medium Changer ANSI SCSI revision: 02 root@fileserver:/var/log Then check if the st driver is loaded and has found the tapedrive. Make sure that the module is loaded (if st is a module, do a 'modprobe st') and check the kernel logs for something like: Detected scsi tape st0 at scsi0, channel 0, id 3, lun 0 st: bufsize 32768, wrt 30720, max init. buffers 4, s/g segs 16. This is a part of /var/log/boot.msg 4Detected scsi tape st0 at scsi0, channel 0, id 8, lun 0 6(scsi0:0:9:0) Synchronous at 20.0 Mbyte/sec, offset 15. 4 Vendor: OVERLAND Model: LXB Rev: 0518 4 Type: Medium Changer ANSI SCSI revision: 02 4Detected scsi generic sgh at scsi0, channel 0, id 9, lun 0 4scsi : detected 1 SCSI tape 1 SCSI cdrom 5 SCSI disks total. 4sr0: scsi3-mmc drive: 0x/0x caddy 6Uniform CDROM driver Revision: 2.56 Check if /dev/st0 and /dev/nst0 are correct: crw-rw1 root tape 9, 128 Jul 21 1998 /dev/nst0 crw-rw1 root tape 9, 0 Jul 21 1998 /dev/st0 ls -l /dev/nst* root@fileserver:/dev ls -l /dev/nst0 crw-r--r-- 1 amanda disk 9, 128 Apr 27 07:50 /dev/nst0 root@fileserver:/dev ls -l /dev/st0 crw-rw 1 root disk 9, 0 Nov 8 1999 /dev/st0 root@fileserver:/dev Run 'mt -f /dev/st0 status'. If this works all right (i.e. you don't get error messages like mt: /dev/st0: No such file or directory or /dev/st0: No such device or address) then the OS and the tapedrive are working fine and your problem is an Amanda problem :) mt -f /dev/st0 mt: /dev/st0: the device is busy (Das Gerät oder die Ressource ist belegt) root@fileserver:/dev Bevor i installed an new SCSI-Hard Drive, the system works fine. After this installation the system don't work. Is the device nst0 damaged? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: Problem with device sg*
Hi John! Hm...the tape haven't and hasn't SCSI ID 5 ... But earlier you said: Before i installed a new hard drive in the system (only scsi devices), the changer device was /dev/sg6 and the tape device was /dev/sg5. Yes, because i read that the first scsi device becomes the device /dev/sg0, the second device becomes sg1 etc. The SCSI-ID must not the same as the sg-device. Shit, i don't find the documentation for this. I mean, when only one scsi device is in the system with id 3, than it becomes the device /dev/sg0. Is the one SCSI-Device ID 1, it becomes /dev/sg0 Have you two scsi devices with SCSI-ID 2 and SCSI-ID 4 becomes the device with SCSI-ID 2 /dev/sg0 and the SCSI-Devie with SCSI-ID 4 /dev/sg1 In my System there was 4 HD's, one CD-ROM and the tape with the changer. The HD's have /dev/sg0 - /dev/sg3, the CD-ROM /dev/sg4 and the Tape /Dev/sg5 and the changer /dev/sg6. I took that to mean the tape drive used to be ID 5. Not that it really matters. The problem is that it doesn't work now. Right. I don't know enough about Linux to know where you find this out for sure (e.g. some boot time log messages or the like), but I suspect what might be happening is that the driver found something else it thought of as the first (zero'th) sequential access device and so 128 is the wrong minor number to have picked. You might try creating a few others (/dev/nst1, etc) per the man page and see if any of them will answer to a simple mt -f /dev/whatever rewind. Hm...at another Server i looked in the devices and there is 9 and 128 the Major and Minor numbers of /dev/nst0. The same is in the Doc from the devices. I will search for this dokument. So, i found it. The document is in the Kernel sources under /usr/src/linux/Documentation/devices.txt One other possibility is that when you added the disk the tape drive went dead (unable to be accessed by the st driver) for some reason. For instance, it's in the wrong place on the SCSI chain (narrow after wide, for instance), or termination is now wrong. That's less likely Hm..The System is a 19 Rack with only Mainboard, Grafik etc, and cd-Rom. in the second 19 Rack there are the HD's and the changer is an external device. All HD's are the same Model. since, if I understood correctly, you can do some simple (info) mtx things to it. Yes. Other than that, I think you need some real Linux help here. Until you can get /dev/nstN to work with normal mt commands, this is not really an Amanda issue. OK, i think you are right. John, i thank you very much for your Infos and your help. I will search for the error and i want write to you when the changer is running and when i know what the error is. Bye Juergen -- It's Friday!
Re: Problem with device sg*
Hi! But i have another Problem. I can't open the no-rewinding device /dev/nst0. So, are we just supposed to guess what error message you're getting??? Yes. as user amanda an ./amcheck Daily brings: amanda@fileserver:/usr/local/sbin ./amcheck Daily Amanda Tape Server Host Check - Holding disk /dumps/amanda: 1758764 KB disk space available, that's plenty After 10 Minutes i send a break with ctrl-c because there is no operating. I send the logfiles as a tar archive called logfiles.tar from /tmp/amanda Does it work if you do something like mt -f /dev/nst0 rewind as the Amanda user? How about some other user? as user amanda and as user root after typing mt-f /dev/nst0 rewind this error message is displayed: mt: /dev/nst0: Input-/output error Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: Problem with device sg*
Hi John! See above. Mtx status sends changer SCSI commands to a device (although info is a generic command all devices support). So you can't use mtx to talk to the tape drive except with some specific commands -- status isn't one of them, info probably is. OK, i understand. Is /dev/sg6 and /dev/nst0 the same, eg. the tape? They might end up talking to the same physical device, but you cannot use mtx (in general) to talk to /dev/nst0 and you cannot use mt to talk to /dev/sg6. Mt sends the tape driver ioctl's to do generic types of things (e.g. rewind). The driver translates those to the appropriate tape (SCSI, in this case) commands. Amanda (other than chg-scsi) needs a real tape device it can issue mt-like ioctl's to. So you've got to get /dev/nst0 fixed. Chg-scsi can issue raw SCSI commands to a device and bypass the st driver, which is why you give it the sg* names. So with Amanda and chg-scsi, you need both to work properly. OK, i think it's present, because amanda works fine bevor i installed a new hard disk. Put another way, the /dev/nst0 driver is at one level between an application and the tape device, the /dev/sg* driver is at the next level down (closer to the device): Application (e.g. mt or Amanda, other than chg-scsi) st driver sg driver physical device When i understand you, than is the application coressponding with the st driver, the st driver is coressponding with the sg driver and the sg driver is coressponding with the physical device. You said: as user amanda and as user root after typing mt-f /dev/nst0 rewind this error message is displayed: mt: /dev/nst0: Input-/output error ... I think the device /dev/nst0 is demaged. I agree that your /dev/nst0 entry might be wrong. It's probably still telling the tape driver to talk to SCSI ID 5, which is why it hung -- Hm...the tape haven't and hasn't SCSI ID 5, that's the CD-ROM. First, ID 0, ID1, ID 2, ID 4 are hard drives, ID 5 is the CD-ROM, ID 8 is the tape device and ID 9 is the Changer device. ID 7 is the adaptec. Now, i installed a new hard drive with ID 3 in the system, and from this moment amanda can't change the tapes. disk drives don't like to be told to rewind :-). I don't know how :-) you tell Linux to regenerate /dev entries. Maybe if you just remove (or rename would be safer) it, it will come back on the next reboot? No, i have removed the device /dev/nst0 and rebooted the system, but this device isn't come back, so that i must create it from hand. I made this with mknod /dev/nst0 c 9 128 but it don't work :-( Bye Juergen --- It's friday!
Re: Problem with device sg*
Am Mittwoch, 25. April 2001 16:47 schrieben Sie: Have you tried different devices ? What mtx -f /dev/sgX status says on them ? Also make sure the device is readable by amanda user. Problem is fixed, the major and minor numbers are not set correct. mtx is working fine, gives me the Information which slot ist loaded etc. But i have another Problem. I can't open the no-rewinding device /dev/nst0. Bye Juergen -- Dies ist eine Microsoft freie Mail!
Changer don't run after installing a new hard drive
Hi All! Amanda, Version 2.4.2-19991216-beta1, runs a lot of time very well. Now i have installed a new SCSI Hard Drive, and than i want to start amanda. But amanda don't run. Amanda Tape Server Host Check - Holding disk /dumps/amanda: 2095692 KB disk space available, that's plenty amcheck-server: could not get changer info: error could not read result from "/usr/local/libexec/chg-scsi" (got signal 11) Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.042 seconds, 0 problems found (brought to you by Amanda 2.4.2-19991216-beta1) amanda@fileserver:/usr/bin Who can help me? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: Changer don't run after installing a new hard drive
Am Mittwoch, 18. April 2001 19:10 schrieben Sie: Holding disk /dumps/amanda: 2095692 KB disk space available, that's plenty amcheck-server: could not get changer info: error could not read result from "/usr/local/libexec/chg-scsi" (got signal 11) Odds are excellent that you have set the SCSI ID of your new drive to the same as either the tape drive or the changer. Remember that the changer typically uses an ID different from the actual tape drive Another user found the error. The changer device ist /dev/sg6 and the new hard drive have an ID bevor the changer. Also the SG-Device is changed to /dev/sg7 (+1) Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Am Montag, 12. März 2001 09:25 schrieben Sie: Hi! Can't determine disk and mount point from $CWD amrecover What is wrong? In short NOTHING. When you start amrecover it assumes that you want to recover directly into your current working directory. You need to sethost, then setdisk. So, if I wanted to recover /usr on rebel.net.au I would do something like: amrecover sethost rebel.net.au [some response] amrecover setdisk /usr And continue... Yes, at a long time ago it works fine. I thank all the people who help me with this problem. Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Am Freitag, 9. Mrz 2001 16:10 schrieben Sie: Hi John! Should i make a fileserver.medienwerft.de root king.medienwerft.de root in the /home/amanda/.amandahosts, too? Yes. That's exactly what it's telling you. Thanks, thats good, working of amrecover will be better. OK, i have done it and start the amrecover and... root@fileserver:/usr/local/sbin ./amrecover Daily AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ... 220 fileserver AMANDA index server (2.4.2-19991216-beta1) ready. 200 Access OK Setting restore date to today (2001-03-12) 200 Working date set to 2001-03-12. 200 Config set to Daily. 200 Dump host set to fileserver. Can't determine disk and mount point from $CWD amrecover What is wrong? Bye Jeurgen
Re: amrestore problem
Am Freitag, 9. Mrz 2001 04:48 schrieben Sie: Hi! And I also said exactly what I thought was wrong, based on what you posted. However what you wrote in that letter is not the same as what Sorry, this mail didn't come to me! And some mails are more than once by me. you wrote in this one: These are better but still not correct. When you insert tcpd in an inetd.conf line, you also need to remove the "argv[0]" arg from the line. OK. So these should be: amandaidx stream tcp nowait amanda /usr/sbin/tcpd /usr/local/libexec/amindexd amidxtape stream tcp nowait amanda /usr/sbin/tcpd /usr/local/libexec/amidxtaped amanda dgram udp wait amanda /usr/sbin/tcpd /usr/local/libexec/amandad Note that the trailing "amindexd", "amidxtaped" and "amandad" are gone. Yes, i changed the lines so you given me. OK, thats fine. Amanda finds the Indexfile. AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ... 220 fileserver AMANDA index server (2.4.2-19991216-beta1) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed root@fileserver:/usr/local/sbin Hm...in my /home/amanda/.amandahosts are fileserver.medienwerft.de amanda king.medienwerft.de amanda In /etc/hosts are 10.0.1.50 fileserver.medienwerft.de fileserver 127.0.0.1 localhost Should i make a fileserver.medienwerft.de root king.medienwerft.de root in the /home/amanda/.amandahosts, too? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Am Montag, 5. März 2001 09:17 schrieben Sie: Hi! vi /etc/services /amandaidx amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp Is that correct? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
amandaidx stream tcp nowait amanda /usr/sbin/tcpd/ usr/local/libexec amidxtape stream tcp nowait amanda /usr/sbin/tcpd /usr/local/libexe amanda dgram udp wait amanda /usr/sbin/tcpd /usr/local/libexec Those cannot be right. First, there is a trailing '/' on "tcpd" for amandaidx. Next, all the lines end with "libexec", which is a directory, not a program. Hm...and what is the right way to change this parameters? Can you give me a tip? Bye Jeurgen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Hi! Huh? No output at all??? The file has 0 Bytes :-( ... What file? The amrecover program? Yes, and i don't know why amrecover has 0 Byte. Bu i have a copy :-) The first place to look is /tmp/amanda/amindexd*debug on the server. The result of this run is : amindexd: debug 1 pid 3228 ruid 560 euid 560 start time Thu Mar 1 09:14:29 2001amindexd: version 2.4.2-19991216-beta1 Is this ok or are you missing some? What does your inetd.conf line (or the config file for xinetd) look like for amandaidx? In /etc/inetd.conf : [...] amandaidx stream tcp nowait amanda /usr/sbin/tcpd/ usr/local/libexec amidxtape stream tcp nowait amanda /usr/sbin/tcpd /usr/local/libexe amanda dgram udp wait amanda /usr/sbin/tcpd /usr/local/libexec [...] That are the three lines for amanda. The index exists on the fileserver for the fileserver and the client: /usr/local/etc/amanda/index/fileserver/sdb1 /usr/local/etc/amanda/index/fileserver/sdc1 /usr/local/etc/amanda/index/fileserver/sdc1 /usr/local/etc/amanda/index/king/hdb1 That are the index directories for the Sever and the client. In this directories are files called 20010215_0.gz and so on. It's a compressed ASCII File with directories and filenames from the harddrive that i will be backed up. I had compiled and installed amanda in /usr/local/sbin and when i'm compiling and installing a new version af amanda i will install it in the same directory e.g. /usr/local/sbin must i remove the older files or will there be overwritten? They will be overwritten. That's fine. So i will install the newer Version of amanda when i have a little more time :-) Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Hi! Running with no Problems and give me: root@fileserver:/usr/local/sbin mt -f/dev/nst0 rewind root@fileserver:/usr/local/sbin dd if=/dev/nst0 bs=32k count=1 AMANDA: TAPESTART DATE 20010223 TAPE Daily04 The amrestore command is working fine ... I'm confused. You said it didn't work in previous letters. Are you now saying it does work, at least with this tape? Oh no, i'm confused. I changed the tape, rewinded it and type ./amrestore /dev/nst0 king hdb1 and amrestore is working, but amrestore writes all files into one file called king.hdb1.20010226.0 So i think it's working fine. root@fileserver:/usr/local/sbin ./amrecover AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ... amrecover: Unexpected server end of file First, look at /tmp/amanda/amindexd*debug on "fileserver" and see if it has anything to say. Also, what's in /tmp/amanda/amrecover*debug on this client? After typing amrecover i don't become an error but i don't become anything else. The Computer is working for a little time and then i have the cursor on the screen. Amrecover don't give me a message. Where must i start the recovery? On the Server or on the client? On the fileserver (Tapeserver) amrecover give me no output, and on the client (king) an amrecover gives me: root@King:/usr/local/sbin ./amrecover -C Daily -s fileserver -t fileserver AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ... amrecover: Unexpected server end of file root@King:/usr/local/sbin OK, the amrestore is working (not fine but working) and amrecover don't work. Some others. I'm using amanda 2.4.2-1991216-beta1. Is it ok to change to the newest Version of amanda? When yes, can i compile and install the new sources over the older version of amanda? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Hi! But, after rewinding the tape i become another error: root@fileserver:/usr/local/sbin ./amrestore /dev/nst0 king amrestore: WARNING: not at start of tape, file numbers will be offset This was right after a rewind? If so, then that's not an Amanda tape. Or it cannot be read. Try this with this tape: mt -f /dev/nst0 rewind dd if=/dev/nst0 bs=32k count=1 Running with no Problems and give me: root@fileserver:/usr/local/sbin mt -f/dev/nst0 rewind root@fileserver:/usr/local/sbin dd if=/dev/nst0 bs=32k count=1 AMANDA: TAPESTART DATE 20010223 TAPE Daily04 1+0 Records ein 1+0 Records aus root@fileserver:/usr/local/sbin This should display the Amanda label. Jepp, that is correct :-) I think i must change the tape because amanda uses two tapes per dump and at this moment the second tape is in the slot. Is this correct? You're correct that you have to have the right tape mounted before you run amrestore. But I think something else is wrong with your tapes. So, i think its a correct Tape in the slot, and i'm typing root@fileserver:/usr/local/sbin ./amrecover AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ... amrecover: Unexpected server end of file root@fileserver:/usr/local/sbin The amrestore command is working fine, but it is to hard to select some files that must be rerstored. I think amrecover is better, because it browse the Database for the files (and i can select the files i need?) that i need. But what an error is this? Bye Juergen
Re: amrestore problem
amanda@fileserver:~ cd /usr/local/sbin/ amanda@fileserver:/usr/local/sbin ./amrestore /dev/nst0 king amrestore: missing file header block Did you "mt -f /dev/nst0 rewind" first? i have forgotten :-( But, after rewinding the tape i become another error: root@fileserver:/usr/local/sbin ./amrestore /dev/nst0 king amrestore: WARNING: not at start of tape, file numbers will be offset root@fileserver:/usr/local/sbin I think i must change the tape because amanda uses two tapes per dump and at this moment the second tape is in the slot. Is this correct? BYe Juergen
Re: amreport Problem
Am Dienstag, 20. Februar 2001 00:22 schrieben Sie: Hi! If ./configure cannot find the right program (it looks for "Mail", "mailx" and "mail"), you can set the "MAILER" environment variable to a full path to a mail program that understands "-s subject user". When you're done, run "amadmin xx version | grep MAIL" and see what that says. It should point to the path Amanda will use. Hmafter typing this i see MAILER="/usr/sbin/sendmail" OK, can i change this without new compiling amanda? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Hi! root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king /dev/sg5 is a changer. The tape device is /dev/nst0, and that's what amrestore wants. OK, i tested it with this commands: amanda@fileserver:~ cd /usr/local/sbin/ amanda@fileserver:/usr/local/sbin ./amrestore /dev/nst0 king amrestore: missing file header block amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of tape: date amanda@fileserver:/usr/local/sbin HmWhat´s wrong? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amrestore problem
Am Freitag, 16. Februar 2001 20:57 schrieben Sie: root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king /dev/sg5 is a changer. The tape device is /dev/nst0, and that's what amrestore wants. OK, i will testing at theses day. Thanks a lot. Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amreport Problem
Am Freitag, 16. Februar 2001 20:57 schrieben Sie: Hi Alexandre! amreport: mail command failed: /usr/sbin/sendmail -s "Daily AMANDA MAIL REPORT FOR BogusMonth 0, 0" [EMAIL PROTECTED] It shouldn't be running sendmail directly. It should be using `Mail', `mailx' or `mail', as per configure. Why did you override the MAILER choice? Hmi didn't give them another name for the Mail. I compiled amanda with the standard options. Where can i change the mailname to the original name? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: broken pipe
Am Donnerstag, 15. Februar 2001 08:51 schrieben Sie:
Hi Alexandre!
Also the backup is finnished correctly?
I'd guess so, but you didn't post the part of the report that says
which dumps made to which tape, so I can't tell for sure.
OK, i send you the complete mail from amanda and hope that it helps:
Begin complete mail fom Amanda
These dumps were to tapes Daily01, Daily02.
Tonight's dumps should go onto 2 tapes: Daily03, Daily04.
FAILURE AND STRANGE DUMP SUMMARY:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:10
Run Time (hrs:min) 3:45
Dump Time (hrs:min)2:41 2:41 0:00
Output Size (meg) 44392.544392.50.0
Original Size (meg) 44392.544392.50.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped4 4 0
Avg Dump Rate (k/s) 4713.1 4713.1--
Tape Time (hrs:min)2:41 2:41 0:00
Tape Size (meg) 44392.644392.60.0
Tape Used (%) 111.0 111.00.0
Filesystems Taped 4 4 0
Avg Tp Write Rate (k/s) 4710.0 4710.0--
FAILED AND STRANGE DUMP DETAILS:
/-- fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
sendbackup: start [fileserver:sdc1 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Thu Feb 15 04:14:16 2001
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/sdc1 (/test/platte3) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 13086232 tape blocks.
| DUMP: Volume 1 started at: Thu Feb 15 04:14:58 2001
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 10.23% done, finished in 0:43
| DUMP: 21.75% done, finished in 0:35
| DUMP: 33.32% done, finished in 0:30
| DUMP: 44.95% done, finished in 0:24
| DUMP: 57.16% done, finished in 0:18
| DUMP: 68.34% done, finished in 0:13
| DUMP: 80.59% done, finished in 0:08
\
NOTES:
taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device
taper: retrying fileserver:sdc1.0 on new tape: [writing file: No space left
on device]
taper: tape Daily02 kb 13135584 fm 1 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
fileserver sdb10 1319558413195584 -- 40:525380.8 40:555375.7
fileserver sdc10 1313555213135552 -- 45:114844.5 45:134840.9
fileserver sdd10 92850889285088 -- 30:535009.9 30:555005.7
king hdb10 98416969841696 -- 43:483745.2 43:483744.4
(brought to you by Amanda version 2.4.2-19991216-beta1)
---End of Mail from Amanda
Bye Jeurgen
--
Dies ist eine Microsoft freie Mail!
Re: broken pipe
Am Donnerstag, 15. Februar 2001 09:50 schrieben Sie: See? No failures. You can use amtoc or amadmin info to find out in which tape the filesystem was stored. OK, no failure. Amadmin tell me that the backup is ok. I thank you for your help and Infos. Bye Juergen -- Dies ist eine Microsoft freie Mail!
amrestore problem
Hi! I will restore some files from the tape changer, but i become some errors: root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king amrestore: error reading file header: the argument is not correct (Das Argument ist ungueltig) In chg-scsi.conf i have config 0 drivenum0 dev /dev/nst0 scsitapedev /dev/sg5 startuse0 enduse 9 Why don't work amrestore? Bye Juergen -- Dies ist eine Microsoft freie Mail!
broken pipe
Hi!
At first i installed amanda for a long time on a tape server and amanda works
fine.
After insatlling amanda on a client i have this problems.
---Begin Amanda Mail
These dumps were to tapes Daily01, Daily02.
Tonight's dumps should go onto 2 tapes: Daily03, Daily04.
FAILURE AND STRANGE DUMP SUMMARY:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:10
Run Time (hrs:min) 3:45
Dump Time (hrs:min)2:41 2:41 0:00
Output Size (meg) 44392.544392.50.0
Original Size (meg) 44392.544392.50.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped4 4 0
Avg Dump Rate (k/s) 4713.1 4713.1--
Tape Time (hrs:min)2:41 2:41 0:00
Tape Size (meg) 44392.644392.60.0
Tape Used (%) 111.0 111.00.0
Filesystems Taped 4 4 0
Avg Tp Write Rate (k/s) 4710.0 4710.0--
FAILED AND STRANGE DUMP DETAILS:
/-- fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
sendbackup: start [fileserver:sdc1 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Thu Feb 15 04:14:16 2001
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/sdc1 (/drive/drive3) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 13086232 tape blocks.
| DUMP: Volume 1 started at: Thu Feb 15 04:14:58 2001
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 10.23% done, finished in 0:43
| DUMP: 21.75% done, finished in 0:35
| DUMP: 33.32% done, finished in 0:30
| DUMP: 44.95% done, finished in 0:24
| DUMP: 57.16% done, finished in 0:18
| DUMP: 68.34% done, finished in 0:13
| DUMP: 80.59% done, finished in 0:0
\
NOTES:
taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device
taper: retrying fileserver:sdc1.0 on new tape: [writing file: No space left
on device]
taper: tape Daily02 kb 13135584 fm 1 [OK]
-- End Message from Amanda
Whats the problem of amanda?
Bye Juergen
Re: broken pipe
Am Donnerstag, 15. Februar 2001 08:40 schrieben Sie: On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote: fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"] fileserver sdc1 lev 0 FAILED [dump to tape failed] [snip] taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device Looks like tape full. Ok, the tape is full, taper: tape Daily02 kb 13135584 fm 1 [OK] Looks like Amanda recovered correctly, restarting the dump in the following tape. and used the next tape. Also the backup is finnished correctly? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Client problem
Hi all! I have installed Amanda on a tape server for a long time ago and it works fine. The tape server is called fileserver with ip 10.0.1.50 and have an entry in the DNS, the client is king with ip 10.0.1.49 and have no entry in DNS. Now, i installed Amanda on a client without Server. When i am running on the tape server amcheck Daily i become a error message: amanda@fileserver:/usr/local/sbin ./amcheck Daily Amanda Tape Server Host Check Holding disk /dunps/amanda: 2100567 KB disk space available, thats plenty amcheck-server: slot : date 20010129 label Daily04 (exact label match) NOTE: skipping tape-writable test Tape Daily04 label ok Amanda Backup Client Host Check - Error: 10.0.1.49: [addr 10.0.1.50: hostname lookup failed] Client check: 2 hosts checked in 0.462 seconds, 1 problem found (brought to you by Amanda 2.4.2-19991216-beta1) In the disklist file i have fileserver sdb1 Daily 1 fileserver sdc2 Daily 2 fileserver sdd1 Daily 3 10.0.1.49 hdb1 Daily 4 Where is the problem? Who can help me by this (little?) problem? Thanks ! Bye Juergen -- This Mail is Microsoft free!
Re: Client problem
Hi Alexandre! I have checked the DNS configuration, and thats ok. I find the computers by giving the name How about finding the name given the IP? That's what Amanda is complaining about. Does `nslookup 10.0.1.50' succeed on 10.0.1.49? reverselookup was not set correct, i fixed ist. Now, when im start amcheck -c Daily i become a error amanda@fileserver:/usr/local/sbin ./amcheck -c Daily Amanda Backup Client Hosts Check ERROR: king: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed Client check: 2 hosts checked in 0.048 seconds, 1 problem found (brought to you by Amanda 2.4.2-19991216-beta1) On the fileserver under /home/amanda exist a file called .amandahosts and i have king and fileserver in it. Any hints? Bye Juergen
Amanda installation on a client
Hi! I had installed amanda on a tape server and there amanda is running fine. Now, I want to be install amanda on a client running under Kernel 2.2.17, so that the tape server can backup the client. I have decompressed the sources on the client and im not shure which options i need to configure amanda. I think that i will be using ./configure --with-name=amanda --with-group=disk --with-config=Daily --without-server is this correct? And what must be changed on the tape server so that amanda is backing up the client? I have in the disklist file on the tape server this entries 10.0.1.50 sdb1 Daily 1 10.0.1.50 sdb1 Daily 2 10.0.1.50 sdc1 Daily 3 Is that correct that i make a new entry in the disklist file on th tape server 10.0.1.49 hda1 Daily 4 so that amanda is going on the client and make a backup? Thanks Bye Juergen
Re: more than one Tapes?
Hi! This error suggests that either you have more than one amdump running at the same time, or you have more than one amanda server trying to talk to 'fileserver' at the same time, or else you have 'fileserver' listed in your disklist with more than one name. Basically it means that amandad was already running on 'fileserver' when it was contacted by amdump again to do something else. amandad is not multi-threaded and gave NAK response. No, there is only one entry for the fileserver. Amanda was waiting of the next Tape, because i have changed the amanda.conf while amanda is running. After stopping this and restart, a new incr. backup was made. I hope that amanda is using more than one tapes by a full backup. Bye Juergen -- Dies ist eine Microsoft freie Mail! Have Fun!
more than one Tapes?
Hi!
I have installed Amanda on a SUSE Linux with a Tapechanger. So far so good.
It works fine, but since Monday Amanda means that one tape is not enough.
OK, one Tape can save 40GB native Data, and i must save ca. 50GB.
In Amanda.conf i give Amanda one tape
runtapes 1 #number of tapes to be used in a single run of amdump
After changing runtapes 1 to runtapes 2, Amanda will not make backups
I became the following Mail from Amanda:
--begin
from: Amanda Admin [EMAIL PROTECTED]
to: [EMAIL PROTECTED]:;
Datum: Wed, 24 Jan 2001 07:46:45 +0100
These dumps were to tape Daily09.
Tonight's dumps should go onto 2 tapes: Daily00, Daily06.
FAILURE AND STRANGE DUMP SUMMARY:
fileserver sdd1 lev 0 FAILED [fileserver NAK: amandad busy]
fileserver sdc1 lev 0 FAILED [fileserver NAK: amandad busy]
fileserver sdb1 lev 0 FAILED [fileserver NAK: amandad busy]
STATISTICS:
TotalFull Daily
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 0:06
Dump Time (hrs:min)0:000:000:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped 0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:000:000:00
Tape Size (meg) 0.00.00.0
Tape Used (%)0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
driver: WARNING: got empty schedule from planner
taper: tape Daily09 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
fileserver sdb10 FAILED ---
fileserver sdc10 FAILED ---
fileserver sdd10 FAILED ---
(brought to you by Amanda version 2.4.2-19991216-beta1)
-End
What is the mistake? Who can help me?
Thanks
Juergen
--
This is a Microsoft free Mail!
Have Fun!
