Re: Too many taper retries
--On Thursday, September 12, 2002 11:03:48 +0800 Alvin Ko <[EMAIL PROTECTED]> wrote: > I used amanda 2.4.2p2 with a DDS-3 tape drive to do a full backup of my > Linux last night. In the amanda.conf file, I used chg-manual as the changer > with 3 tapes. My /export/home folder has 23GB data. I had labeled three > tapes (Tape-01, Tape-02, Tape-03) and then start the backup. 3 hours later, > she asked me to insert backup tape into slot 1. When amdump completed, I got > the following report. > --- > These dumps were to tapes Tape-01, Tape-02, Tape-03. > The next 3 tapes Amanda expects to used are: a new tape, a new tape, a new > tape. > > FAILURE AND STRANGE DUMP SUMMARY: > localhost /export/home lev 0 FAILED [too many taper retries] > ... > NOTES: > ... > taper: tape Tape-01 kb 12013824 fm 7 writing file: No space left on device > taper: retrying localhost:/export/home.0 on new tape: [writing file: No > space left on device] > taper: tape Tape-02 kb 12004832 fm 1 writing file: No space left on device > taper: retrying localhost:/export/home.0 on new tape: [writing file: No > space left on device] > taper: tape Tape-03 kb 0 fm 0 [OK] > driver: Could not rmdir /mnt/hdc1/20020911: Directory not empty > --- > She could not backup my /export/home folder into multiple tapes. Anybody > knows why? > > Best Regards, > > Alvin K. T. Ko Amanda can not backup any filesystem that is bigger than a single tape. Evidently your tapetype has a size listed greater than the actual capacity of your tape or Amanda wouldn't even have tried. You mentioned DDS3 which has a 12GB raw capacity, and that is about how much taper says it wrote before getting the 'no space' error. If your data is highly compressible, you might be able to get it to fit using compression, otherwise you will have to split your disklist entry for /export/home into a few (or several) subdirectories that will each fit on a tape and use tar to do the backups (dump usually either won't back up subdirectories or will be unable to keep track of the dumpdates for them). Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Too many taper retries
On Wednesday 11 September 2002 23:03, Alvin Ko wrote: >I used amanda 2.4.2p2 with a DDS-3 tape drive to do a full backup > of my Linux last night. In the amanda.conf file, I used > chg-manual as the changer with 3 tapes. My /export/home folder > has 23GB data. I had labeled three tapes (Tape-01, Tape-02, > Tape-03) and then start the backup. 3 hours later, she asked me > to insert backup tape into slot 1. When amdump completed, I got > the following report. >--- >These dumps were to tapes Tape-01, Tape-02, Tape-03. >The next 3 tapes Amanda expects to used are: a new tape, a new > tape, a new tape. > >FAILURE AND STRANGE DUMP SUMMARY: > localhost /export/home lev 0 FAILED [too many taper retries] >... >NOTES: > planner: Adding new disk localhost:/boot. > planner: Adding new disk localhost:/usr. > planner: Adding new disk localhost:/. > planner: Adding new disk localhost:/export/home. > planner: Adding new disk localhost:/home. > planner: Adding new disk localhost:/var. > planner: Adding new disk localhost:/opt. > taper: tape Tape-01 kb 12013824 fm 7 writing file: No space left > on device taper: retrying localhost:/export/home.0 on new tape: > [writing file: No space left on device] > taper: tape Tape-02 kb 12004832 fm 1 writing file: No space left > on device taper: retrying localhost:/export/home.0 on new tape: > [writing file: No space left on device] > taper: tape Tape-03 kb 0 fm 0 [OK] > driver: Could not rmdir /mnt/hdc1/20020911: Directory not empty >--- >She could not backup my /export/home folder into multiple tapes. > Anybody knows why? > >Best Regards, > >Alvin K. T. Ko How big is /export/home? If its bigger than your DDS3 tape, you will have to break that entry up into even smaller pieces. Basicly, amanda cannot span more than one tape with a single filesystem, and probably never will. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Too many taper retries
I used amanda 2.4.2p2 with a DDS-3 tape drive to do a full backup of my Linux last night. In the amanda.conf file, I used chg-manual as the changer with 3 tapes. My /export/home folder has 23GB data. I had labeled three tapes (Tape-01, Tape-02, Tape-03) and then start the backup. 3 hours later, she asked me to insert backup tape into slot 1. When amdump completed, I got the following report. --- These dumps were to tapes Tape-01, Tape-02, Tape-03. The next 3 tapes Amanda expects to used are: a new tape, a new tape, a new tape. FAILURE AND STRANGE DUMP SUMMARY: localhost /export/home lev 0 FAILED [too many taper retries] ... NOTES: planner: Adding new disk localhost:/boot. planner: Adding new disk localhost:/usr. planner: Adding new disk localhost:/. planner: Adding new disk localhost:/export/home. planner: Adding new disk localhost:/home. planner: Adding new disk localhost:/var. planner: Adding new disk localhost:/opt. taper: tape Tape-01 kb 12013824 fm 7 writing file: No space left on device taper: retrying localhost:/export/home.0 on new tape: [writing file: No space left on device] taper: tape Tape-02 kb 12004832 fm 1 writing file: No space left on device taper: retrying localhost:/export/home.0 on new tape: [writing file: No space left on device] taper: tape Tape-03 kb 0 fm 0 [OK] driver: Could not rmdir /mnt/hdc1/20020911: Directory not empty --- She could not backup my /export/home folder into multiple tapes. Anybody knows why? Best Regards, Alvin K. T. Ko
Re: amlabel: Operation not permitted
On Wed, Sep 11, 2002 at 05:21:39PM -0400, Caitlyn M. Martin wrote: > > Hi, everyone, > > I'm trying to setup a new backup server running Red Hat and Amanda > 2.4.2p2. I'm using an Exabyte VXA-1 RakPaq, basically two LVD SCSI > VXA-1 tape drives which I have daisy chained together. vxaTool reports > that the first drive is /dev/sga and the second is /dev/sgb. I can > access either drive with mt or vxaTool, so I believe my issue is with > Amanda. > > I'm trying to label a tape before doing my first (test) backup with the > command: > > su -c amanda "amlabel DailySet1 DailySet101" > > The system first responds: > > rewinding > amlabel: rewinding tape: Operation not permitted > > I suspect a permissions issue as I can rewind the tape as root using > vxaTool. Also, if I run the amlabel command as root it will say: > > amlabel: running as user "root" instead of "amanda" > > I know I'm doing something simple and stupid wrong, but for the life of > me I can't see what. I can post relevant sections of my amanda.conf > file if it will help. > > I've setup Amanda before, but it was on Solaris and it was a few years > ago. Any clues where I'm being thickheaded? What are the permissions on sga and sgb and vxaTool? $ ls -l -L /dev/sga /dev/sgb What operations can you perform with mt. Is rewind one of them? Are sga and sgb the actual tape read and write devices or the changer mechanisms? What chg-XXX driver are you using and as amanda, can you cd to the config dir, then run chg-XXX status or info or slot # or ???. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amlabel: Operation not permitted
Hi, everyone, I'm trying to setup a new backup server running Red Hat and Amanda 2.4.2p2. I'm using an Exabyte VXA-1 RakPaq, basically two LVD SCSI VXA-1 tape drives which I have daisy chained together. vxaTool reports that the first drive is /dev/sga and the second is /dev/sgb. I can access either drive with mt or vxaTool, so I believe my issue is with Amanda. I'm trying to label a tape before doing my first (test) backup with the command: su -c amanda "amlabel DailySet1 DailySet101" The system first responds: rewinding amlabel: rewinding tape: Operation not permitted I suspect a permissions issue as I can rewind the tape as root using vxaTool. Also, if I run the amlabel command as root it will say: amlabel: running as user "root" instead of "amanda" I know I'm doing something simple and stupid wrong, but for the life of me I can't see what. I can post relevant sections of my amanda.conf file if it will help. I've setup Amanda before, but it was on Solaris and it was a few years ago. Any clues where I'm being thickheaded? Thanks, Cait
amcheck -c and NAK error
I'm trying to pin down a amanda problem and get over the hurdle of running amcheck(8) to ensure that client and server are set up properly. Right now, I'm not sure if the problem is with my AMANDA client or with the server. Here is what I have. An AMANDA server running version 2.4.2p2-1. I think my server system is RedHat version 7.1. amanda-server-2.4.2p2-1 amanda-2.4.2p2-1 A version of 7.2 Redhat amanda client running version 2.4.2p2-1 amanda-2.4.2p2-1 amanda-client-2.4.2p2-1 >From the server, I invoke the command: amcheck -c "RonSet", where RonSet my personalized configuration file. It's pretty standard with very minimal modifications. I get the error: Amanda Backup Client Hosts Check ERROR: rgoodwyn-lx.idev.atl.hp.com NAK: service selfcheck unavailable Client check: 1 host checked in 0.030 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) On the client side, I have verified that the directory /tmp/amanda is created. This directory contains some debug information that is useful. Output from /tmp/amanda (I'm removing all that constant jazz...) got packet: Amanda 2.4 REQ HANDLE 000-303F0608 SEQ 1031769257 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR /home 0 OPTIONS |;bsd-auth;compress-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gt ar; execute access to "/usr/local/libexec/selfcheck" denied sending nack: Amanda 2.4 NAK HANDLE 000-303F0608 SEQ 1031769257 ERROR service selfcheck unavailable amandad: pid 1061 finish time Wed Sep 11 14:39:12 2002 Are there any issues if the version of the OS where AMANDA is running differs from that of the client? I wouldn't think so. I had this working until I upgraded my client to release 7.2 of RedHat. Well if you have any insights I would be very grateful. Many Thanks, Ron Goodwyn
Re: Working with multiple tape drives----- Ammended
--On Monday, April 27, 2020 18:01:38 -0400 Gene Heskett <[EMAIL PROTECTED]> wrote: > On Wednesday 11 September 2002 12:50, Quinn, Richard C. - > Collinsville IT wrote: >> E: Working with multiple tape drives- Ammended >> Date: Wed, 11 Sep 2002 11:50:51 -0500 > From: "Quinn, Richard C. - Collinsville IT" >> <[EMAIL PROTECTED]> To: "Gene Heskett" >> <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> >> >> Yes, >> >> my box is a Sparc E-450 running Sol 6. >> >> I am using the SST driver for Solaris 6. >> >> I think it(SST Driver) is the predecessor to Solaris' sgen driver >> for Sol 7 and 8. >> >> Here are the boot messages for the Jukebox robotic arm and its 2 >> QUANTUM drives >> >> Sep 4 12:30:12 sun1 unix: sst3:found Changer device at >> tgt0, lun0 >> Sep 4 12:30:12 sun1 unix: sst3:Vendor/Product ID = STK >> 9730 Sep 4 12:30:12 sun1 unix: sst3 at pci1000,f7: >> Sep 4 12:30:12 sun1 unix: target 0 lun 0 >> Sep 4 12:30:12 sun1 unix: sst3 is /pci@1f,4000/scsi@4,1/sst@0,0 > > And try as I might, includeing hilighting the cmplete message, there > is something in the listing that prevents me from quoting it all. > > The bottom line is that for this, I think you are going to need the > manuals on this device. Its entirely possible it has a problem. I > find it different in that it finds the robot at address 0, and the > two drives at address 1 and 2. But properly set in amanda.conf and > chg-scsi.conf, I don't believe that to be a problem. > > You may have to either take it to a winderz box and check it with > their software, or return it to the vendor with your impression of > the problem. > You might also see if you can install mtx on your server (it requires GNU make and possibly a few other things not standard on Solaris) and use that to control your changer. If you can use mtx commands to control your library from the command line then it should be straightforward to use Amanda's chg-mtx driver instead of chg-scsi. I believe mtx accesses the changer through a raw device, bypassing the scsi driver, and can sometimes do more with some changers. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Working with multiple tape drives----- Ammended
On Mon, Apr 27, 2020 at 06:01:38PM -0400, Gene Heskett wrote: > On Wednesday 11 September 2002 12:50, Quinn, Richard C. - > > > >Yes, > > > >my box is a Sparc E-450 running Sol 6. > > > >I am using the SST driver for Solaris 6. > > > >I think it(SST Driver) is the predecessor to Solaris' sgen driver > > for Sol 7 and 8. > > > >Here are the boot messages for the Jukebox robotic arm and its 2 > > QUANTUM drives > > > >Sep 4 12:30:12 sun1 unix: sst3:found Changer device at > > tgt0, lun0 > >Sep 4 12:30:12 sun1 unix: sst3:Vendor/Product ID = STK > > 9730 Sep 4 12:30:12 sun1 unix: sst3 at pci1000,f7: > >Sep 4 12:30:12 sun1 unix: target 0 lun 0 > >Sep 4 12:30:12 sun1 unix: sst3 is /pci@1f,4000/scsi@4,1/sst@0,0 > > And try as I might, includeing hilighting the cmplete message, there > is something in the listing that prevents me from quoting it all. > > The bottom line is that for this, I think you are going to need the > manuals on this device. Its entirely possible it has a problem. I > find it different in that it finds the robot at address 0, and the > two drives at address 1 and 2. But properly set in amanda.conf and > chg-scsi.conf, I don't believe that to be a problem. > > You may have to either take it to a winderz box and check it with > their software, or return it to the vendor with your impression of > the problem. Richard, I visited the StorageTek website yesterday hoping to see if they had online manuals. Seems that to get to the heard of the support pages you have to register and I was disinclined. However while reading some pages, and later visiting docs.sun.com searching for storagetek, some software was mentioned lots of times. I "think" the name was ACLCS, and it seemed to be the equivalent of mtx, something to control the jukebox. Solaris versions were mentioned. I may have gotten totally the wrong impression, if so sorry for the wild goose chase. But do you have, or know of the software? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumpcycle-runspercycle-tapecycle
On Wednesday 11 September 2002 13:17, Anne M. Hammond wrote: >On Wed Sep 11, 6:52am Gene Heskett wrote: >>But with only 7 tapes, there is a possibility of over-writing the >>last full of that disklist entry with only an incremental as >>amanda gets the scheduling adjusted. No one here would >>recommend only 7 tapes, the murphy style disaster is >>inevitable... >> >>You need at least 14, and I have 20 in my own rotation, so I'm >>always assured that there are at least 2 fulls available in the >>unlikely event a disk goes belly up on me. > >I asked Gene for hise amanda.conf entries, which are: > >dumpcycle 1 week >runspercycle 7 >tapecycle 20 > >Using this configuration, I understand amanda will schedule >a level 0 each week (dumpcycle). At any one time, you would >have 3 level 0 dumps (in case of tape error, or a dump could >not be restored). > >So tapecycle does not need to be a multiple of dumpcycle or >runspercycle? > >It's not quite clear what amanda.conf recommends the "extra" >tapes in the tapecycle are for--after amanda has been through >one cycle of the tapes, there are really no more "extra" tapes?? > >amanda.conf: >tapecycle 19 tapes # the number of tapes in rotation ># 4 weeks (dumpcycle) times 5 tapes per > week (just # the weekdays) plus a few to handle errors that # > need amflush and so we do not overwrite the full # backups > performed at the beginning of the previous # cycle > Amanda will use ALL labeled tapes in the rotation, in order, unless WE mess it up, and then start over at the top of the list reusing them in the same order.\ -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: personal request - no need for double mail
On Wednesday 11 September 2002 13:10, Jon LaBadie wrote: >On Wed, Sep 11, 2002 at 10:00:50AM -0400, Jon LaBadie wrote: >> In addressing replies and follow-ups, >> I kindly request either a list posting or a private email. >> Both are unnecessary. > >It has been pointed out to me that I may be the cause of my own > anguish. > >Apologies and "Never Mind". Humm, do you talk to yourself that way often, Jon? I thought I was the only one who did that. :-) -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Working with multiple tape drives----- Ammended
On Wednesday 11 September 2002 12:50, Quinn, Richard C. - Collinsville IT wrote: >E: Working with multiple tape drives- Ammended >Date: Wed, 11 Sep 2002 11:50:51 -0500 From: "Quinn, Richard C. - Collinsville IT" > <[EMAIL PROTECTED]> To: "Gene Heskett" > <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > >Yes, > >my box is a Sparc E-450 running Sol 6. > >I am using the SST driver for Solaris 6. > >I think it(SST Driver) is the predecessor to Solaris' sgen driver > for Sol 7 and 8. > >Here are the boot messages for the Jukebox robotic arm and its 2 > QUANTUM drives > >Sep 4 12:30:12 sun1 unix: sst3:found Changer device at > tgt0, lun0 >Sep 4 12:30:12 sun1 unix: sst3:Vendor/Product ID = STK > 9730 Sep 4 12:30:12 sun1 unix: sst3 at pci1000,f7: >Sep 4 12:30:12 sun1 unix: target 0 lun 0 >Sep 4 12:30:12 sun1 unix: sst3 is /pci@1f,4000/scsi@4,1/sst@0,0 And try as I might, includeing hilighting the cmplete message, there is something in the listing that prevents me from quoting it all. The bottom line is that for this, I think you are going to need the manuals on this device. Its entirely possible it has a problem. I find it different in that it finds the robot at address 0, and the two drives at address 1 and 2. But properly set in amanda.conf and chg-scsi.conf, I don't believe that to be a problem. You may have to either take it to a winderz box and check it with their software, or return it to the vendor with your impression of the problem. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: personal request - no need for double mail
On Wed, Sep 11, 2002 at 10:00:50AM -0400, Jon LaBadie wrote: > > In addressing replies and follow-ups, > I kindly request either a list posting or a private email. > Both are unnecessary. It has been pointed out to me that I may be the cause of my own anguish. Apologies and "Never Mind". -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dumpcycle-runspercycle-tapecycle
On Wed Sep 11, 6:52am Gene Heskett wrote: >But with only 7 tapes, there is a possibility of over-writing the >last full of that disklist entry with only an incremental as >amanda gets the scheduling adjusted. No one here would >recommend only 7 tapes, the murphy style disaster is >inevitable... > >You need at least 14, and I have 20 in my own rotation, so I'm >always assured that there are at least 2 fulls available in the >unlikely event a disk goes belly up on me. I asked Gene for hise amanda.conf entries, which are: dumpcycle 1 week runspercycle 7 tapecycle 20 Using this configuration, I understand amanda will schedule a level 0 each week (dumpcycle). At any one time, you would have 3 level 0 dumps (in case of tape error, or a dump could not be restored). So tapecycle does not need to be a multiple of dumpcycle or runspercycle? It's not quite clear what amanda.conf recommends the "extra" tapes in the tapecycle are for--after amanda has been through one cycle of the tapes, there are really no more "extra" tapes?? amanda.conf: tapecycle 19 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle TIA
RE: Working with multiple tape drives----- Ammended
Yes, my box is a Sparc E-450 running Sol 6. I am using the SST driver for Solaris 6. I think it(SST Driver) is the predecessor to Solaris' sgen driver for Sol 7 and 8. Here are the boot messages for the Jukebox robotic arm and its 2 QUANTUM drives Sep 4 12:30:12 sun1 unix: sst3:found Changer device at tgt0, lun0 Sep 4 12:30:12 sun1 unix: sst3:Vendor/Product ID = STK 9730 Sep 4 12:30:12 sun1 unix: sst3 at pci1000,f7: Sep 4 12:30:12 sun1 unix: target 0 lun 0 Sep 4 12:30:12 sun1 unix: sst3 is /pci@1f,4000/scsi@4,1/sst@0,0 -- -- Sep 4 12:30:17 sun1 unix: st57: Sep 4 12:30:17 sun1 unix: st57 at pci1000,f7: Sep 4 12:30:17 sun1 unix: target 1 lun 0 Sep 4 12:30:17 sun1 unix: st57 is /pci@1f,4000/scsi@4,1/st@1,0 *** ***This Bottom entry is the Problem Tape Drive *** Sep 4 12:30:17 sun1 unix: st58: Sep 4 12:30:17 sun1 unix: st58 at pci1000,f7: Sep 4 12:30:17 sun1 unix: target 2 lun 0 Sep 4 12:30:17 sun1 unix: st58 is /pci@1f,4000/scsi@4,1/st@2,0 and, as I said before, I can write and read and such to the tape drive. As Tien That Ton stated earlier, I am starting to wonder if the issue might be with the Robotic Arm. AFAIK, the arm recalibrates itself upon powering on (At least that's what the messages say). If I knew the SCSI commands, I'd send some SCSI commands to the robotic arm directly. Would I find such a thing in the source code of chg-scsi, maybe in chg-scsi.c? -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 10, 2002 7:25 PM To: Quinn, Richard C. - Collinsville IT; [EMAIL PROTECTED] Subject: Re: Working with multiple tape drives- Ammended On Tuesday 10 September 2002 16:36, Quinn, Richard C. - Collinsville IT wrote: >Hi again, > >I think I've narrowed it down just a spell. >Gene was helpfull with some advice regarding the "tapedev" > variable in amanda.conf. >Unfortunately that didn't seem to fix the issue, which I think MAY > be scsi related and not amanda related. > >In a nutshell the problem is this: >I cannot get the robotic arm to take the tapes in and out of one > of my 2 DLT drives. >I will set up chg-scsi to only configure for one drive(the one > that is being ignored by my robotic arm). >I'll send a chg-scsi -resetcommand and get this error: >0 slot 0 move failed > > > >However, upon issuing the chg-scsi command, the tape drive will > rewind and offline itself, and yes, I can do ufsdumps to the > drive. So, if it is a SCSI problem, I am not sure what or how, > AFAIK, ufsdump and mt rew ultimately issue scsi commands don't > they? > >It doesn't seem to be the drive so much as the arm going to the > drive. > >Just before I get this ''move failed'' error, the robotic arm will > move in front of the drive, then move down an inch, then back up > an inch, then down, and THEN, I get the ''move failed'' error. > > > >Here is a snip of the errors I get in >/tmp/amanda-dbg/chg-scsi-#.debug and /var/adm/messages > respectively: > > > >== >== # START LookupElement ># STOP LookupElement (DTE) ># START LookupElement ># STOP LookupElement (STE) >ioctl on 4 failed, errno 5, ret -1 ># START DecodeSense >SCSI_ExecuteCommand:Sense Keys >ErrorCode 1d >Valid 1 >ASC 90 >ASCQ 10 >Sense key 0F >Reserved >== >== > = >=== > > >Sep 10 14:35:06 sun1 unix: WARNING: /pci@1f,4000/scsi@4,1/sst@0,0 >(sst3): >Sep 10 14:35:06 sun1 unix: Error for Command: 0xa5> Error Level: Fatal >Sep 10 14:35:06 sun1 unix: Requested Block: 0 >Error Block: 0 >Sep 10 14:35:06 sun1 unix: Vendor: STK >Serial Number: >Sep 10 14:35:06 sun1 unix: Sense Key: Illegal Request >Sep 10 14:35:06 sun1 unix: ASC: 0x3a (medium not present), > ASCQ: 0x0, FRU: 0x0 >== >== > > > >Any ideas? > > >Does anyone speak SCSI? Not very well I'm afraid. But an idea is beginning to jell in the back of my mind, and it has to do with SOME drives penchant for assigning the robot (s) to the same address as the drive itself, but to a non zero LUN at that address. Now, AFAIK, the lkernel, when initializing itself, does the device scan, it scans all LUNs at each address on the bus, and is the major reason for a noticable pause in the boot proceedings at that point. Such tomfoolery with the bus address and LUN's is normally recorded in /var/log/dmesg, so please post that section of it, probably not more than 20 lines to this list and let us see what was actually detected and recorded by the kernel at your last bootup. It might be cluefull to one of
Re: win32
On Wed, 11 Sep 2002, Galen Johnson wrote: > Hello gang, > > A while back I had sent a request regarding backing up windows machines > without having to deal with samba. Someone had responded with the win32 > Amanda client on sourceforge. I have looked it up and it seems like > it'll do what I want. However, it hasn't been touched in 18 months. Is > anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully?
win32
Hello gang, A while back I had sent a request regarding backing up windows machines without having todeal with samba. Someone had responded with the win32 amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with amanda 2.4.3.b4? =G=
amverify only on most recent set
Is there a way to get amverify to only check tapes from the most recently completed backup? I currently have runtapes set to 3 (to allow for new hosts I'm going to be adding in the next few weeks) however the current backup only takes one tape. amverify is currently scanning it's 3rd tape (from a backup 2 days ago) This takes a ton of time to scan tapes that have already been scanned. Any way around this other than writing a script to check the output of amtape show and run amverify per slot on the newest tapes only? Also, if you specify a slot with amverify does it then ignore the runtapes option? - andrew __ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute
Reading planner output
Is there any information on reading the output of planner? I'd like to get some idea as I make entries to the disklist as to how much I'm increasing the backup sizes. (or is there a better way to do it) - andrew __ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute
personal request - no need for double mail
I'm moderately active on the list, both posting and through private emails. In addressing replies and follow-ups, I kindly request either a list posting or a private email. Both are unnecessary. Others may have vastly differing opinion. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapetype
Gene Heskett wrote: > On Wednesday 11 September 2002 06:28, Mozzi wrote: > >>Hi again all >> >>When running typetype what do I spesify as my type size ? >>I have a 40/80 Gig dlt tape drive >>so will my command be >>typetype -e 40 -f /dev/nst0 -t Tandberg VS80 DLT >>or >>typetype -e 80 -f /dev/nst0 -t Tandberg VS80 DLT >>? > > > Turn off any hardware compression first, and *leave it off*, then > try the first version. With hardware compression on, the data from > /dev/urandom will expand somewhat and tapetype will return an > amount thats conservative, probably by double digit percentages. > > Amanda needs to know how much the tape can hold because she counts > bytes being sent to the medium AFTER Cool so we want the "real" capacity witch is 40 Gigs any compression she might have > been told to do via your chosen dumptype in the disklist. Since > software compression can, except for already compressed archive > files, very handily beat the socks off the hardware rll, you'll get > quite a bit more real capacity out of a tape with software. One > session last week had nearly 7 gigs of src, on tape it was well > under 2gigs, using less than half a DDS2 tape. > > In your disklist, don't compress directories full of archives, and > do compress the other stuff unless the email from amanda says the > compression was over 100% for that entry, which tells you the data > grew. > Tnx a lot Mozzi
RE: index tee error : Fixed
A follow up: Well, something like three or four weeks ago I posted an issue regarding that my amanda server logs were having "index tee: connection reset by peer" errors. These did not seem to be interfering with the archiving of data to tape. Possibly it was interfering with the writing of the indices, but I didn't check. My system was lacking the "holdingdisk" type of disklist, so I added it in about a week ago. It seems to have fixed the problem. I have been checking logs daily, and seen no recurrence of that issue. Michael Martinez System Administrator Information Systems and Technology Management CSREES - United States Department of Agriculture
Re: tapetype
On Wednesday 11 September 2002 06:28, Mozzi wrote: >Hi again all > >When running typetype what do I spesify as my type size ? >I have a 40/80 Gig dlt tape drive >so will my command be >typetype -e 40 -f /dev/nst0 -t Tandberg VS80 DLT >or >typetype -e 80 -f /dev/nst0 -t Tandberg VS80 DLT >? Turn off any hardware compression first, and *leave it off*, then try the first version. With hardware compression on, the data from /dev/urandom will expand somewhat and tapetype will return an amount thats conservative, probably by double digit percentages. Amanda needs to know how much the tape can hold because she counts bytes being sent to the medium AFTER any compression she might have been told to do via your chosen dumptype in the disklist. Since software compression can, except for already compressed archive files, very handily beat the socks off the hardware rll, you'll get quite a bit more real capacity out of a tape with software. One session last week had nearly 7 gigs of src, on tape it was well under 2gigs, using less than half a DDS2 tape. In your disklist, don't compress directories full of archives, and do compress the other stuff unless the email from amanda says the compression was over 100% for that entry, which tells you the data grew. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
Re: dumpcycle-runspercycle-tapecycle
On Wednesday 11 September 2002 06:09, Mozzi wrote: >Hi all >When I set the following in amanda.conf > >dumpcycle 1 weeks >runspercycle 7 >tapecycle 7 tapes > >Does that mean I will get a full dump once a week and encrementals >everey day(7 days) > You will get a full dump of each entry in the disklist at least once a week, mixed in with incrementals in a schedule that try's to equalize the tape useage per day. But with only 7 tapes, there is a possibility of over-writing the last full of that disklist entry with only an incremental as amanda gets the scheduling adjusted. No one here would recommend only 7 tapes, the murphy style disaster is inevitable... You need at least 14, and I have 20 in my own rotation, so I'm always assured that there are at least 2 fulls available in the unlikely event a disk goes belly up on me. >What will be the formula to work on here? >dumpcycle= period between full dumps? >runspercycle= number of times backups will be done(divided into > dumpcylce) tapecycle=number of tapes used in dumpcycle. > >If I have dumpcycle=1 week and runspercycle=5 and tapecycle=5 >Will I then get 1 full dump per week and incrementals monday to > friday ? Not without manually forceing the schedule, which is, generally speaking, not always a good thing(tm). >Sorry for this all but I am writing a newbie howto and need to get > my facts straight. > > >Mozzi -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
Re: crontab, a bit offtopic
On Wednesday 11 September 2002 03:55, Brian Jonnes wrote: >On Tue 10 Sep 02 18:53, Gene Heskett wrote: >> Don't feel like the lone stranger Brian. Somebody really >> *should* write a book on howto use cron. No denigration of Paul >> Vixie intended, but the docs (what there is) suck. But I guess >> thats > >man 5 crontab isn't _too_ bad. > >> what we get when a usefull utility gets into the habit because >> nothing else does the job quite as elegantly, particularly one >> written back in jurrasic computer times and which is probably >> old > >We should replace it with... Unix Task Scheduler!!! Ha! And you > have to have a web-browser to configure it. > >..Brian Well, those users of the kde desktop suite do have the choice of using kcron to configure stuff, and which has the advantage of showing, if you are root, every cron job on the system. But it has one glaringly huge gotcha when trying to setup sequenced operations that require online access with an autodial script, and that is its 5 minute granularity based on a half a screen full of checkboxes. If you have already setup something for a 1 minute interval, and try to edit it, kcron will mung that entry rather nicely. Not. Where might a sample of this scheduler with a web interface be seen, or dl'd? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
tapetype
Hi again all When running typetype what do I spesify as my type size ? I have a 40/80 Gig dlt tape drive so will my command be typetype -e 40 -f /dev/nst0 -t Tandberg VS80 DLT or typetype -e 80 -f /dev/nst0 -t Tandberg VS80 DLT ? Tnx Mozzi
Re: Working with multiple tape drives----- Ammended
Reply With History >From what you described, the problem is to do with the robotic arm. There is a sensor on the robot arm to tell if it has moved to the right position (either the tape drive or the cartridge slot), all you need to do then is to re-calibrate the robotic arm. Then all should be well again. Gene, sorry if the msg was posted to you, something to do with this stupid Lotus Notes Memo Gene Heskett <[EMAIL PROTECTED]> on 11/09/2002 02:25:14 To: "Quinn, Richard C. - Collinsville IT" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] cc:(bcc: Tien That Ton/TDASA/TDATA) Subject: Re: Working with multiple tape drives- Ammended On Tuesday 10 September 2002 16:36, Quinn, Richard C. - Collinsville IT wrote: >Hi again, > >I think I've narrowed it down just a spell. >Gene was helpfull with some advice regarding the "tapedev" > variable in amanda.conf. >Unfortunately that didn't seem to fix the issue, which I think MAY > be scsi related and not amanda related. > >In a nutshell the problem is this: >I cannot get the robotic arm to take the tapes in and out of one > of my 2 DLT drives. >I will set up chg-scsi to only configure for one drive(the one > that is being ignored by my robotic arm). >I'll send a chg-scsi -resetcommand and get this error: >0 slot 0 move failed > > > >However, upon issuing the chg-scsi command, the tape drive will > rewind and offline itself, and yes, I can do ufsdumps to the > drive. So, if it is a SCSI problem, I am not sure what or how, > AFAIK, ufsdump and mt rew ultimately issue scsi commands don't > they? > >It doesn't seem to be the drive so much as the arm going to the > drive. > >Just before I get this ''move failed'' error, the robotic arm will > move in front of the drive, then move down an inch, then back up > an inch, then down, and THEN, I get the ''move failed'' error. > > > >Here is a snip of the errors I get in >/tmp/amanda-dbg/chg-scsi-#.debug and /var/adm/messages > respectively: > > > >== >== # START LookupElement ># STOP LookupElement (DTE) ># START LookupElement ># STOP LookupElement (STE) >ioctl on 4 failed, errno 5, ret -1 ># START DecodeSense >SCSI_ExecuteCommand:Sense Keys >ErrorCode 1d >Valid 1 >ASC 90 >ASCQ 10 >Sense key 0F >Reserved >== >== > = >=== > > >Sep 10 14:35:06 sun1 unix: WARNING: /pci@1f,4000/scsi@4,1/sst@0,0 >(sst3): >Sep 10 14:35:06 sun1 unix: Error for Command: 0xa5> Error Level: Fatal >Sep 10 14:35:06 sun1 unix: Requested Block: 0 >Error Block: 0 >Sep 10 14:35:06 sun1 unix: Vendor: STK >Serial Number: >Sep 10 14:35:06 sun1 unix: Sense Key: Illegal Request >Sep 10 14:35:06 sun1 unix: ASC: 0x3a (medium not present), > ASCQ: 0x0, FRU: 0x0 >== >== > > > >Any ideas? > > >Does anyone speak SCSI? Not very well I'm afraid. But an idea is beginning to jell in the back of my mind, and it has to do with SOME drives penchant for assigning the robot (s) to the same address as the drive itself, but to a non zero LUN at that address. Now, AFAIK, the lkernel, when initializing itself, does the device scan, it scans all LUNs at each address on the bus, and is the major reason for a noticable pause in the boot proceedings at that point. Such tomfoolery with the bus address and LUN's is normally recorded in /var/log/dmesg, so please post that section of it, probably not more than 20 lines to this list and let us see what was actually detected and recorded by the kernel at your last bootup. It might be cluefull to one of us here. Since I see references to sun1 and unix in that trace above, defining your system to us may also help, I suspect its not middle of the road linux, but may call for some sun/solaris expertise I don't have. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
RE: biliyorum ama napiim :))
Merhaba daha once sizinle bir kanalda gorusmustuk bu mail aracaligi ile tanismamiz mumkun mu acaba ? Cunku biliyorsunuz szinle sadece 2 defa konusmustuk ehehe
dumpcycle-runspercycle-tapecycle
Hi all When I set the following in amanda.conf dumpcycle 1 weeks runspercycle 7 tapecycle 7 tapes Does that mean I will get a full dump once a week and encrementals everey day(7 days) What will be the formula to work on here? dumpcycle= period between full dumps? runspercycle= number of times backups will be done(divided into dumpcylce) tapecycle=number of tapes used in dumpcycle. If I have dumpcycle=1 week and runspercycle=5 and tapecycle=5 Will I then get 1 full dump per week and incrementals monday to friday ? Sorry for this all but I am writing a newbie howto and need to get my facts straight. Mozzi
[no subject]
. MX Financial Solutions is a trading name of MX Moneyextra Financial Solutions Ltd, which is regulated by the Financial Services Authority and a member of the General Insurance Standards Council. MX Moneyextra Financial Solutions Ltd is registered in England No. 3379907. Registered Office: One Temple Back East, Temple Quay, Bristol BS1 6DX A wholly owned subsidiary of Bristol & West plc.
SATILIK DEVREMULK ACiL !
Club Flipper 'dan ACiLEN SATILIK DEVREMULK Club Flipper VIP konutlarinda , Degisime dahil , 4 kisilik , Mayisin son iki haftasi , 99 yil sureli devremulk SATILIKTIR ! Fiyati : 10.000$ Odemede her turlu kolaylik saglanir. Ayni degerde otomobil ile takas edilir. Ilgilenenler lutfen [EMAIL PROTECTED] adresine mail atsinlar. ( iki tane K var dikkat edin.. turkk.net) Not: bu bir spam maili degildir
Re: crontab
On Tue 10 Sep 02 18:53, Gene Heskett wrote: > Don't feel like the lone stranger Brian. Somebody really *should* > write a book on howto use cron. No denigration of Paul Vixie > intended, but the docs (what there is) suck. But I guess thats man 5 crontab isn't _too_ bad. > what we get when a usefull utility gets into the habit because > nothing else does the job quite as elegantly, particularly one > written back in jurrasic computer times and which is probably old We should replace it with... Unix Task Scheduler!!! Ha! And you have to have a web-browser to configure it. ..Brian -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
