Haftalk Blten
Title: YURT PARTISI Mail Listemizden Çýkmak Ýstiyorsanýz Lütfen Týklayýnýz.Ýrde Ýnternet Hizmetleri
Re: USBSCRIBE ME!
On Tue, 22 Oct 2002 at 11:51pm, Phil wrote usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe This won't work for two reasons: 1) You can't spell. 2) You're not following the directions at http://www.amanda.org on how to (un)subscribe from/to these lists. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: compression
On Wed, 23 Oct 2002 at 5:10pm, Joseph Sirucka wrote I would like to know where and what do I insert into the amanda.conf for allow tape compression to work. the tape unit is a hp1537A in a six stacker based unit. That depends on your OS and how the tape drive does compression. Sometimes, it is done by using a specific tape device, e.g. /dev/rmt/0cn on Solaris (c for compress). The tape device you would specify in your amanda.conf. Sometimes it is done via mt commanda, e.g. 'mt -f /dev/nst1 compression 1' for my AIT1 drive on Linux. This I put in the script that runs my nightly backups. Finally, if you want to use hardware compression (and that's not necessarily a bad thing (although some would argue otherwise)), you need to a) make sure that you're not also using software compression and b) lie to AMANDA about how big your tapes are. This lie (in the length parameter of your tapetype) is based on a guess of how compressible your data is and how well the drive compression works. It will probably take some finangling to optimize -- guess too big, and you'll hit EOT every night; guess too small and you'll be wasting tape. It is, in part, this guesswork that makes some people strongly recommend software compression, in which AMANDA keeps a history of how compressible your data is and you don't have to lie to AMANDA about your tape size. Of course, if you can't spare the cycles, then hardware compression will work just fine. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: USBSCRIBE ME!
On Tue, 2002-10-22 at 23:51, Phil wrote: usubscribe me,usubscribe me,usubscribe me,usubscribe me,usubscribe snippage Maybe if you would spell it right bonehead. -- -=/Thom Red Hat Linux release 8.0 (Psyche) running Linux Kernel 2.4.18-17.8.0 Up: 10:09am up 4 days, 21:49, 1 user, load average: 1.66, 1.69, 1.73 Registered Linux User #214499 http://counter.li.org
writing into a tape !!
Sir: I am new to amanda. I have installed it on my machine which is running AiX last week. My system description: 1. Using amanda-2.4.2p2 on AiX 2. I have followed the instructions given in README, INSTALL, docs/* files 3. I am not getting any errors when I run $ ./amcheck -m confname; ./amdump confname. I guess it is dumping something into the holding disk. The file in the holding disk is found to be ibms2.hd4.1. Is this the dump? 4. When I open the file, it has some special characters. 5. But when I say, $ ./amflush -f confname, it is not writing anything to the tape (/dev/rmt0). I have some other information in the tape drive. Will it not write to the tape or how can I write into it. 6. If I say, $ tar -tvf /dev/rmt0, I sould see the old files in the tape. 7. Also please help me, how to take backups of a single directory onto the tape/other directory in the machine at some other location. Thanking you very much in advance. Please help me. Regards, Nitesh
Re: compression
On Wednesday 23 October 2002 03:10, Joseph Sirucka wrote: Hi All I would like to know where and what do I insert into the amanda.conf for allow tape compression to work. the tape unit is a hp1537A in a six stacker based unit. regards Joseph That part is already in the amanda.conf file Joseph. The choice that controls when amanda will use it is made in the file disklist by your choice of which of the backup profiles contained in amanda.conf it is to use for each entry. This next is something you may not have considered. Generally speaking, its not a good idea to mix the use of compression by amanda with the use of hardware compression in the drive. And since amanda's compression can usually shrink things better than the drives hardware can, albeit at the expense of time to do the compression in software, most prefer to turn off the drives compression and use amanda choices exclusively if their machine has the horsepower. That drive probably has the ability to turn the compression back on even if the dip switches on it are set to disable it. It does this by reading a hidden header on the tape everytime a different tape is inserted, and if the tape was ever recorded with the compression turned on, then its very difficult to turn it off when reusing that tape again. Amanda by herself cannot do it, although it would be a nice feature to have. (hint hint) I've related a method that I've used many times several times previously on this list, so if thats a problem for you, look back thru the archives see if you can find it. If not, give us another yelp for help. :-) -- Cheers, Gene AMD K6-III500mhz 320M Athlon1600XP1400mhz 512M 99.18% setiathome rank, not too shabby for a WV hillbilly
Re: Quick Multiple Tape Question
On Tuesday 22 October 2002 18:04, Chad Morland wrote: I am trying to backup a 100G file onto tape. I am wondering if I can use amanda for this. Will it span the archive across more than one tape? I am using a DLT 7000 drive. If not, what are you recommendations? Yikes! For that, you will have to locate a drive and tape format that will hold it in one tape. Or, you have to use a split/join utility to break it up into tapable sized pieces that are each an independant file to the filesystem. Amanda cannot span one file across more than one tape, and because of the potentials for a disaster in such things as re-ordering the tapes on recovery, or any one of the other things that Mr. Murphy is famous for, it isn't likely that amanda ever will have that ability programmed in. -- Cheers, Gene AMD K6-III500mhz 320M Athlon1600XP1400mhz 512M 99.18% setiathome rank, not too shabby for a WV hillbilly I find that very strange considering that tar, dump and several other backup utilities support this. Amanda developers don't want to add this just for the sake of having it? I know I am not the only one that can find this feature useful. I can keep track of my tapes, and I'm sure it is not a difficult task for someone who can install, configure and use Amanda to do the same. Are there any other concrete and real issues for not including this feature other than operator misuse? -CM
Re: Quick Multiple Tape Question
Some OSs like AIX can span tapes using their version of tar by manually asking to mount another volume... I am not sure if you need to do this on a regular basis or just as a one time deal. If one time deal and you have the avail disk space use split to break it into as many pieces as you need and cat or join to bring it back together when you need to restore. Or you can get a tape drive like the M2 drives from exabyte that handle 60GB native 150GB compressed (varies depending on type of data). Is this database data or text files? or what? --- Chad Morland [EMAIL PROTECTED] wrote: I am trying to backup a 100G file onto tape. I am wondering if I can use amanda for this. Will it span the archive across more than one tape? I am using a DLT 7000 drive. If not, what are you recommendations? -CM __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/
Re: problem with restore
Try a blocking factor of 2, then try a blocking factor of 1. I think -b is for number of 512 byte blocks... so if you are using 1024 byte blocks use 2. Have you ever been able to restore before? There is some useful information in the source under docs/RESTORE but it's not extemely verbose on the -b piece of it. Jerry --- Max Kamenetsky [EMAIL PROTECTED] wrote: Jerry, Same problem. I've tried omitting it AND setting it to other values, and none of it helps. Thanks, Max * Jerry [EMAIL PROTECTED] [10/22/02 11:14] wrote: Are you sure you have the right blocking factor? Try omitting the -b and see if it works. Jerry --- Max Kamenetsky [EMAIL PROTECTED] wrote: Hi! I'm looking for some help on my restore problem. Everytime I attempt to restore, I get an error that says tape is not a dump tape. Here's a sample output: chinook:/home/.restore# amrestore /dev/nst0 chinook hda1 amrestore: 0: skipping start of tape: date 20021012 label DAILY09 amrestore: 1: restoring chinook.hda1.20021012.1 amrestore: 2: skipping zephyrus.sda1.20021012.1 amrestore: 3: skipping axon.sda1.20021012.1 amrestore: 4: skipping boreas.sda1.20021012.1 amrestore: 5: skipping chinook.hda5.20021012.1 amrestore: 6: skipping axon.sda3.20021012.1 amrestore: 7: skipping zephyrus.sda3.20021012.1 amrestore: 8: skipping boreas.sda3.20021012.1 amrestore: 9: skipping axon.sda4.20021012.1 amrestore: 10: skipping zephyrus.sda4.20021012.1 amrestore: 11: skipping chinook.hda6.20021012.0 amrestore: 12: skipping chinook.hda7.0021012.0 amrestore: 13: skipping boreas.sda4.20021012.0 amrestore: 14: reached end of tape: date 20021012 chinook:/home/.restore# restore -ivf chinook.hda1.20021012.1 -b 512 Verify tape and initialize maps Input is from file/pipe Input block size is 512 Checksum error 21367431044, inode 0 file (null) restore: Tape is not a dump tape chinook:/home/.restore# file chinook.hda1.20021012.1 chinook.hda1.20021012.1: new-fs dump file (little endian), This dump Sat Oct 12 00:51:08 2002, Previous dump Thu Oct 10 00:54:42 2002, Volume 1, Level 788529152, type: tape header, Label nne, Device dev/hda1, Host hinook.stanford.edu, Is this dump corrupted or am I doing something wrong? Incidentally, I had the same problem when using amrestore -p and piping the output to restore and also when trying to use amrecover. I would really appreciate any help you can offer. There are some critical files on that backup that I need to recover. Please cc me on any replies you send to the mailing list. Thanks, Max __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/
Re: Quick Multiple Tape Question
On Wed, 23 Oct 2002 at 11:03am, Chad Morland wrote On Tuesday 22 October 2002 18:04, Chad Morland wrote: I am trying to backup a 100G file onto tape. I am wondering if I can use amanda for this. Will it span the archive across more than one tape? I am using a DLT 7000 drive. If not, what are you recommendations? Yikes! For that, you will have to locate a drive and tape format that will hold it in one tape. Or, you have to use a split/join utility to break it up into tapable sized pieces that are each an independant file to the filesystem. *snip* I find that very strange considering that tar, dump and several other backup utilities support this. Amanda developers don't want to add this Err, *can* dump/tar span a single *file* across tapes? I'm not sure. A single filesystem -- sure. But a file? just for the sake of having it? I know I am not the only one that can find this feature useful. I can keep track of my tapes, and I'm sure it is not a difficult task for someone who can install, configure and use Amanda to do the same. Are there any other concrete and real issues for not including this feature other than operator misuse? Time. Spanning support has been in the planning stages for a long time. But the core AMANDA developers work very hard on lots of things that aren't AMANDA. If you'd like to get in touch with them and start coding, the contributions would be welcome. If you're talking about a *filesystem* rather than a file, then AMANDA can handle that easily via multiple disk list entries using tar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Quick Multiple Tape Question
I find that very strange considering that tar, dump and several other backup utilities support this. Amanda developers don't want to add this Err, *can* dump/tar span a single *file* across tapes? I'm not sure. A single filesystem -- sure. But a file? From the GNU tar manpage: Use --multi-volume (-M) on the command line, and then tar will, when it reaches the end of the tape, prompt for another tape, and continue the archive. Each tape will have an independent archive, and can be read without needing the other. (As an exception to this, the *file* that tar was archiving when it ran out of tape will usually be split between the two archives.. When I generate a table of context for my tape it shows that the file has been continued from X byte so it seems as if it is working. Time. Spanning support has been in the planning stages for a long time. But the core AMANDA developers work very hard on lots of things that aren't AMANDA. If you'd like to get in touch with them and start coding, the contributions would be welcome. If you're talking about a *filesystem* rather than a file, then AMANDA can handle that easily via multiple disk list entries using tar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University Thanks for the clear answer... it's alot easier to stomache that they don't have the time rather than the desire. Perhaps I can contribute to this project and finally give back to the world! ;-) -CM
RE: Quick Multiple Tape Question
Amanda cannot span one file across more than one tape, and because of the potentials for a disaster in such things as re-ordering the tapes on recovery, or any one of the other things that Mr. Murphy is famous for, it isn't likely that amanda ever will have that ability programmed in. Thats a shame, I've persisted using amanda as it has all the features I want except for this one. I had hoped that this functionality would appear soon. I always thought that one of the best features of Amanda was its ability to enforce correct tape usage, therefore I can't see why that should be a big issue. This is the one thing that is stopping me consolidating all my unix/linux backups onto amanda. I know you can split one partition into smaller sections using options to tar, but given the way the filesystem changes frequently I'm not happy to trust this (its easier and safer to stick with ufsdump) BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
Re: Quick Multiple Tape Question
[ On Wednesday, October 23, 2002 at 11:31:20 (-0400), Joshua Baker-LePain wrote: ] Subject: Re: Quick Multiple Tape Question Err, *can* dump/tar span a single *file* across tapes? I'm not sure. A single filesystem -- sure. But a file? Yes, with dump you should be able to put large files on multiple tape volumes. Most versions of dump/restore can handle multiple volumes (and they always could), and they shouldn't care if a file spans multiple volumes, though it's been some time since I really tested this ability in any implementation. However most versions of tar/pax/cpio/afio should _not_ allow you to span multiple tapes with a single file. The formal definitions of ustar, cpio, and now pax archive formats do not allow for multiple volume support. There are some proprietary formats (maybe even GNU Tar's) which might allow spanning a file across multiple tapes. The issue is that there really must be a header on the second and following tapes, and normally in the tar/ustar/pax/cpio formats a header always starts a new file. So in order to use tar/pax/cpio/afio to archive files larger than a single tape you either have to split large file first into just slightly smaller than tape-sized chunks, or you have to create the archive on disk, then split it into just less than tape-sized chunks and either write each chunk to tape and very very very very carefully label the tapes so that you can read the archive back in in the right order, or then subsquently again use a version of pax or tar or cpio which does support multiple volumes to put the archive chunks onto multiple tapes. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
Re: amdump ignoring portrange and udpportrange
I had the same problem until I checked 2 things. 1) Make sure that's enough ports. I've got 3 clients with 12 partitions. I'm using portrange 10080-10180 and udpportrange 900-925. I tried using 50 ports for the portrange, but I was still getting client timed out messages on odd ports. 100 ports might seem to be overkill, but I haven't got the client timed out since. 2) Check any firewalls that might be on the client or server. Make sure the amanda service is starting on the client when called from the server. If it's not able to receive the clients reply or the client isn't replying, amanda'll time out. Lalo Marvin Davenport wrote: i am using amanda-2.4.3b4 , I have recompiled with options --with-portrange=850,860 --with-udpportrange=850,860 it passes amcheck but when I run amdump I get the following error in the amdump.log dumper: stream_client: connect to 209.123.168.230.49833 failed: Connection timed out it appears to be picking port 49833, any ideas why? __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ -- Lalo Castro Programmer/Analyst McHenry Library (831) 459-5208
Samba NT_ACCESS_DANIED
Hi, I've got a problem with samba shares, here the report : FAILED AND STRANGE DUMP DETAILS: /-- backup.mti //Servermti/backupz lev 0 STRANGE sendbackup: start [backup.mti.it://Servermti/backupz level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? NT_STATUS_ACCESS_DENIED listing \RECYCLER\S-1-5-21-583907252-436374069-1060284298-500\* ? NT_STATUS_ACCESS_DENIED listing \System Volume Information\* | tar: dumped 65677 files and directories | Total bytes written: 9764754944 sendbackup: size 9535894 sendbackup: end \ I've tried to use exclude-list (works successful on unix) for these 2 dirs (/RECYCLER and /System Volume Information), but the problem persist. What I can do for this errors? Thanks in advance. matteo -- GnuPG fingerprint: 3C4D 4D2A 3BBE B24B 4EC2 60E7 6FFE 947C 9CAE 9642
Re: Samba NT_ACCESS_DANIED
On Wed, 23 Oct 2002 at 11:39pm, `matte wrote I've tried to use exclude-list (works successful on unix) for these 2 dirs (/RECYCLER and /System Volume Information), but the problem persist. As noted in docs/SAMBA, you can only have one exclude (not an exclude list) for smb backups. Pick one to exclude, and ignore the other error. :) -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
huge filesystems timing out on calcsize.
Has anyone else encountered this problem ? FAILURE AND STRANGE DUMP SUMMARY: releng.ink /export/releng2/shipped lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/share lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/releng2_tmp lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/re lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/np lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/downloads_sync lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/cdrom lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/PrepArea lev 0 FAILED [Request to releng.inktomi.com timed out.] releng.ink /export/releng2/NTarchive lev 0 FAILED [Request to releng.inktomi.com timed out.] etc... The filesystem layout is thus : /dev/md/dsk/d1 1018191861776 95324 91% / /dev/md/dsk/d3 1018191 74474882626 8% /var /dev/md/dsk/d411193440 9316148 1765358 85% /export /dev/dsk/c1t5d0s0104262624 97523668 5696330 95% /export/releng2 /dev/dsk/c2t2d0s2173478604 158757126 12986692 93% /export/releng etc... With the disks being larger then the capacity of a single backup volume I'm therefore backing up subdirs using gtar. The filesystems have lots and lots of small files. I've increased etimeout in amanda.conf to 6000s, and still I get the timeouts. Does anyone have any ideas ? All help gratefully received :) Cheers, Al -- Alan C. Horn Inktomi - Unix Architect. +1-650-653-5436 [[EMAIL PROTECTED]]
Re: Quick Multiple Tape Question
On Wed, Oct 23, 2002 at 11:53:08AM -0400, Chad Morland wrote: I find that very strange considering that tar, dump and several other backup utilities support this. Amanda developers don't want to add this Err, *can* dump/tar span a single *file* across tapes? I'm not sure. A single filesystem -- sure. But a file? From the GNU tar manpage: Use --multi-volume (-M) on the command line, and then tar will, when it reaches the end of the tape, prompt for another tape, and continue the archive. Each tape will have an independent archive, and can be read without needing the other. (As an exception to this, the *file* that tar was archiving when it ran out of tape will usually be split between the two archives.. In a discussion of whether tar/dump/... can handle multiple volumes you forget one thing, generally those programs are not handling the tape themselves in an amanda backup. The dump has been made to a file with an amanda header and then transfered to the tape. Even when going directly to the tape, the dumps are generally going through other programs like gzip and the indexer and ??? They are not writing to the tape itself. From long ago discussion I recall that one of the biggest problems those that looked into multi-volume dumps was determining just exactly what part of the dump file actually made it successfully onto the tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: What features should I look for in a new library?
Gary Algier [EMAIL PROTECTED] writes: Multiple tape drives: Our old library had only one drive installed. I could have added a second one, but I could not see how amanda would use it to advantage. Can amanda use a second (or third...) drive? Is there any benefit? Beside having it for redundancy (in case the first tape drive fails) I use it to restore data while the amdump still runs on teh first drive. I use mtx for moving the tape to the second drive; and after the amrecove rrun I have to use mtx again to move it back. Barcodes: Can amanda find a tape faster if the library supports barcodes? The current method of reading the headers of each tape is slow enough to make me willing to drive to work to look at the written labels on the tapes. Can this kind of mechanism be used instead of barcodes to find the tape quicker? As long as the tape requested by the taper algorithm (use amadmin tape) comes directly after the current tape it will be found immediately. The cycling through the whole library only happens when the requested tape isn't in the library anymore. And according to my observations barcode does not help in that case. See [EMAIL PROTECTED] sent to this list. But mtx can display the barcode, so you can use that in order to find out which tape to insert via amtape. Sven
compression
Hi All I would like to know where and what do I insert into the amanda.conf for allow tape compression to work. the tape unit is a hp1537A in a six stacker based unit. regards Joseph
RE: Samba NT_ACCESS_DANIED
Those folders aren't needed. Just ignore the errors -Original Message- From: Joshua Baker-LePain [mailto:jlb17;duke.edu] Sent: 23 October 2002 23:01 To: `matte Cc: ML Amanda Users Subject: Re: Samba NT_ACCESS_DANIED On Wed, 23 Oct 2002 at 11:39pm, `matte wrote I've tried to use exclude-list (works successful on unix) for these 2 dirs (/RECYCLER and /System Volume Information), but the problem persist. As noted in docs/SAMBA, you can only have one exclude (not an exclude list) for smb backups. Pick one to exclude, and ignore the other error. :) -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
