Re: amanda having trouble choosing next tape
On Mon, Mar 03, 2003 at 09:20:22AM -0800, John Oliver wrote: The dumps were flushed to tape Indyme014. The next tape Amanda expects to use is: a new tape. [EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist 20030303 Indyme014 reuse 20030228 Indyme013 reuse 20030227 Indyme012 reuse 20030227 Indyme011 reuse 20030226 Indyme010 reuse 20030225 Indyme009 reuse 20030221 Indyme008 reuse 20030220 Indyme007 reuse 20030219 Indyme006 reuse 20030218 Indyme005 reuse 20030215 Indyme004 reuse 20030214 Indyme003 reuse 20030213 Indyme002 reuse 20030212 Indyme001 reuse [EMAIL PROTECTED] root]# Why isn't it telling me it wants 001? I would reckon it's because you have tapecycle set to a number greater than 14 in your amanda.conf - If this is the case, amanda's going to ask for a new tape until it reaches this number. Looking back at one of your previous posts, you said: dumpcycle 1 week runspercycle 5 tapecycle 15 tapes If you set tapecycle to 14, amanda should ask for tape 001. Hope that helps, Simon.
Re: Make amanda unload tape drive?
On Sat, Jan 25, 2003 at 12:34:47PM -0500, John R. Jackson wrote: The standard trick is to call either amtape CONFIG eject or (what I do) amtape CONFIG slot advance after the amdump run. For instance: amdump CONFIG ; amtape CONFIG slot advance So I did this last night, and today all tapes are still in their drives. I would have expected to see one of them with a nice green 'operate handle' light :-( Without the amtape call, the next amdump run will do a load current (which doesn't do anything because the tape is still loaded), check the current tape (the one that was written yesterday), decide it does not like it and then do a load next, which ejects current and goes on to the next tape. That works but, as you noted, the last tape from a run sits in the drive between runs. Hmm. I've just read this again. You say a load next ejects the current tape - which would imply that I should be seeing an ejected tape eventually. This in fact never happens. amtape config eject works fine, however. Should I have 'needeject' set in my chg-multi.conf? It's the only way I can see of having amanda eject a tape when moving on to the next. But the comment in chg-multi.conf says, If you are using multiple drives as a tape changer, you don't want to do this... I'm thinking that I *do* want to do this. Would I be right? Simon
Re: Make amanda unload tape drive?
On Sat, Jan 25, 2003 at 12:34:47PM -0500, John R. Jackson wrote: Can amanda send a signal to my DLT IV to unload the tape after backups are finished, so whoever goes back to swap tapes can just do it without waiting to manually unload? The standard trick is to call either amtape CONFIG eject or (what I do) amtape CONFIG slot advance after the amdump run. For instance: amdump CONFIG ; amtape CONFIG slot advance Thanks very much! I'll try it out tonight :-) Simon
GNUTAR
Hi, I'm using tar for backup, but my DLEs refer to device names. For example, henry /dev/sda1 root-tar henry /dev/sda2 user-tar I'm also trying to use exclude lists, but these don't seem to be working as I would expect them to (it looks like they're being ignored). The question is, should I be refering to paths rather than devices when using tar? Like this: henry / root-tar henry /usruser-tar ...and have an exclude file for, say, the root filesystem which ignores all the mount points covered by the other DLEs? Thanks! Simon
Re: GNUTAR
On Fri, Jan 24, 2003 at 01:20:04PM +0100, Paul Bijnens wrote: Simon Young wrote: The question is, should I be refering to paths rather than devices when using tar? Like this: henry / root-tar henry /usruser-tar Yes. You may even use path for if you use dump instead of tar. Amanda will make then necessary conversion for you. ...and have an exclude file for, say, the root filesystem which ignores all the mount points covered by the other DLEs? No, you don't need that. GNUTAR is run with the option '--one-file-system' that avoids crossing mount points. Excellent! Thanks very much :-) Simon
Re: amandahostsauth failed
On Thu, Jan 23, 2003 at 09:17:43AM -0700, Santiago wrote: Thanks so much to everyone responding to my first question. I got that fixed right away. However, I am still running into the following issue. Possibly my configuration is poor . .. the error is: Amanda Backup Client Hosts Check ERROR: scratchy: [access as amanda not allowed from amanda@backup] amandahostsauth failed Client check: 3 hosts checked in 0.020 seconds, 1 problem found (brought to you by Amanda 2.4.3) Make sure that the entry in scratchy's /etc/hosts file has the fully quallified domain name of the backup machine. For example: xxx.xxx.xxx.xx scratchy.yourdomain.org scratchy That ought to fix it :-) Simon.
Re: Make amanda unload tape drive?
On Thu, Jan 16, 2003 at 01:13:14AM -0500, Jon LaBadie wrote: On Fri, Jan 10, 2003 at 11:14:55AM +, Pavel Rabel wrote: Can amanda send a signal to my DLT IV to unload the tape after backups are finished, so whoever goes back to swap tapes can just do it without waiting to manually unload? For amdump this is easy. Is it really easy when using a tape changer? If you follow amdump with an amtape eject command, will you not be ejecting the tape in the 'current' slot? Once amdump has finished, isn't the current slot incremented? Implying that you'll be ejecting the tape in the next slot, which is most likely the one amanda will be wanting to use next. I'm not quite clear about this yet, so please correct me if I'm wrong. And what if amanda uses more than one tape in a single run? Is there a nice way to have it eject only the tapes it used? Thanks, Simon.
Re: Make amanda unload tape drive?
On Wed, Jan 22, 2003 at 09:28:12AM -0500, Jon LaBadie wrote: The original OP did not specify a changer and I, perhaps incorrectly formed my answer based on a single drive with no changer. That's what I thought, but I was hoping it would be just as easy :-) My experience with changers is pretty limited and the changer script I use (chg-mtx) does not maintain the state of the current slot in a disk file. I just use a straightforward chg-multi with three external drives. The state of the changer is stored in a state file. But based on that limited experience I find that amdump leaves the last tape used in the drive. It leaves it at the end of media, after the last file is written; i.e. not rewound. The changer script is not called again at this point. From this I don't see where the current slot state would be incremented past the last tape used. Your experience may differ, if so I'd like to know for future reference. Well, I'm quite new to amanda, but I've been running amdump for the last few nights. Last night's backup was to the tape in slot 2. If I run 'amtape config current' now, I get the tape in slot 3. Therefore I'm assuming the state file must have been updated after amdump ran. Again my lack of experience causes this question. Do other changers or libraries work differently? Can some eject multiple individual tapes? Curious minds would like to know. With chg-multi, all tapes in the 'changer' can be controlled individually, since they're really just individual drives. I was toying with the idea of finding out which is the current slot *before* runing the backup, then ejecting the tape in this slot once amdump is finished - but this doesn't work if amanda used more than one tape. Any ideas would be appreciated. Thanks, Simon.
Re: Amanda correct hostname resolution
Hi Santiago, On Wed, Jan 22, 2003 at 08:03:43AM -0700, Santiago wrote: Hello. I am new to amanda, so please forgive any newbie questions. I have done my best to RTFM for all of the docs I can find googling amanda. My question relates to the hostname lookup performed by amanda - I have put the correct machine name/IP in /etc/hosts. There is no DNS resolution for this machine (or many other machines that I will be backing up). How do I correct this error and get amanda to resolve hostnames correctly (from my /etc/hosts file)? TIA, Santiago Yes, the machine resolves to /etc/hosts first. I had this problem too. You have to make sure that the client can look up the server as well. So I guess scratchy needs an entry in /etc/hosts for the backup server :-) Hope that helps, Simon
Re: Make amanda unload tape drive?
On Wed, Jan 22, 2003 at 10:48:09AM -0500, Jon LaBadie wrote: On Wed, Jan 22, 2003 at 03:12:07PM +, Simon Young wrote: On Wed, Jan 22, 2003 at 09:28:12AM -0500, Jon LaBadie wrote: Your experience may differ, if so I'd like to know for future reference. Well, I'm quite new to amanda, but I've been running amdump for the last few nights. Last night's backup was to the tape in slot 2. If I run 'amtape config current' now, I get the tape in slot 3. Therefore I'm assuming the state file must have been updated after amdump ran. Any chance that is a base 0 vs. base 1 difference. Some changer scripts number things 0,1,2 even when the changer/library might number them 1,2,3. Good point, but I've accounted for that. The changer only has slots 1, 2 and 3. At the minute, each slot has it's own tape. This will change in the very near future, but it would be nice to have amanda eject the tapes it doesn't need for a while. Simon
Re: Make amanda unload tape drive?
On Wed, Jan 22, 2003 at 01:04:33PM -0500, Gene Heskett wrote: If you follow amdump with an amtape eject command, will you not be ejecting the tape in the 'current' slot? Thats how it would work here at any rate. Amanda does not change her notion of slot until the next invocation of amdump or amcheck, both of which apparently start out by searching for the next reusable tape. Ah! That explains it then :-) I'd assume in those robots where it has an internal storage of 12 or more tapes, that an eject would mean it will bring that tape to the door for you to remove, in which case you would need to tell it which tape slot to give you the contents of. This would not be the same as ejecting a tape from a drive, which in larger libraries, there may be 2 or more of. I keep refering to 'magazine' because thats the 'style' mine is built as, which of course will not apply to all cases. It's ok. I'm only using a pseudo-changer (i.e. three external scsi DLT drives all connected to the same box), so I would have thought it would be a common request, in this situation, to have amanda eject the tapes it has just used. I'd just like to make the job of changing the tapes as easy as possible for the guy who ends up doing it, ya see. Not trying to confuse, my apologies if it does. Not confusing. Interesting :-) Cheers, Simon
DLT8000 Strangeness
Hi,
I'm setting up amanda on a Compaq Proliant DL380 with three Compaq
DLT8000 tape drives.
Having run tapetype a few times (using DLT IV tapes), I'm getting the
following:
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 38301 mbytes
filemark 23 kbytes
speed 2088 kps
}
I'm concerned about the 'speed' entry. Whenever I tar a large file
directly to the tape, I get transfer rates of about 4MB/s - but tapetype
seems to think things are going at half this speed.
I looked up the tapetype definition for a Quantum DLT8000 on the
Faq-O-Matic (which I believe to be the same hardware, but with Compaq
firmware?). It gave a speed rating of 5482 kps. This is more what I
would expect, since these drives are supposed to have a transfer rate of
around 6MB/s.
BTW, I'm using the debian package of amanda, version 2.4.2p2-4.
Is it reasonable to change the speed setting to be more in line with
observed transfer rates? Does amanda try to stream data at this rate, or
is it more of a guideline for the planner to base its calculations on?
Any suggestions would be greatly appreciated :-)
Many thanks,
Simon.
Re: Problems with labelstr
On Thu, Jan 16, 2003 at 09:50:35AM -0600, Dan Spray wrote: Hello all, I am new to Amanda and have been following http://www.backupcentral.com/amanda.html to the T to get Amanda setup and working. In chapter 12 it says to run # su amanda - c amlabel Daily Daily-123 slot 123 when I do I get: [root@ZEUS /named]# su amanda -c amlabel config Daily-123 slot 123 amlabel: label Daily-123 doesn't match labelstr ^DailySet1[0-9][0-9] *$ My labelstr in my config file is: labelstr ^DailySet1[0-9][0-9]*$ Not sure what I am doing wrong or how to fix it. Any help would be greatly appreciated. I'm also new to Amanda, but not so new to regular expressions. The labelstr directive says that your tape label must be of a certain form. In this case, it's expecting the string 'DailySet1' followed by a number, followed by zero or more numbers. Therefore 'Daily-123' doesn't match the label string. You could change labelstr to be something like ^Daily-[0-9][0-9]*$ Or change your tape label to something like 'DailySet1123'. I'd go for the first option :-) Hope that helps! Simon.
