disk offline
I would expect this to be a frequently asked question, but after looking
through Google, I didn't see much specifically on it, so...
My amdump email report starts out:
These dumps were to tape daily001.
The next tape Amanda expects to use is: daily001.
FAILURE AND STRANGE DUMP SUMMARY:
client.agic. /usr lev 0 FAILED [disk /usr offline on client.agic.ne.jp?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0: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:
planner: Adding new disk client.agic.ne.jp:/usr.
driver: WARNING: got empty schedule from planner
taper: tape daily001 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
client.agic.ne /usr0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
I'm not really sure where to start looking for answers here.
Can anyone suggest a starting point?
Thanks,
Shawn
Tar patch
hi! How do i apply the Tar patfch in the patches directory? I am using tar 1.13.19 . Do i still need the patch? thanks for any replies, Vijay
[no subject]
I'm getting this on a RedHat box. It was backing up fine and all of a sudden it starts failing. Nothing known was changed... Amanda Daily Report: /-- mehrh /usr2 lev 0 FAILED [data timeout] sendbackup: start [mehrh.site.corp.com:/usr2 level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end \ on mehrh: more /tmp/amanda/runtar.20020419173244.debug sendbackup: started index creator: "/bin/gtar -tf - 2>/dev/null | sed -e 's/^\./ /'" index tee cannot write [Broken pipe] sendbackup: pid 21969 finish time Fri Apr 19 17:35:29 2002 And yet /export/home on the same machine backed up at level 0 just fine. Any ideas? Thanks again, Brandon Moro Systems Administration, Unify Corporation [EMAIL PROTECTED] - >From meanness first this Portsmouth Yankey rose, And still to meanness all his conduct flows.--Oppression, A poem by an American (Boston, 1765).
Re: AIT libraries
I am using a Spectra-2000 15 tape changer with an AIT-2 drive. I can recommend it with a couple of caveats: 1. So far it has been reliable on Solaris 8 with a SE SCSI card. 2. Spectra and I have so far been unable to get the tape drive working on a Dell 1550 with LVD. On Mon, 22 Apr 2002, Brandon D. Valentine wrote: - This is exciting. My department is seriously looking at investing in a - tape library. I've always wanted one to call my own ;-). So it is with - this happy news that I turn to you, the most helpful group of tape - library owners I am aware of. - - I am seeking recommendations, testimonials if you will, from people - succesfully using AIT libraries with amanda. To aid in this, here's a - bit of background about our current setup and our projected budget & - storage goals. - - We currently use a standalone SDX-300C AIT1 tape drive w/ 35GB tapes. - We run a 2week long 10tape Daily backup cycle and a Monthly 10tape - cycle. The Monthly cycle uses skip-incr, record no and chg-manual. - However, we are rapidly accumulating data beyond what I can - realistically do a chg-manual, skip-incr dump on. - - I am interested in AIT libraries in the 15-16 tape size range. Solid - compatibility with amanda is a must. We are looking to spend obviously - as little as possible to get a quality product, but $10k is a very firm - ceiling and the closer to $5k we can hold the price, the more likely it - is to get funded. Rackmount is a must, though I'm not so concerned with - how many RUs it takes up. So far the only products I am really familiar - with are the Sony LIB-152 & LIB-162 series. I understand that Overland - Data and several other companies are also making AIT libraries. I'd be - interested to hear about those. Pros/Cons of them versus the Sony ones, - etc. - - My other question is: - Does anyone know how backwards compatible AIT2/AIT3 drives are with AIT1 - tapes? The reason I ask is that if the backwards compatibility is good - I would consider the extra cost of an AIT2 or 3 drive in the library up - front so that if (and when) the capacity of our existing tapes started - to become strained I could spring for the relatively cheap upgrade of a - new round of larger tapes. Those 100GB native capacity AIT3 tapes are - quite sexy. - - Thanks, - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
help on define tapetype in amanda.conf
What should be my definintion in amanda.conf if I have this device: sa0 at sym0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 16) I've found a long list from the link below but I don't know which one to select: http://www.amanda.org/fom-serve/cache/72.html Thanks. Neil
RE: Amanda and Encryption
Agreed, but it does not encrypt the data on tape. The setup I mentioned is used to encrypt the dump itself, not the transport. Andrew On Mon, 22 Apr 2002, Bort, Paul wrote: > Another option, depending on how many machines are on the public network, is > a VPN tunnel, like FreeSWAN or CIPE. (This also provides a secure channel > for other useful things like monitoring and remote control, if desired). > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: Monday, April 22, 2002 3:45 PM > > To: Chad Morland > > Cc: [EMAIL PROTECTED] > > Subject: Re: Amanda and Encryption > > > > > > Hello, > > > > Encryption is possible via gnupg and gzip. > > > > Please read the info at the the following url: > > > > http://security.uchicago.edu/tools/gpg-amanda/ > > > > I am in the process of writting a document to cover this. It > > is about 90% > > done and is not up to date with 2.4.3. ( I dont know if there are any > > differences with 2.4.3, I assume none) If you would like I > > can forward > > you what I have. Its info is complete but it needs to be proof read > > again, so understand its not perfect. > > > > I am currently running this setup and love it. It has not > > messed up on > > me once. > > > > > > Andrew > > > > On Mon, 22 Apr 2002, Chad Morland wrote: > > > > > I was wondering if it is possible to encrypt the traffic that amanda > > > sends over a network. I have data that I need to backup and > > some of the > > > data will have to travel over the public internet. Because this data > > > contains sensitive information I do not want the data to be sent > > > unencrypted. Has anyone configured amanda to use SSL/TLS or > > even SSH? > > > Thanks. > > > > > > -CM > > > > > >
Re: don't know what's next
Can someone send me a working amanda.conf for my specs below? I tried renaming amanda.conf.in and editing it, but the words/directives are totally new to me. Btw, mine is /dev/nrsa0 Thanks. Enlighten again. :-) - Original Message - From: "Onie Camara" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 22, 2002 1:18 PM Subject: don't know what's next > hi, > > I'm using freebsd4.5 stable. A lot of people on a diff mailing and irc told > me to use > Amanda. I've installed amanda from ports. I've also downloaded the > tar.gz so I can get an example conf file on example directory. > > Browsing through the example directory brought me to confusion. There are > sample > files but I don't know which one to use. I also couldn't find a fine guide > on amanda configuration > from the net. > > Here is the spec of my freebsd. > > 1. sa0 at sym0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 10.000MB/s transfers (10.000MHz, offset 16) > > 2. and sym > sym0: <875> port 0x7800-0x78ff mem > 0xf3fff000-0xf3ff,0xf3ffef00-0xf3ffefff irq 11 at device 16.0 on pci0 > sym0: No NVRAM, ID 7, Fast-20, SE, parity checking > sa0 at sym0 bus 0 target 6 lun 0 > > What I wanted: > 1. I want to backup another unix machine > 2. Optionally, I want to backup the amanda machine itself. > > Thanks. Please enlighten. :-) > > Neil > >
Re: AIT libraries
> I am interested in AIT libraries in the 15-16 tape size range. Solid > compatibility with amanda is a must. We are looking to spend obviously > as little as possible to get a quality product, but $10k is a very firm > ceiling and the closer to $5k we can hold the price, the more likely it > is to get funded. Rackmount is a must, though I'm not so concerned with > how many RUs it takes up. So far the only products I am really familiar > with are the Sony LIB-152 & LIB-162 series. I understand that Overland > Data and several other companies are also making AIT libraries. I'd be > interested to hear about those. Pros/Cons of them versus the Sony ones, > etc. Once upon a time I ran an Overland Library with 19 AIT-2 tapes and a Sony SDX-500C internally just fine with Amanda.
Overland LXB Changer
Hello, I've used amanda before, but never with a changer. I'm having some problems, some of which seem to be amanda-related and some of which seem to be changer-related. Hardware: Computer running linux Overland DLT-LXG2016 Global Control Module - 16 tapes Overland DLT-LXB7110 Base Module - 10 tapes, 1 drive I can talk to both the changer (/dev/sg2) and the tape drive (/dev/nst0). The basic config *seems* to work. When I go to label a tape, though... Results are below. I'd like to know why amlabel grabs the tape from the wrong slot. [amanda@backup fam]$ mtx -f /dev/sg2 status Storage Changer /dev/sg2:1 Drives, 26 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full :VolumeTag=PHH369 Storage Element 2:Full :VolumeTag=PHH370 Storage Element 3:Full :VolumeTag=PHH371 Storage Element 4:Full :VolumeTag=PHH372 Storage Element 5:Full :VolumeTag=PHH373 Storage Element 6:Full :VolumeTag=PHH374 Storage Element 7:Empty Storage Element 8:Empty Storage Element 9:Empty Storage Element 10:Empty Storage Element 11:Empty Storage Element 12:Empty Storage Element 13:Empty Storage Element 14:Empty Storage Element 15:Empty Storage Element 16:Empty Storage Element 17:Full :VolumeTag=PHH360 Storage Element 18:Full :VolumeTag=PHH361 Storage Element 19:Full :VolumeTag=PHH362 Storage Element 20:Full :VolumeTag=PHH363 Storage Element 21:Full :VolumeTag=PHH364 Storage Element 22:Full :VolumeTag=PHH365 Storage Element 23:Full :VolumeTag=PHH366 Storage Element 24:Full :VolumeTag=PHH367 Storage Element 25:Full :VolumeTag=PHH368 Storage Element 26:Full :VolumeTag=CLN280 [amanda@backup fam]$ amlabel fam PHH630 slot 17 labeling tape in slot 17 (/dev/nst0): rewinding amlabel: tape_rewind: rewinding tape: /dev/nst0: Input/output error [amanda@backup fam]$ mtx -f /dev/sg2 status Storage Changer /dev/sg2:1 Drives, 26 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 19 Loaded):VolumeTag = PHH362 Storage Element 1:Full :VolumeTag=PHH369 Storage Element 2:Full :VolumeTag=PHH370 Storage Element 3:Full :VolumeTag=PHH371 Storage Element 4:Full :VolumeTag=PHH372 Storage Element 5:Full :VolumeTag=PHH373 Storage Element 6:Full :VolumeTag=PHH374 Storage Element 7:Empty Storage Element 8:Empty Storage Element 9:Empty Storage Element 10:Empty Storage Element 11:Empty Storage Element 12:Empty Storage Element 13:Empty Storage Element 14:Empty Storage Element 15:Empty Storage Element 16:Empty Storage Element 17:Full :VolumeTag=PHH360 Storage Element 18:Full :VolumeTag=PHH361 Storage Element 19:Empty Storage Element 20:Full :VolumeTag=PHH363 Storage Element 21:Full :VolumeTag=PHH364 Storage Element 22:Full :VolumeTag=PHH365 Storage Element 23:Full :VolumeTag=PHH366 Storage Element 24:Full :VolumeTag=PHH367 Storage Element 25:Full :VolumeTag=PHH368 Storage Element 26:Full :VolumeTag=CLN280 [amanda@backup fam]$ >From amanda.conf: tpchanger "chg-scsi" tapedev "0" changerfile"/usr/etc/amanda/fam/changer.conf" changerdev "/dev/sg2" >From changer.conf: number_configs 1 eject 0 sleep 5 cleanmax20 changerdev /dev/sg2 startuse1 enduse 26 cleancart 26 statfile/var/lib/amanda/fam/statfile cleanfile /var/lib/amanda/fam/cleanfile usagecount /var/lib/amanda/fam/usagecount config 0 drivenum0 dev /dev/nst0 ~
[no subject]
unsubscribe [EMAIL PROTECTED]
RE: Amanda and Encryption
Another option, depending on how many machines are on the public network, is a VPN tunnel, like FreeSWAN or CIPE. (This also provides a secure channel for other useful things like monitoring and remote control, if desired). > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 22, 2002 3:45 PM > To: Chad Morland > Cc: [EMAIL PROTECTED] > Subject: Re: Amanda and Encryption > > > Hello, > > Encryption is possible via gnupg and gzip. > > Please read the info at the the following url: > > http://security.uchicago.edu/tools/gpg-amanda/ > > I am in the process of writting a document to cover this. It > is about 90% > done and is not up to date with 2.4.3. ( I dont know if there are any > differences with 2.4.3, I assume none) If you would like I > can forward > you what I have. Its info is complete but it needs to be proof read > again, so understand its not perfect. > > I am currently running this setup and love it. It has not > messed up on > me once. > > > Andrew > > On Mon, 22 Apr 2002, Chad Morland wrote: > > > I was wondering if it is possible to encrypt the traffic that amanda > > sends over a network. I have data that I need to backup and > some of the > > data will have to travel over the public internet. Because this data > > contains sensitive information I do not want the data to be sent > > unencrypted. Has anyone configured amanda to use SSL/TLS or > even SSH? > > Thanks. > > > > -CM > > >
Re: Why does amrecover not show all the files?
I reasoned that the latest should be the greatest, but failed to get Amanda working with 1.13.25 on some platform (can't remember which one; perhaps the HP-UX). I didn't dig further. I went back to 1.13.19 and it worked. -- Ulrik Sandberg Joshua Baker-LePain skrev: > > On Mon, 22 Apr 2002 at 4:01pm, Niall O Broin wrote > > > Latest pre-release version is 1.13.25 - is it OK to use this or should one > > stick to 1.13.19 ? > > > I can't recall hearing anything bad about 25. Test it, of course, but it > "should" work just fine.
AIT libraries
This is exciting. My department is seriously looking at investing in a tape library. I've always wanted one to call my own ;-). So it is with this happy news that I turn to you, the most helpful group of tape library owners I am aware of. I am seeking recommendations, testimonials if you will, from people succesfully using AIT libraries with amanda. To aid in this, here's a bit of background about our current setup and our projected budget & storage goals. We currently use a standalone SDX-300C AIT1 tape drive w/ 35GB tapes. We run a 2week long 10tape Daily backup cycle and a Monthly 10tape cycle. The Monthly cycle uses skip-incr, record no and chg-manual. However, we are rapidly accumulating data beyond what I can realistically do a chg-manual, skip-incr dump on. I am interested in AIT libraries in the 15-16 tape size range. Solid compatibility with amanda is a must. We are looking to spend obviously as little as possible to get a quality product, but $10k is a very firm ceiling and the closer to $5k we can hold the price, the more likely it is to get funded. Rackmount is a must, though I'm not so concerned with how many RUs it takes up. So far the only products I am really familiar with are the Sony LIB-152 & LIB-162 series. I understand that Overland Data and several other companies are also making AIT libraries. I'd be interested to hear about those. Pros/Cons of them versus the Sony ones, etc. My other question is: Does anyone know how backwards compatible AIT2/AIT3 drives are with AIT1 tapes? The reason I ask is that if the backwards compatibility is good I would consider the extra cost of an AIT2 or 3 drive in the library up front so that if (and when) the capacity of our existing tapes started to become strained I could spring for the relatively cheap upgrade of a new round of larger tapes. Those 100GB native capacity AIT3 tapes are quite sexy. Thanks, -- Brandon D. Valentine <[EMAIL PROTECTED]> Computer Geek, Center for Structural Biology "This isn't rocket science -- but it _is_ computer science." - Terry Lambert on [EMAIL PROTECTED]
Re: Amanda and Encryption
Hello, Encryption is possible via gnupg and gzip. Please read the info at the the following url: http://security.uchicago.edu/tools/gpg-amanda/ I am in the process of writting a document to cover this. It is about 90% done and is not up to date with 2.4.3. ( I dont know if there are any differences with 2.4.3, I assume none) If you would like I can forward you what I have. Its info is complete but it needs to be proof read again, so understand its not perfect. I am currently running this setup and love it. It has not messed up on me once. Andrew On Mon, 22 Apr 2002, Chad Morland wrote: > I was wondering if it is possible to encrypt the traffic that amanda > sends over a network. I have data that I need to backup and some of the > data will have to travel over the public internet. Because this data > contains sensitive information I do not want the data to be sent > unencrypted. Has anyone configured amanda to use SSL/TLS or even SSH? > Thanks. > > -CM >
Re: dos partion
u probably want to back it up with tar - i suppose. There is not enough info, but i could guess ur using dump. /gat Tom Beer wrote: > > Hi, > > I want to back a dos partition > on a dual boot machine. I mount > this parition /mnt/dos and the disklist > entry is > > vaio.system ad0s1 comp-user > > sendsize.debug states "bad sblock number" > entiry dump terminated. > > Any pointers? > > Thanks Tom
[no subject]
unsubscribe [EMAIL PROTECTED]
RE: dos partion
dump is fs-specific. If your dump is for ext2 file systems, it won't understand FAT or FAT32 at all, and bails rahter than risking something. (The specific error is because it is looking for a superblock (or sblock), and the place that ext2 would have put one has something else in FAT, which doesn't make sense as an sblock number) change the dump type to comp-user-tar, make sure that comp-user-tar has the options you want, and you should be set. Oh, and make sure you have a non-broken version of tar. 1.13.19 is recommended. > -Original Message- > From: Tom Beer [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 22, 2002 2:12 PM > To: [EMAIL PROTECTED] > Subject: dos partion > > > Hi, > > I want to back a dos partition > on a dual boot machine. I mount > this parition /mnt/dos and the disklist > entry is > > vaio.system ad0s1 comp-user > > sendsize.debug states "bad sblock number" > entiry dump terminated. > > Any pointers? > > Thanks Tom >
Re: don't know what's next
On Mon, 22 Apr 2002, Onie Camara wrote: > hi, > > I'm using freebsd4.5 stable. A lot of people on a diff mailing and irc told > me to use > Amanda. I've installed amanda from ports. I've also downloaded the > tar.gz so I can get an example conf file on example directory. > > Browsing through the example directory brought me to confusion. There are > sample > files but I don't know which one to use. I also couldn't find a fine guide > on amanda configuration > from the net. > > Here is the spec of my freebsd. > > 1. sa0 at sym0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 10.000MB/s transfers (10.000MHz, offset 16) > > 2. and sym > sym0: <875> port 0x7800-0x78ff mem > 0xf3fff000-0xf3ff,0xf3ffef00-0xf3ffefff irq 11 at device 16.0 on pci0 > sym0: No NVRAM, ID 7, Fast-20, SE, parity checking > sa0 at sym0 bus 0 target 6 lun 0 > > What I wanted: > 1. I want to backup another unix machine > 2. Optionally, I want to backup the amanda machine itself. > > Thanks. Please enlighten. :-) > > Neil > Hi Neil - If you installed the amanda24-server port, there will be documentation in the /usr/local/share/amanda folder. Take a look there at the INSTALL file. As for tape device, you'll probably use "/dev/nrsa0", but first you need to go through the procedure of setting up the server and then the client(s). Also check the documentation at amanda.org and/or search this list online for later problems. -- ~~ Doug Silver Network Manager Urchin Corporation http://www.urchin.com ~~
Re: dos partion
On Mon, 22 Apr 2002 at 8:12pm, Tom Beer wrote > I want to back a dos partition > on a dual boot machine. I mount > this parition /mnt/dos and the disklist > entry is > > vaio.system ad0s1 comp-user > > sendsize.debug states "bad sblock number" > entiry dump terminated. You'll need to use tar, not dump. dump only works for ext2. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
dos partion
Hi, I want to back a dos partition on a dual boot machine. I mount this parition /mnt/dos and the disklist entry is vaio.system ad0s1 comp-user sendsize.debug states "bad sblock number" entiry dump terminated. Any pointers? Thanks Tom
Amanda Basics
hi! I am a newbee here and am just abt to install Amanda to take incremantal backups of abt 15 linux clients. I had a few elementary questions 1. I have tar 1.13.19 . Where do i get the patch up for runing Amanda using tar and how exactly do i apply it? 2.My purpose is to take incremental backups of the machines on the hard disks of some of the machines itself (NO TAPE).( Ours is a very small group of Graduate students having a very small network of abt 15 Linux clients and a Linux server, so our requirements are very modest ;-) ).So any ideas how shd i configure my Amanda (probable values of dumpcycle , runsperdump ,tapedevs ..etc) . 3.Does Amanda decide for itself when to take a full backup and when to go for a incremental one? If yes how does it do that? 4.I dont have a tape device so what do i specify abt the tape dev location and tapechng in configuration? thanks , Vijay ~~ Graduate Research Assistant Wireless Networking & Simulation Lab University of Cincinnati. Ph: (Lab) 513 556 1121Mail: [EMAIL PROTECTED] (Res) 513 556 7513 [EMAIL PROTECTED] ~~
Re: Increasing number ot tapes used.
--On Monday, April 22, 2002 20:23:01 +0100 Niall O Broin <[EMAIL PROTECTED]> wrote: > I'm not long using Amanda (haven't finished a full dumpcycle yet) and I've > decided that I'd like to use more tapes than I initially decided. I have > > dumpcycle 2 weeks > runspercycle 10 > tapecycle 14 tapes > > and I'd like to bump tapecycle up to 20 tapes or even a couple more because: > > a) I have the tapes already :-) > b) Even if my backup load expands to nearly my full capacity (tape size * > runspercycle) with tapecycle = 2 * runspercycle I'll always have 2 full > dumps available. > > Is there any problem with changing tapecycle now ? > No, you can increase it anytime, but if you like to feed your tapes in numerical order either add them in when it is about to use your first tape or follow the directions in the archive on editing your tapelist. Also, don't forget to label the new tapes (the first option is much easier, IMHO). Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Using Amanda
On Mon, 22 Apr 2002 at 12:39pm, Morrison, Trevor (Trevor) wrote > > 3) Please respond below quoted text. > OK, never mind about this one, as LookOut doesn't seem to add any quoted text marker. *sigh* > I am sorry, I am responding from work where my address is not part of > the users list and am running Outlook as you can tell. What should the > permissions be for amanda 750, 755 ,700? You shouldn't have to change permissions on any filesystems or files to use amanda. So they should be whatever site security requires. > > I tried adding amanda to the disk group and the root group, but to no > > avail. I really do not fully understand the permissions that amanda > > requires. I thought by adding amanda to the respective groups that own > > the directories that that would be fine. Could you straighten me out on > > this. TIA. > > > To have xinetd run the program with *all* groups the user belongs to, > > you need a "groups=yes" line in the appropriate service file (i.e. > > /etc/xinetd.d/amanda). Also, certain bits of amanda should be > > installed setuid root. What does 'ls -l /usr/local/libexec | grep > > rws' say? This allows amanda to be root to backup stuff via tar. > > > I will add groups=yes when I get home. I am running a program called > > XSid that goes in and changes files so that they cannot be setuid > > root. I will run you command later and let you know. Thanks. Does XSid have some sort of exclusion list? Some stuff needs to be setuid... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Amanda and Encryption
I was wondering if it is possible to encrypt the traffic that amanda sends over a network. I have data that I need to backup and some of the data will have to travel over the public internet. Because this data contains sensitive information I do not want the data to be sent unencrypted. Has anyone configured amanda to use SSL/TLS or even SSH? Thanks. -CM
RE: Please help -- planner askfor: lev out of range -1..10: 10
--On Monday, April 22, 2002 11:42:46 -0600 "Brashers, Bart -- MFG, Inc."
<[EMAIL PROTECTED]> wrote:
> Hi Frank, thanks for your response!
>
>> To summarize what I think you've said, you are trying to back up
>> ~200GB on a 40GB tape, and are dynamicly rewriting your disklist
>> entries into ~25GB chunks. You don't say how many tapes you have
>> in your runtapes and tapecycle, or if you have some kind of changer
>> configured (even if it is chg-manual).
>
>> > The relevant parts of my amanda.conf file are:
>> >
>> > dumpcycle 3 weeks
>> > runspercycle 15
>> > tapecycle 17 tapes
>> > define dumptype mydumptype {
>> > program "GNUTAR"
>> > compress none
>> > } (plus more of the usual options)
>
> runtapes 1
> tapedev "/dev/nst0"
>
> I'm trying to avoid using chg-manual, and let amanda run on 1 tape per
> night. I'd like to be able to use my tape drive for other non-amanda tasks
> during the day ;-).
You could still use it during the day, as long as amdump or amcheck
weren't trying to use it. If you really don't want to set up a changer,
and if you have enough holding disk, you could lie to Amanda about
your tapetype and say it is 80GB, then planner will dump up to that
much. You will get a tape error in your daily report (since it will
hit EOT around 40GB), but you can then amflush it whenever it is
convenient.
>>> FAILURE AND STRANGE DUMP SUMMARY:
>>> beowulf/home/proj/mm5 lev 1 FAILED [dump larger than tape, skipping
>>> incremental]
>>> beowulf/var/mail lev 1 FAILED [dumps way too big, must skip
>>> incremental dumps]
>>> (and so on, for ~30 or so directories)
>>
>> This says an incremental of /home/proj/mm5 is >40GB so it can't write
>> it to tape. The /var/mail error (dumps way too big) indicates that
>> the day's backup can't fit on the tapes allotted to it, so Amanda is
>> having to skip backups of those filesystems.
>
> Ok, I'm confused. Each of these errors "dump larger than tape" and "dumps
> way too big" refers not to the overall amanda run, BUT TO THAT PARTICULAR
> DISK? That should be impossible. Each night _before_ amanda is run, my
> ammakelist script would break up /home/proj/mm5 into sub-directories that
> are each less than 25Gb. So it's impossible for the lev 1 to be larger than
> 25Gb, and it should fit on a tape. Not necessarily this tape, since the
> amount to be written on any one night is generally larger than my
> tapedrive...
>
> [root]% du -h /var/spool/mail/
> 360k/var/spool/mail
>
> There's no way the lev 1 on /var/spool/mail is larger than a tape. So these
> errors "dump larger than tape" and "dumps way too big" must refer to the
> total amount dumped to tape.
"dumps way too big" does refer to total backup size, but the other
warning, "dump larger than tape" refers to the individual filesystem.
Check the size of /home/proj/mm5. Perhaps its size changed between
the time your disklist was created and when amdump ran.
>> Increasing runtapes should help (although you may have to adjust
>> tapecycle and runspercycle unless you have extra tapes).
>
> So my idea that I should add tapes (I recently went from 12 to 17) was
> heading in the right direction. I have extra tapes in-house. Can I go to
>
> dumpcycle 4 weeks
> runspercycle 20
> tapecycle 22 tapes
> runtapes 1
>
> or do I have to go to something like
>
> dumpcycle 2 weeks
> runspercycle 10
> tapecycle 22 tapes
> runtapes 2
Unless you can use compression to get more on a tape, it will take
quite a while to get everything backed up if you only use one tape
(5 or 6 days to do the first set of fulls without any incrementals).
I prefer having more than one full backup around, so I would prefer
the shorter dumpcycle. If your data doesn't change too much it might
only require two tapes for the first couple of weeks and then it
will level out and fit on one tape again. Definitely look into
compression, some data (especially text) compresses amazingly well.
If you are using hardware compression you may be able to increase
the size in your tapetype if you are not getting EOT errors.
>
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Increasing number ot tapes used.
On Mon, 22 Apr 2002 at 8:23pm, Niall O Broin wrote > Is there any problem with changing tapecycle now ? > Nope -- amanda will keep demanding new tapes utnil you've amlabelled tapecycle worth of tapes. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Increasing number ot tapes used.
I'm not long using Amanda (haven't finished a full dumpcycle yet) and I've decided that I'd like to use more tapes than I initially decided. I have dumpcycle 2 weeks runspercycle 10 tapecycle 14 tapes and I'd like to bump tapecycle up to 20 tapes or even a couple more because: a) I have the tapes already :-) b) Even if my backup load expands to nearly my full capacity (tape size * runspercycle) with tapecycle = 2 * runspercycle I'll always have 2 full dumps available. Is there any problem with changing tapecycle now ? Regards, Niall O Broin
don't know what's next
hi, I'm using freebsd4.5 stable. A lot of people on a diff mailing and irc told me to use Amanda. I've installed amanda from ports. I've also downloaded the tar.gz so I can get an example conf file on example directory. Browsing through the example directory brought me to confusion. There are sample files but I don't know which one to use. I also couldn't find a fine guide on amanda configuration from the net. Here is the spec of my freebsd. 1. sa0 at sym0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 16) 2. and sym sym0: <875> port 0x7800-0x78ff mem 0xf3fff000-0xf3ff,0xf3ffef00-0xf3ffefff irq 11 at device 16.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sa0 at sym0 bus 0 target 6 lun 0 What I wanted: 1. I want to backup another unix machine 2. Optionally, I want to backup the amanda machine itself. Thanks. Please enlighten. :-) Neil
RE: Please help -- planner askfor: lev out of range -1..10: 10
> > Thanks for your responses, Jon and Paul, > > I don't think going to 'runtapes 2' in amanda.conf is going > to fix the "lev > out of range" error, since that part happens long after my > error. The email > message starts out with > > FAILURE AND STRANGE DUMP SUMMARY: > planner: FATAL error [planner askfor: lev out of range -1..10: 10] > beowulf/usr/local RESULTS MISSING > beowulf/var/mail RESULTS MISSING > > and there's nothing in /tmp/amanda/dump/20020419/ and the > like. The planner > fails, so nothing is ever gtar'd, so there's nothing to write > to tape(s). > > Any ideas on how to clear the "lev out of range" error? Then > I'll tackle > the other errors stemming from having way to much data to > backup compared to > my tapesize. > Bart, increasing the number of tapes should address this problem, because the planner is trying to figure out what level to run for each backup, and for unknown reasons is bouncing that backup down to a lower level than dump can handle. (Or one part of planner understands that 10 is the limit and another thinks that 9 is the limit.) Additional tape space will allow planner to go with a higher level for that (and other) backups. Paul
Re: Please help -- planner askfor: lev out of range -1..10: 10
To summarize what I think you've said, you are trying to back up
~200GB on a 40GB tape, and are dynamicly rewriting your disklist
entries into ~25GB chunks. You don't say how many tapes you have
in your runtapes and tapecycle, or if you have some kind of changer
configured (even if it is chg-manual).
From the looks of the errors, Amanda is trying to do full
dumps and your disklist isn't doing what you think:
>> FAILURE AND STRANGE DUMP SUMMARY:
>> beowulf/home/proj/mm5 lev 1 FAILED [dump larger than tape, skipping
>> incremental]
>> beowulf/var/mail lev 1 FAILED [dumps way too big, must skip
>> incremental dumps]
>> (and so on, for ~30 or so directories)
This says an incremental of /home/proj/mm5 is >40GB so it can't write
it to tape. The /var/mail error (dumps way too big) indicates that
the day's backup can't fit on the tapes allotted to it, so Amanda is
having to skip backups of those filesystems.
If this was a formerly working setup, best guess is that the daily
volume of data to backup has exceeded your capacity (~40GB x runtapes).
Increasing runtapes should help (although you may have to adjust
tapecycle and runspercycle unless you have extra tapes).
I would also suggest splitting up your directories to under 20GB
instead of 25GB. If it writes one 25GB dump to tape and then starts
on another level 0, it will write 15 GB and hit EOT, and have to
start over on another tape. With a smaller directory size it will
waste less space on each tape.
Good luck,
Frank
--On Monday, April 22, 2002 09:52:10 -0600 "Brashers, Bart -- MFG, Inc."
<[EMAIL PROTECTED]> wrote:
>
> I didn't get any responses from my posting last Thursday, so I'm guessing
> I'm really up the creek on this one.
>
> If anyone has any suggestions as to how to fix this problem, please let me
> know. I've now gone 4 days without a backup, and I'm afraid I'm going to
> have to delete everything and start from scratch!
>
> Thanks,
>
> Bart
>
>
>
> After many months of operation (THANK YOU to all the developers!) last
> night's amanda Daily run gave me this error:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> planner: FATAL error [planner askfor: lev out of range -1..10: 10]
> beowulf/usr/local RESULTS MISSING
> beowulf/var/mail RESULTS MISSING
> (and so on, for every element of the disklist)
>
> The only debug files from this (9 PM) run were
> /tmp/amanda.amtrmlog.*.debug
> /tmp/amanda/amtrmidx.*.debug
> but they showed nothing particularly interesting or helpful. The latter
> said
> could not open index directory "/var/lib/amanda/Daily/index/db02/_root/"
> but that's because I recently added that machine-directory combination
> (oops, forgot it) and amanda hasn't managed to schedule a full dump, and
> won't incrementally dump a new disk.
>
> The relevant parts of my amanda.conf file are:
>
> dumpcycle 3 weeks
> runspercycle 15
> tapecycle 17 tapes
> define dumptype mydumptype {
> program "GNUTAR"
> compress none
> } (plus more of the usual options)
>
> I searched the archive, but could not find anything directly relevant. This
> "lev out of range" error happened to me once before, when I was first
> learning and setting up amanda. That time, I just deleted all the logs and
> tapelists and everything, and started from scratch. I would like to avoid
> repeating that.
>
> The only other (possibly) relevant detail is that I constantly get errors
> like:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> beowulf/home/proj/mm5 lev 1 FAILED [dump larger than tape, skipping
> incremental]
> beowulf/var/mail lev 1 FAILED [dumps way too big, must skip
> incremental dumps]
> (and so on, for ~30 or so directories)
>
> I've written a script that runs (via crontab) every afternoon and
> re-generates the disklist. It starts with a list of directories (/etc
> /var/log /var/lib /usr/spool /root /home /data). For every directory it
> finds that contains more than 25Gb, it recursively breaks it up and adds the
> sub-directories to the disklist. This is because /home is currently 153Gb,
> and would never get dumped since it's larger than a tape.
>
> I have about 200Gb to backup to a DLT8000 (40 Gb) tape drive. I recently
> went from a 2 to 3 week dumpcycle, hoping that the extra space would get rid
> of the "dumps way too big" error.
>
> Please cc me with any hints as to how to clear this up, as I only get daily
> digests and I don't want to wait until tomorrow to fix this...
>
> Bart
> --
> Bart Brashers MFG Inc.
> Air Quality Meteorologist 19203 36th Ave W Suite 101
> [EMAIL PROTECTED]Lynnwood WA 98036-5707
> http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
RE: Using Amanda
On Mon, 22 Apr 2002 at 10:29am, Morrison, Trevor (Trevor) wrote Two things: 1) Please keep amanda-users on the CC list, so that all can help out and so that it's in the archives 2) Please use some carriage returns -- I see your text as one big line. (checks headers) Ah, M$ware -- I'm so sorry. Maybe exchange is futzing with things along the way... 3) Please respond below quoted text. Oops, that was 3... :) > when I configured amanda I used the --with-user=amanda > --with-group=amanda, so I am running amandad as user amanda. I did not > use the --wtih-tmpdir=/tmp option. I copied the entry for POP# when I > created the xinetd file called amanda use amanda as the user. Would > amdump even execute if the user was not correct? Also, I noticed that > I had to give 751 permission on any directory that I wanted to back up. AII! You should *not* have to do this. > I tried adding amanda to the disk group and the root group, but to no > avail. I really do not fully understand the permissions that amanda > requires. I thought by adding amanda to the respective groups that own > the directories that that would be fine. Could you straighten me out on > this. TIA. To have xinetd run the program with *all* groups the user belongs to, you need a "groups=yes" line in the appropriate service file (i.e. /etc/xinetd.d/amanda). Also, certain bits of amanda should be installed setuid root. What does 'ls -l /usr/local/libexec | grep rws' say? This allows amanda to be root to backup stuff via tar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Tape drives
On Mon, Apr 22, 2002 at 05:16:15PM +0200, Mozzi wrote: > Hi all I was wondering whitch of these drives will have the best support under Linux > and espetially with amanda > > STD2401LW-SDAT - 20 - 40Gb - Seagate Scorpion 68 pin - SCSI > > C5686A hp surestore DAT40i Internal Drive Either should work fine. Given my experience with DAT hardware, I'd buy whichever one you can get with the longest warranty, even if that entails paying a few denarii extra. Regards, Niall O Broin
RE: Please help -- planner askfor: lev out of range -1..10: 10
You could at least temporarily go to 'runtapes 2' in amanda.conf to make
more room in each run. If you can afford more tapes, using two a day might
help, or using two tape drives with chg-multi might be good too.
Lengthening the tapecycle is going to take a while (about two tapecycles,
I'm guessing) to level out as you would expect. It sounds like you need more
tape now, which a second tape and/or a second drive could do.
Also, rather than regenerating the disklist every night, you might not
confuse amanda as much if you simply checked the directory structure every
night, and warned when a disklist entry is close to the limit. This would
allow you to plan splits better, and having your disk list entries change
less often is a good thing if you have to restore.
> -Original Message-
> From: Brashers, Bart -- MFG, Inc. [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 22, 2002 11:52 AM
> To: '[EMAIL PROTECTED]'
> Subject: Please help -- planner askfor: lev out of range -1..10: 10
>
>
>
> I didn't get any responses from my posting last Thursday, so
> I'm guessing
> I'm really up the creek on this one.
>
> If anyone has any suggestions as to how to fix this problem,
> please let me
> know. I've now gone 4 days without a backup, and I'm afraid
> I'm going to
> have to delete everything and start from scratch!
>
> Thanks,
>
> Bart
>
>
>
> After many months of operation (THANK YOU to all the developers!) last
> night's amanda Daily run gave me this error:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> planner: FATAL error [planner askfor: lev out of range -1..10: 10]
> beowulf/usr/local RESULTS MISSING
> beowulf/var/mail RESULTS MISSING
> (and so on, for every element of the disklist)
>
> The only debug files from this (9 PM) run were
> /tmp/amanda.amtrmlog.*.debug
> /tmp/amanda/amtrmidx.*.debug
> but they showed nothing particularly interesting or helpful.
> The latter
> said
> could not open index directory
> "/var/lib/amanda/Daily/index/db02/_root/"
> but that's because I recently added that machine-directory combination
> (oops, forgot it) and amanda hasn't managed to schedule a
> full dump, and
> won't incrementally dump a new disk.
>
> The relevant parts of my amanda.conf file are:
>
> dumpcycle 3 weeks
> runspercycle 15
> tapecycle 17 tapes
> define dumptype mydumptype {
> program "GNUTAR"
> compress none
> } (plus more of the usual options)
>
> I searched the archive, but could not find anything directly
> relevant. This
> "lev out of range" error happened to me once before, when I was first
> learning and setting up amanda. That time, I just deleted
> all the logs and
> tapelists and everything, and started from scratch. I would
> like to avoid
> repeating that.
>
> The only other (possibly) relevant detail is that I
> constantly get errors
> like:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> beowulf/home/proj/mm5 lev 1 FAILED [dump larger than
> tape, skipping
> incremental]
> beowulf/var/mail lev 1 FAILED [dumps way too big, must skip
> incremental dumps]
> (and so on, for ~30 or so directories)
>
> I've written a script that runs (via crontab) every afternoon and
> re-generates the disklist. It starts with a list of directories (/etc
> /var/log /var/lib /usr/spool /root /home /data). For every
> directory it
> finds that contains more than 25Gb, it recursively breaks it
> up and adds the
> sub-directories to the disklist. This is because /home is
> currently 153Gb,
> and would never get dumped since it's larger than a tape.
>
> I have about 200Gb to backup to a DLT8000 (40 Gb) tape drive.
> I recently
> went from a 2 to 3 week dumpcycle, hoping that the extra
> space would get rid
> of the "dumps way too big" error.
>
> Please cc me with any hints as to how to clear this up, as I
> only get daily
> digests and I don't want to wait until tomorrow to fix this...
>
> Bart
> --
> Bart Brashers MFG Inc.
> Air Quality Meteorologist 19203 36th Ave W Suite 101
> [EMAIL PROTECTED]Lynnwood WA 98036-5707
> http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040
>
RE: Using Amanda
On Mon, 22 Apr 2002 at 8:32am, Morrison, Trevor (Trevor) wrote > It does pass amcheck fine. I was using the root-tar backup type in the > amanda.conf file. I did not create an amanda subdirectory in /tmp; > could this be my problem? If it is what is this subdirectory for? I /tmp/amanda should get created when any part of amanda (e.g. amcheck, or amdump) is run, and it is for storage of debugging files. If it's not getting created, then there's probably some sort of permissions problem. Or did you specify a different --with-tmpdir when you ./configured amanda? > created an /amanda off the root to stage the file before backing up to > the tape drive. What have I misconfigured. TIA. It's probably a permissions problem. What user/group is running amanda? What do your (x)inetd entries look like? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: LTO Ultrium Unit
On Fri, 2002-04-19 at 21:18, Marcos Teodoro Dias Junior wrote: > Some one here have been used this tape unit with Amanda using Linux as > S.O? I'm using the IBM equivalent on a Sun-server, and it works just fine. I've added a tapetype entry to the FAQ-O-matic. Kind regards... -- Jens Rohde, System Administrator --- Eastfork Object Space (EOS), Margrethepladsen 3, 8000 Aarhus C, Denmark Tel: +45 8732 8787 / Fax: +45 8732 8788
Please help -- planner askfor: lev out of range -1..10: 10
I didn't get any responses from my posting last Thursday, so I'm guessing
I'm really up the creek on this one.
If anyone has any suggestions as to how to fix this problem, please let me
know. I've now gone 4 days without a backup, and I'm afraid I'm going to
have to delete everything and start from scratch!
Thanks,
Bart
After many months of operation (THANK YOU to all the developers!) last
night's amanda Daily run gave me this error:
FAILURE AND STRANGE DUMP SUMMARY:
planner: FATAL error [planner askfor: lev out of range -1..10: 10]
beowulf/usr/local RESULTS MISSING
beowulf/var/mail RESULTS MISSING
(and so on, for every element of the disklist)
The only debug files from this (9 PM) run were
/tmp/amanda.amtrmlog.*.debug
/tmp/amanda/amtrmidx.*.debug
but they showed nothing particularly interesting or helpful. The latter
said
could not open index directory "/var/lib/amanda/Daily/index/db02/_root/"
but that's because I recently added that machine-directory combination
(oops, forgot it) and amanda hasn't managed to schedule a full dump, and
won't incrementally dump a new disk.
The relevant parts of my amanda.conf file are:
dumpcycle 3 weeks
runspercycle 15
tapecycle 17 tapes
define dumptype mydumptype {
program "GNUTAR"
compress none
} (plus more of the usual options)
I searched the archive, but could not find anything directly relevant. This
"lev out of range" error happened to me once before, when I was first
learning and setting up amanda. That time, I just deleted all the logs and
tapelists and everything, and started from scratch. I would like to avoid
repeating that.
The only other (possibly) relevant detail is that I constantly get errors
like:
FAILURE AND STRANGE DUMP SUMMARY:
beowulf/home/proj/mm5 lev 1 FAILED [dump larger than tape, skipping
incremental]
beowulf/var/mail lev 1 FAILED [dumps way too big, must skip
incremental dumps]
(and so on, for ~30 or so directories)
I've written a script that runs (via crontab) every afternoon and
re-generates the disklist. It starts with a list of directories (/etc
/var/log /var/lib /usr/spool /root /home /data). For every directory it
finds that contains more than 25Gb, it recursively breaks it up and adds the
sub-directories to the disklist. This is because /home is currently 153Gb,
and would never get dumped since it's larger than a tape.
I have about 200Gb to backup to a DLT8000 (40 Gb) tape drive. I recently
went from a 2 to 3 week dumpcycle, hoping that the extra space would get rid
of the "dumps way too big" error.
Please cc me with any hints as to how to clear this up, as I only get daily
digests and I don't want to wait until tomorrow to fix this...
Bart
--
Bart Brashers MFG Inc.
Air Quality Meteorologist 19203 36th Ave W Suite 101
[EMAIL PROTECTED]Lynnwood WA 98036-5707
http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040
Re: What to do when tape is full?
On Mon, Apr 22, 2002 at 11:39:55AM +0200, Toralf Lund wrote: > On 19/04 2002 16:18 Dave Sherohman wrote: > > You can do this manually by not changing tapes (or leaving the tape > > drive empty) tonight, which will cause all of tonight's dumps to stay > > on the holding disk (provided it's big enough), then put the new tape > > in and run amflush tomorrow morning to collect all of the untaped dumps. > Yes, of course. Does this also mean that it's a good idea to use the > amount equivalent to one tape of the holding disk space? IMO, holding disk space is a matter of 'the more, the merrier'. You definitely want enough to handle at least one runs' worth of level 1 dumps, in case someone forgets to switch tapes or the taping never starts for some other reason. I like to go with at least twice that (disk is cheap, these days...) so that I can consolidate partial dumps if something goes wrong mid-run. > > Nope. Last night's untaped dumps will sit on the holding disk forever > > unless you either delete them or run amflush > Too bad. Yeah, it would be nice if you could set amanda up to automatically do an amflush onto the same tape after completing a normal run if the tape isn't full yet. > I'm assuming there is no way to continue writing to the tape were > something was amflushed, either, but please let me know if I'm wrong. You are correct. Amanda will not append to tapes under any circumstances. It always starts writing from the beginning of the tape.
Re: amlabel & ftape
hello again! yes, and i am using it ( ln -s /dev/nqft0 /dev/tape ). but meanwhile i have found these lines in /var/log /messeges : Apr 22 17:18:17 tester kernel: [141] zftape-read.c (check_read_access) - req_len 32768 not a multiple of block size 10240. Apr 22 17:18:18 tester kernel: [142] zftape-write.c (check_write_access) - write-count 32768 must be multiple of block-size 10240. Apr 22 17:18:18 tester kernel: [143] zftape-write.c (_zft_write) - check_write_access(req_len, &volume,&zft_pos,zft_blk_sz) failed: so i guess i am using wrong buffer size. i will have a glimpse on the ftape homepage. tx for your efforts stefan Tom Beer wrote: >Hi Stefan, > >>the device is working properly. i am able to write and read tar archives. >>the mt command is working fine, too. >> > >I'm no expert but two possiblities come to my mind. > >1) you are using a non-rewinding driver. >2) it is simply not compatible with a qic or zip drive. > >Is there a non-rewinding driver for this drive? > >Greets Tom > >
Tape drives
Hi all I was wondering whitch of these drives will have the best support under Linux and espetially with amanda STD2401LW-S DAT - 20 - 40Gb - Seagate Scorpion 68 pin - SCSI C5686A hp surestore DAT40i Internal Drive Any help will be appreciated Tnx Mozzi
Re: GNU tar version 1.13.19?
On Mon, 22 Apr 2002 at 4:59pm, Toralf Lund wrote > On 22/04 2002 15:08 Joshua Baker-LePain wrote: > > ftp://alpha.gnu.org/gnu/tar > So it is (and I quote) "unstable, incomplete, or otherwise unsuited for > official > publication." > > Seems like Red Hat and others have not "respected the good judgement of > maintainers", though, and ineed included it in an official distribution. > > Comments, anyone? You'll have to ask the tar maintainer(s) why there hasn't been an official release since (as you noted) 1999, especially given that there are obvious bugs fixed in the development releases. I would guess *that* is why just about every distro out there includes these "alpha" releases. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Why does amrecover not show all the files?
On Mon, 22 Apr 2002 at 4:01pm, Niall O Broin wrote > Latest pre-release version is 1.13.25 - is it OK to use this or should one > stick to 1.13.19 ? > I can't recall hearing anything bad about 25. Test it, of course, but it "should" work just fine. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: GNU tar version 1.13.19?
On 22/04 2002 15:08 Joshua Baker-LePain wrote: > On Mon, 22 Apr 2002 at 10:09am, Toralf Lund wrote > > > Someone mentioned on this list earlier that "exclude list" won't work > with > > GNU tar 1.13, and that version 1.13.19 was required. I think I have > > verified that; our Linux clients have tar version 1.13.19, and on those > > > "exclude list" (or tar --exclude-from) seems to work fine, while on our > > > SGI clients (which includes the server with most of the file systems) > with > > tar 1.13 it doesn't. > > > > Anyhow, the big question is: Where does version 1.13.19 come from? > > ftp://ftp.gnu.org/pub/gnu/tar has nothing newer than 1.13 from 1999. > > > ftp://alpha.gnu.org/gnu/tar So it is (and I quote) "unstable, incomplete, or otherwise unsuited for official publication." Seems like Red Hat and others have not "respected the good judgement of maintainers", though, and ineed included it in an official distribution. Comments, anyone? - Toralf
Re: amlabel & ftape
Hi Stefan, > the device is working properly. i am able to write and read tar archives. > the mt command is working fine, too. I'm no expert but two possiblities come to my mind. 1) you are using a non-rewinding driver. 2) it is simply not compatible with a qic or zip drive. Is there a non-rewinding driver for this drive? Greets Tom
Re: amlabel & ftape
hi tom, the device is working properly. i am able to write and read tar archives. the mt command is working fine, too. clueless regards stefan
Re: Questions with chg-zd-mtx
I think u are looking for the "OFFLINE_BEFORE_UNLOAD=1" setting in chg-zd-mtx Nate DeLong wrote: > > > Ok. It wasn't until I went to BRU's website that I found the following > command (that worked): > > # mt -f /dev/nst0 offline > > Then I can finish up by issuing a " mtx -f /dev/sga unload 1 ". > > So, that explains what I've done... Now I was hoping someone could steer me > in the right direction with chg-zd-mtx. It does support using the " mt > offline" but do I need to do anything special in my instance. And, > is my instance unusual, or is the tape drive itself usually seen as > /dev/nst0? > > Sorry for the longwinded e-mail. > > Nate D.
Re: amlabel & ftape
is this command, replacing /dev/tape with the correct value working sufficiently? mt -f /dev/tape rewind Greets Tom
Re: Why does amrecover not show all the files?
On Mon, Apr 22, 2002 at 09:16:28AM -0400, Joshua Baker-LePain wrote: > On Mon, 22 Apr 2002 at 8:57am, Niall O Broin wrote > > > I'm using amanada with SuSE 7.3 which has tar 1.3.18 which seems to work > > fine. I just installed SuSE 8.0 on a box and it also has 1.3.18. I knew > > about the silly numbers issue (bit me before elsewhere) but 1.3.18 doesn't > > have that. Is there some big amanda problem which exists with 1.3.18 and > > doesn't with 1.3.19 ? > > > There are two patches on http://www.amanda.org/patches.html relating to > tar 1.13.18 (i.e. patches to apply to tar before using it with amanda). > Seems easier to me to use 1.13.19. Latest pre-release version is 1.13.25 - is it OK to use this or should one stick to 1.13.19 ? Regards, Niall O Broin
Re: Why does amrecover not show all the files?
On Mon, 22 Apr 2002 at 8:57am, Niall O Broin wrote > I'm using amanada with SuSE 7.3 which has tar 1.3.18 which seems to work > fine. I just installed SuSE 8.0 on a box and it also has 1.3.18. I knew > about the silly numbers issue (bit me before elsewhere) but 1.3.18 doesn't > have that. Is there some big amanda problem which exists with 1.3.18 and > doesn't with 1.3.19 ? > There are two patches on http://www.amanda.org/patches.html relating to tar 1.13.18 (i.e. patches to apply to tar before using it with amanda). Seems easier to me to use 1.13.19. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Using Amanda
On Sun, 21 Apr 2002 at 8:38pm, Trevor Morrison wrote > FAILURE AND STRANGE DUMP SUMMARY: > stud.haili /var/tmp lev 0 FAILED [missing result for /var/tmp in > stud.hailix.com response] > stud.haili /usr/src lev 0 FAILED [missing result for /usr/src in > stud.hailix.com response] > stud.haili /chroot/named lev 0 FAILED [missing result for > /chroot/named in stud.hailix.com response] > stud.haili /etc lev 0 FAILED [missing result for /etc in > stud.hailix.com response] > Does this config pass amcheck? What backup tool are you using (dump or tar)? What are the contents of the relevant /tmp/amanda/sendsize*debug files on stud? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Questions with chg-zd-mtx
I have a Dell PowerVailt 120T DLT library, and want to see if I can get it to work with Amanda. When working up to setting up chg-zd-mtx, I seem to be having some weird issues: If I cat /proc/scsi/scsi, here is my output: Attached devices: Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: ADIC Model: FastStor DLT Rev: D118 Type: Medium Changer ANSI SCSI revision: 02 Host: scsi2 Channel: 00 Id: 03 Lun: 00 Vendor: BNCHMARK Model: DLT1 Rev: 391B Type: Sequential-AccessANSI SCSI revision: 02 So it does see the loader device and the tape drive itself. If I run mtx inquirys against those devices, here's what I get: # mtx -f /dev/sga inquiry Product Type: Medium Changer Vendor ID: 'ADIC' Product ID: 'FastStor DLT' Revision: 'D118' Attached Changer: No # mtx -f /dev/sgb inquiry Product Type: Tape Drive Vendor ID: 'BNCHMARK' Product ID: 'DLT1' Revision: '391B' Attached Changer: No That looks good. So now, if I try loading a tape using " mtx -f /dev/sga load 1 " it works. But if I try unloading in the same fashion, I receive the " MOVE MEDIUM from Element Address 82 to 1 Failed " error. Which means I should use mt to rewind & eject the tape. Here's the results of using mt against those devices: # mt -f /dev/sga offline /dev/sga: Permission denied # mt -f /dev/sgb offline /dev/sgb: Permission denied Ok. It wasn't until I went to BRU's website that I found the following command (that worked): # mt -f /dev/nst0 offline Then I can finish up by issuing a " mtx -f /dev/sga unload 1 ". So, that explains what I've done... Now I was hoping someone could steer me in the right direction with chg-zd-mtx. It does support using the " mt offline" but do I need to do anything special in my instance. And, is my instance unusual, or is the tape drive itself usually seen as /dev/nst0? Sorry for the longwinded e-mail. Nate D.
Re: GNU tar version 1.13.19?
On Mon, 22 Apr 2002 at 10:09am, Toralf Lund wrote > Someone mentioned on this list earlier that "exclude list" won't work with > GNU tar 1.13, and that version 1.13.19 was required. I think I have > verified that; our Linux clients have tar version 1.13.19, and on those > "exclude list" (or tar --exclude-from) seems to work fine, while on our > SGI clients (which includes the server with most of the file systems) with > tar 1.13 it doesn't. > > Anyhow, the big question is: Where does version 1.13.19 come from? > ftp://ftp.gnu.org/pub/gnu/tar has nothing newer than 1.13 from 1999. > ftp://alpha.gnu.org/gnu/tar -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Why does amrecover not show all the files?
On Sun, Apr 21, 2002 at 05:09:57PM -0400, Joshua Baker-LePain wrote: > On Sun, 21 Apr 2002 at 8:56pm, David Trusty wrote > > > Thanks for responding. My tar version is 1.13. > > Bad. Bad bad bad. > > > /usr/local/bin/gunzip -c 20020421_0.gz | more > > 07460550617/./ > *snip* > > Yep -- that's it. Your index files are corrupt (as evidenced by those big > numbers at the beginning of each entry) due to a bad version of tar. You > need at least 1.13.19, which is available at alpha.gnu.org. I'm using amanada with SuSE 7.3 which has tar 1.3.18 which seems to work fine. I just installed SuSE 8.0 on a box and it also has 1.3.18. I knew about the silly numbers issue (bit me before elsewhere) but 1.3.18 doesn't have that. Is there some big amanda problem which exists with 1.3.18 and doesn't with 1.3.19 ? Regards, Niall O Broin
amlabel & ftape
hello everboby, before i am going to buy an expensive dlt-streamer i'd like to do some testing with an old iomega 250 floppy-qic. I have configured all as discripted in the man-pages but unfortunately amlabel closes with an error. here the amlabel output: amanda@tester:~> amlabel test tgl01 rewinding, reading label, not an amanda tape rewinding, writing label tgl01 amlabel: writing label: Invalid argument has anybody any suggestion? regards stefan
Re: What to do when tape is full?
On 19/04 2002 16:18 Dave Sherohman wrote: > On Fri, Apr 19, 2002 at 09:25:02AM +0200, Toralf Lund wrote: > > Well, obviously, the simple answer is "run amflush", which is what I > did > > the last time I got this. The problem with this was that the flush > > required a tape of its own, which was not what I wanted; what I really > had > > in mind was to write the dumps along with next day's backups. > > You can do this manually by not changing tapes (or leaving the tape > drive empty) tonight, which will cause all of tonight's dumps to stay > on the holding disk (provided it's big enough), then put the new tape > in and run amflush tomorrow morning to collect all of the untaped dumps. > > (As I've mentioned before, I've got a flaky tape drive, so I have a > holding disk that's big enough for two full nights' dumps and frequently > find myself consolidating them in this manner.) Yes, of course. Does this also mean that it's a good idea to use the amount equivalent to one tape of the holding disk space? > > Perhaps Amanda would have handled this automatically > > if I had left the holding disk alone? > > Nope. Last night's untaped dumps will sit on the holding disk forever > unless you either delete them or run amflush Too bad. I'm assuming there is no way to continue writing to the tape were something was amflushed, either, but please let me know if I'm wrong. - Toralf
GNU tar version 1.13.19?
Someone mentioned on this list earlier that "exclude list" won't work with GNU tar 1.13, and that version 1.13.19 was required. I think I have verified that; our Linux clients have tar version 1.13.19, and on those "exclude list" (or tar --exclude-from) seems to work fine, while on our SGI clients (which includes the server with most of the file systems) with tar 1.13 it doesn't. Anyhow, the big question is: Where does version 1.13.19 come from? ftp://ftp.gnu.org/pub/gnu/tar has nothing newer than 1.13 from 1999. -- Toralf Lund <[EMAIL PROTECTED]>
