Re: Manual Tape changing
Hello John, Thanks for your prompt help! Everything seems to work great. One thing remains though. I find it strange that I get this line in the backup report: ### These dumps were to tapes Monthly-03, Monthly-04. The next 2 tapes Amanda expects to used are: a new tape, a new tape. ### The next tapes in the tapelist file clearly indicate the sequence of empty tapes: ### 20010630 Monthly-04 no-reuse 20010630 Monthly-03 no-reuse 20010519 Monthly-02 no-reuse 0 Monthly-13 reuse 0 Monthly-12 reuse 0 Monthly-11 reuse 0 Monthly-10 reuse 0 Monthly-09 reuse 0 Monthly-08 reuse 0 Monthly-07 reuse 0 Monthly-06 reuse 0 Monthly-05 reuse ### Why is it not asking for Montly-05 and Monthly-06 for the next backup? Also, I accidently did an amrmtape of Monthly-01. What are the steps to recover the indexes? Thanks. John R. Jackson wrote: When we change the request() in src/changer-src/chg-manual.sh.in to include notification every 60 minutes will AMDUMP automatically detect the inserted tape and continue the backup? ... That depends on how you changed request(). :-) If you took the code in the comments and put that in the changer.conf file so it overrides the builtin request, it will check for the tape being mounted every minute (not every hour). As soon as the drive goes ready, amdump (or amcheck, etc) will continue. The one hour timer in the script is for the E-mail notification only. Also, suppose that I want I don't want to be mailed every hour but instead I want Amanda to dump to the holding disk and wait for me to make the next tape available in the morning. How would I change the request()? I think you'll have to do more than just change request() to accomplish this. Here's how I'd try it: * Change request to set tape to skip (or some non-/dev name) after an hour. * Change the code in loadslot that calls request() to look for $tape being skip after the call, and if so, return an error back to the caller (e.g. look at how eject() handles an error). Amanda will handle this and do the rest of the dumps in degraded mode (into the holding disk). My understanding of the need for the changer.conf file is for automatic tape changers...is this correct? Not necessarily. Contents of the changer.conf file (or files) is entirely up to the changer. For most, it is configuration information, such as the range of slots, and other hardware characteristics. For chg-manual, the file is sourced into the script, which means it can do things like override the request() function. Finally, do I need to put some special label sequence on the tapes for this configuration (ie Monthly-XXX-Slot-X)? ... No, although it might make your life easier. As long as you know what slot 14 is when the changer asks for it, Amanda doesn't care what the actual label is on the tape. Actually, the slot number is pretty meaningless to chg-manual. As long as you load the next tape Amanda wants, the slot number itself is not used for anything. In fact, if you do an amtape config eject after each run, the slot number will be reset to zero. If you do an amadmin config tape before the run, slot zero means the first tape, slot 1 means the second and so on. Luc Lalonde John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: [EMAIL PROTECTED] begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard
Re: Manual Tape changing
The next tapes in the tapelist file clearly indicate the sequence of empty tapes: ... Why is it not asking for Montly-05 and Monthly-06 for the next backup? What is tapecycle set to in amanda.conf? If it's bigger than 12 (the number of tapelist entries), that would explain why Amanda thinks it needs new tapes. Also, I accidently did an amrmtape of Monthly-01. What are the steps to recover the indexes? What do you mean by indexes? If you mean the catalogues that amrecover uses, you can't. This is a harder problem than it might seem because the image has to be sent back to the client to regenerate the catalogue (in the general case). For instance, my tape servers are Solaris boxes and they don't have the AIX restore program to do a catalogue. It's possible a special case could be made for GNU tar, but nobody has done the work. If you mean the other information Amanda uses to remember a tape (the curinfo database, the log.MMDD.NN files, etc), that's also probably not possible (and now you know why I create several backups of my Amanda areas :-). Yet another item for the TODO list. Actually, if you have not made any Amanda runs since you did the amrmtape, it looks like the previous tapelist file is in .../tapelist~ (note the trailing tilde character) and the exported curinfo database is in .../curinfo.orig.$$ (depending somewhat on what infofile is set to in your amanda.conf). So if you have those two files, you could put the tapelist back (I'd diff it to make sure all you're doing is adding the missing tape back in) and you can do an amadmin config import to restore the curinfo area. I'd tar the existing curinfo area first and look very, very carefully at the results. You might even do an amadmin config export and diff that with the *.orig.$$ file to see what will be changing. If you just want to know what's on the tape for your own use (i.e. so if you need to do a restore you can do it by hand), you can use amrestore: mt rewind amrestore -p $TAPE no-such-host /dev/null This will search the tape for a client named no-such-host and, of course, not find it. But along the way it will report all the images it skips. Luc Lalonde John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Manual Tape changing
Hello Folks, When we change the request() in src/changer-src/chg-manual.sh.in to include notification every 60 minutes will AMDUMP automatically detect the inserted tape and continue the backup? I assume that it will do so on the next hourly check from what I can understand in the src. Also, suppose that I want I don't want to be mailed every hour but instead I want Amanda to dump to the holding disk and wait for me to make the next tape available in the morning. How would I change the request()? My understanding of the need for the changer.conf file is for automatic tape changers...is this correct? Finally, do I need to put some special label sequence on the tapes for this configuration (ie Monthly-XXX-Slot-X)? Or can I just use Monthly-XXX? Basically I just want to know if I need to use the slot argument for the amlabel if I change the tape manually. I'm using a Daily config with great success (Thanks!). However, I can't fit the Monthly full dumps on one tape. Cheers. -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: [EMAIL PROTECTED]
Re: Manual Tape changing
When we change the request() in src/changer-src/chg-manual.sh.in to include notification every 60 minutes will AMDUMP automatically detect the inserted tape and continue the backup? ... That depends on how you changed request(). :-) If you took the code in the comments and put that in the changer.conf file so it overrides the builtin request, it will check for the tape being mounted every minute (not every hour). As soon as the drive goes ready, amdump (or amcheck, etc) will continue. The one hour timer in the script is for the E-mail notification only. Also, suppose that I want I don't want to be mailed every hour but instead I want Amanda to dump to the holding disk and wait for me to make the next tape available in the morning. How would I change the request()? I think you'll have to do more than just change request() to accomplish this. Here's how I'd try it: * Change request to set tape to skip (or some non-/dev name) after an hour. * Change the code in loadslot that calls request() to look for $tape being skip after the call, and if so, return an error back to the caller (e.g. look at how eject() handles an error). Amanda will handle this and do the rest of the dumps in degraded mode (into the holding disk). My understanding of the need for the changer.conf file is for automatic tape changers...is this correct? Not necessarily. Contents of the changer.conf file (or files) is entirely up to the changer. For most, it is configuration information, such as the range of slots, and other hardware characteristics. For chg-manual, the file is sourced into the script, which means it can do things like override the request() function. Finally, do I need to put some special label sequence on the tapes for this configuration (ie Monthly-XXX-Slot-X)? ... No, although it might make your life easier. As long as you know what slot 14 is when the changer asks for it, Amanda doesn't care what the actual label is on the tape. Actually, the slot number is pretty meaningless to chg-manual. As long as you load the next tape Amanda wants, the slot number itself is not used for anything. In fact, if you do an amtape config eject after each run, the slot number will be reset to zero. If you do an amadmin config tape before the run, slot zero means the first tape, slot 1 means the second and so on. Luc Lalonde John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
