Re: A list of implementation questions
On Thu, 18 Jan 2001, Hurf Sheldon wrote: > Our amanda was set up by set up by someone who has moved on. Well now that would be me... > 1: When we move the Overland to the FreeBSD PC and run amlabel, we get > errors in the system log file and the DLT goes out to lunch - we setup > an HP SureStore 2300 6 tape DDS as a test and saw some similar errors > but > after the tapes were labeled they subsided: > (ch0:ahc0:0:0:1): MOVE MEDIUM. CDB: a5 20 0 0 0 3 0 1 0 0 0 0 > (ch0:ahc0:0:0:1): ILLEGAL REQUEST asc:3b,d > (ch0:ahc0:0:0:1): Medium destination element full > ch: warning: could not map element source address 0d to a valid element > type > (sa0:ahc0:0:0:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM > command to clear this state. > > Neither the FreeBSD list nor Overland has had any insight into this... Which FreeBSD list did you ask? Each has a different focus. Anyhow this one looks pretty obvious. "Move medium" means the changer received a command to move a tape, "Illegal request...Medium destination element full" means the destination of the move command, either a tape drive or a changer slot, already has a tape in it. What would cause this? Offhand I can think of a couple possibilities, though there may well be others I'm missing. 1) Changer scripts maintain knowledge (in a file) of a "current slot", which is which slot the currently loaded tape came from. If you're moving the changer back and forth between the HP-UX and FreeBSD machines you might be confusing the changer scripts if you're not putting the changer back in the same state it was in when it last came off that machine. Also if you move tapes around in the changer without using amtape commands this could cause the same sort of confusion. 2) Whatever changer script you're using may just not be sending the right commands. To debug this I think I would start at the lowest level of software you can, chio if that's what you're using, and make sure you can send commands to the changer and see it do the right thing in response. Once that works, move up a level to your changer script and do the same thing. Once that works move up to amtape. if the changer script is happy, amtape probably will be, too. > 2: We can't directly access the NAS disks - how would we give dump > instructions > to a system that has it mounted via NFS or SMB? I thought Amanda used > tar > on Unix but a dump request to an Irix system with the NAS mounted failed > "disk /remote/nas01/2 offline on nimble". A remote SMB mount can't be in > turn shared so when trying to backup via smbclient we get: > "PC SHARE //lassiter/N access error: host down or invalid password?" Amanda will use either dump or tar, whichever is specified in the dumptype you specify in the disklist for each filesystem. All the unix systems were using dump when I left. For the NAS you'll have to use tar. > 3: How can we configure amanda to do only level 0 or only incremental > backups? > We'd like to (say) run level 0 over the weekend to one tape set and > incrementals to > another, with an eye to adding a second tape machine and do level 0 to > one and > incrementals to the other. David has already given you some ideas on this. I would just add that in deciding if you really want to do this, you should think carefully about what would be involved in performing a multi-level restore, and then ask yourself if you're really willing to live with that. If your daily run is taking too long I'd think about a few alternatives... a) upgrade the DLT 4000 to a DLT 8000, b) add more tapes to the tape rotation and increase dumpcycle so that level 0s are spread over a greater number of days. For the archive runs you're looking for I'd do that as a separate config with no-record, but I wouldn't eliminate the level 0s in the regular daily config. But that's just my preference. It's your call now of course. > 3a: To use a second 15 tape magazine, is there a way to setup > amanda.conf to count > all 30 tapes sequentially? The problem seems to be that Amanda thinks > there is > 30 slots if there are 30 tapes, so the chio routines fail. We'd like to > have it stop > the tapers, ask for the next magazine and start at slot 1 again. I don't have experience with this type of setup yet, and it's been too long since I've looked at the code so I'm not sure what happens. What happens if the tape it wants isn't in the changer? Does it keep rotating through the changer until you stop it? Does it make one rotation and give up? As far as I can remember Amanda doesn't have a notion of magazines, so it doesn't know internally what the inventory of the changer is. This is knowledge that would have to be built into the changer script, which you could write or have a student tech to write. I wrote the one on the HP server and it didn't take very long. You could probably use that as a starting point. It should be pretty straightforward to rip out the "mc" commands and replace with chi
Re: A list of implementation questions
>Date: Thu, 18 Jan 2001 15:22:02 -0500 >From: Hurf Sheldon <[EMAIL PROTECTED]> >Our present setup is Amanda-2.4.2-19990920 on an HPUX 10.2 system >backing up >a heterogeneous environment of NT, Irix, FreeBSD and HPUX systems to >an Overland 4000LX 15tape/1drive DLT. We are backing up the NT systems >via Samba. >Changes needed: >1: Move the drive to a PC based system - right now we have a FreeBSD >4.2-Stable >system on a dual 266mhz P-II ASUS P2B-D mother board and an Adaptec >2930CU SCSI adapter. OK; I'm using FreeBSD 4.2-STABLE as of 13 Dec 2000. The box doesn't have much in the way of CPU, but has 3 SCSI host adapters (one for the OS, one for holding disks, and one for the tape & changer). I'm running amanda 2.4.2 (as released... well, mostly) on it. >... >Related questions: >1: When we move the Overland to the FreeBSD PC and run amlabel, we get >errors in the system log file and the DLT goes out to lunch - we setup >an HP SureStore 2300 6 tape DDS as a test and saw some similar errors >but >after the tapes were labeled they subsided: >(ch0:ahc0:0:0:1): MOVE MEDIUM. CDB: a5 20 0 0 0 3 0 1 0 0 0 0 >(ch0:ahc0:0:0:1): ILLEGAL REQUEST asc:3b,d >(ch0:ahc0:0:0:1): Medium destination element full >ch: warning: could not map element source address 0d to a valid element >type >(sa0:ahc0:0:0:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM >command to clear this state. Hmm... what changer script are you using? What happens if you issue "chio" commands directly (as a user who has "write" access to /dev/ch0)? (The commands I would use for startes would be "chio info" and "chio params".) >2: We can't directly access the NAS disks - how would we give dump >instructions >to a system that has it mounted via NFS or SMB? I thought Amanda used >tar >on Unix but a dump request to an Irix system with the NAS mounted failed >"disk /remote/nas01/2 offline on nimble". Ummm... you need to use tar, not dump. tar can read an NFS-mounted filesystem; dump cannot. >3: How can we configure amanda to do only level 0 or only incremental >backups? >We'd like to (say) run level 0 over the weekend to one tape set and >incrementals to >another, with an eye to adding a second tape machine and do level 0 to >one and >incrementals to the other. Set up a separate configuration for that. I do something like this, in that I run the "usual" backups Monday - Saturday, and then on Sunday, I run a different configuration that does record-no level 0 backups of everything; the media from this are sent off-site for 2 weeks. Much of the information is set up to be shared between the configurations (by a combination of "include" directives & symlinks). I can send more details if that's not enough (but I thought I had a fair amount of detail in a message a week ago or so). >3a: To use a second 15 tape magazine, is there a way to setup >amanda.conf to count >all 30 tapes sequentially? The problem seems to be that Amanda thinks >there is >30 slots if there are 30 tapes, so the chio routines fail. We'd like to >have it stop >the tapers, ask for the next magazine and start at slot 1 again. Sounds as if you'd need to use a custom changer script to do that, though my knowledge of the details of the stock ones is pretty limited. Starting with an existing script that comes close can be helpful. Cheers, david -- David Wolfskill [EMAIL PROTECTED] UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 I need help: http://www.whistle.com/employment/employ-engg.html#K030391
A list of implementation questions
Hi Folks, Our amanda was set up by set up by someone who has moved on. I feel like I have a pretty good handle on it after 6mos. It has worked reliably. I've learned to add/delete disks, manipulate some of the config options and have succcessfully "twinned" our master configuration so I can test migration of our tape device from one platform to another as well as change the config for a different tape device. As time has passed our needs have progressed and I'm unsure of the best way to proceed. I also have some questions re: day to day operations. Our present setup is Amanda-2.4.2-19990920 on an HPUX 10.2 system backing up a heterogeneous environment of NT, Irix, FreeBSD and HPUX systems to an Overland 4000LX 15tape/1drive DLT. We are backing up the NT systems via Samba. Changes needed: 1: Move the drive to a PC based system - right now we have a FreeBSD 4.2-Stable system on a dual 266mhz P-II ASUS P2B-D mother board and an Adaptec 2930CU SCSI adapter. 2: Add backup for a Dell PowerVault 705 NAS device and Windows 2000 systems 3: Do archival backups 3a: use a second magazine 4: resolve authentication error Related questions: 1: When we move the Overland to the FreeBSD PC and run amlabel, we get errors in the system log file and the DLT goes out to lunch - we setup an HP SureStore 2300 6 tape DDS as a test and saw some similar errors but after the tapes were labeled they subsided: (ch0:ahc0:0:0:1): MOVE MEDIUM. CDB: a5 20 0 0 0 3 0 1 0 0 0 0 (ch0:ahc0:0:0:1): ILLEGAL REQUEST asc:3b,d (ch0:ahc0:0:0:1): Medium destination element full ch: warning: could not map element source address 0d to a valid element type (sa0:ahc0:0:0:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. Neither the FreeBSD list nor Overland has had any insight into this... 2: We can't directly access the NAS disks - how would we give dump instructions to a system that has it mounted via NFS or SMB? I thought Amanda used tar on Unix but a dump request to an Irix system with the NAS mounted failed "disk /remote/nas01/2 offline on nimble". A remote SMB mount can't be in turn shared so when trying to backup via smbclient we get: "PC SHARE //lassiter/N access error: host down or invalid password?" 3: How can we configure amanda to do only level 0 or only incremental backups? We'd like to (say) run level 0 over the weekend to one tape set and incrementals to another, with an eye to adding a second tape machine and do level 0 to one and incrementals to the other. 3a: To use a second 15 tape magazine, is there a way to setup amanda.conf to count all 30 tapes sequentially? The problem seems to be that Amanda thinks there is 30 slots if there are 30 tapes, so the chio routines fail. We'd like to have it stop the tapers, ask for the next magazine and start at slot 1 again. 4: We compiled the latest Amanda for FreeBSD (VERSION="Amanda-2.4.2") which included patches for Windows 2000 via smbclient - that works fine now. We are getting "auth" errors on the cd /usr/local/amanda/FreeBSD system that we built as the tape server: " ERROR: vermeer: [access as backup not allowed from [EMAIL PROTECTED]]\ amandahostsauth failed " - Did we miss something - I'm not able to track this down. 5: What other Amanda guidance/support resources are available? 6: Just out of curiosity, is anyone working on a gui configuration interface for Amanda? my apologies for the "laundry list" thanks in advance for any help hurf Hurf Sheldon, Dir. Research Systems email: [EMAIL PROTECTED] Program of Computer Graphics voice:607 255 6713 fax:607 255 0806 580 Rhodes Hall, Cornell University http://www.graphics.cornell.edu/~hurf/ Ithaca, N.Y. 14853
