Re: Upgrade to 2.4.3 has hiccup -- I take it back
On Mon, Jan 06, 2003 at 04:15:52PM -0600, Douglas K. Rand wrote: I really should just learn to test things before I go off spouting stuff. Why is it always the case that when what I write differs from what I mean, it always turns out that what I write is wrong. Sigh. We both suffer in shame :)) BUT!!! AMANDA 2.4.2p2 ignores the missing exclude file if it doesn't exist. Here is a sendbackup file. Notice that sendbackup notices that the exclude file (//.amanda.excludes) doesn't exist, and so it ignores it. I still like this behavior, but now it is Amanda's sendbackup (and sendsize) that checkes for the existance of the exclude file, and in its absence it doesn't pass it to the backup command. I don't mind that, but I think a warning should be printed at some point rather than have to notice in a debug file that I misspeeled .amanda.exclude. Is there some notice given? In fact, if that sendbackup behavior still exists in 2.4.3 (I suspect it does), then I think the new amcheck notice should be a warning, not an error. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Upgrade to 2.4.3 has hiccup -- I take it back
I still like this behavior, but now it is Amanda's sendbackup (and sendsize) that checkes for the existance of the exclude file, and in its absence it doesn't pass it to the backup command. Jon I don't mind that, but I think a warning should be printed at Jon some point rather than have to notice in a debug file that I Jon misspeeled .amanda.exclude. Is there some notice given? Jon In fact, if that sendbackup behavior still exists in 2.4.3 (I Jon suspect it does), then I think the new amcheck notice should be a Jon warning, not an error. Personally, I don't have a problem with the warning only being in the sendsize or sendbackup diagnostic files. I use the amcheck -m alot and have the output sent to my pager, so I wouldn't want it to always warn me of those, and even if I missed changing a tape, I might not want all those warnings. But thats just my $0.02.
Re: Upgrade to 2.4.3 has hiccup
On Sat, Jan 04, 2003 at 04:35:48PM -0600, Douglas K. Rand wrote: Jon Perhaps it is an added extra check that that should have been in Jon 2.4.2. Extra checking is not a bad thing. Jon The file is not necessary. I really liked how it behaved in 2.4.2. You told Amanda to tell gnu-tar to use an exclude file. Amanda didn't care if the exclude file was there or not, and actually gnu-tar didn't care very much either. Gnu-tar emits a warning that the exclude file doesn't exist, and so it won't use it. This was really nice. If you had file systems that you always wanted everything backed up, it just worked. If you had file systems that you wanted to exclude some things from, just create the exclude file at the root of the file system, and presto, it works. Now I have to create those empty exclude files everywhere. I know, I could use different dump types for those filesystems I want to have excludes on, but it was really nice not having to muck with the Amanda configurations to exclude some stuff from a filesystem. All I have to do is make a file on the client. You can use the keyword 'optional' on your exclude specification and amanda will not complain if the file doesn't exist. You don't have to create empty files. I changed the default because the default must be to emit error about everything, if you want some test to not be preformed, it's up to you to change your config and tell amanda to not do some test. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Upgrade to 2.4.3 has hiccup
[Doug whining because he has to create those empty exlude files ...]
Jean-Louis You can use the keyword 'optional' on your exclude
Jean-Louis specification and amanda will not complain if the file
Jean-Louis doesn't exist. You don't have to create empty files.
Cool! I don't see the particular syntax in the man page. (I was afraid
I'd just not read the page closely enough after the upgrade. :))
Does this syntax work?
define dumptype tar {
defaults
program GNUTAR
optional exclude list.amanda.excludes
}
Re: Upgrade to 2.4.3 has hiccup
On Sat, Jan 04, 2003 at 04:35:48PM -0600, Douglas K. Rand wrote: And did you put a file exclude.gtar in there? Yes, I did, and that got rid of the message. But if amanda needs this file, why doesn't it just create it? Because it is a file you create specifying what you want to exclude. If you don't want to use it, don't list it in amanda.conf. It wasn't necessary with 2.4.2 If it's necessary for 2.4.3, then why isn't it installed with or created by that version? Jon Perhaps it is an added extra check that that should have been in Jon 2.4.2. Extra checking is not a bad thing. Jon The file is not necessary. I really liked how it behaved in 2.4.2. You told Amanda to tell gnu-tar to use an exclude file. Amanda didn't care if the exclude file was there or not, and actually gnu-tar didn't care very much either. Gnu-tar emits a warning that the exclude file doesn't exist, and so it won't use it. I'm surprised at your observations. gnutar on my system terminates with an error if the exclude file is missing. OPPS, ran some tests last evening and assumed -- never assume -- that the error message, error exit status, and very fast completion meant it did not do the tar dump. Just checked again. Turns out it does. Sorry for the mis-information. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Upgrade to 2.4.3 has hiccup
On Sat, Jan 04, 2003 at 05:38:43PM -0600, Douglas K. Rand wrote:
[Doug whining because he has to create those empty exlude files ...]
Jean-Louis You can use the keyword 'optional' on your exclude
Jean-Louis specification and amanda will not complain if the file
Jean-Louis doesn't exist. You don't have to create empty files.
Cool! I don't see the particular syntax in the man page. (I was afraid
I'd just not read the page closely enough after the upgrade. :))
Does this syntax work?
define dumptype tar {
defaults
program GNUTAR
optional exclude list.amanda.excludes
}
The man page is clear:
exclude [ list|file ][[optional][ append ][ string ]+]
So you need: exclude list optional .amanda.excludes
Are you looking at the man page for 2.4.3?
Jean-Louis
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Upgrade to 2.4.3 has hiccup
[Doug whining because he has to create those empty exlude files ...] Jean-Louis You can use the keyword 'optional' on your exclude Jean-Louis specification and amanda will not complain if the file Jean-Louis doesn't exist. You don't have to create empty files. Cool! I don't see the particular syntax in the man page. (I was afraid I'd just not read the page closely enough after the upgrade. :)) Jean-Louis The man page is clear: exclude [ list|file ][[optional][ append ][ string ]+] Jean-Louis So you need: exclude list optional .amanda.excludes Are Jean-Louis you looking at the man page for 2.4.3? Sigh. I used a system with 2.4.2 on it. I found a 2.4.3 system and you are right, there it is in the manual, clear as day. Where did I put that baseball bat with RTFM carved into the end?
Re: Upgrade to 2.4.3 has hiccup
On Saturday 04 January 2003 18:42, Jon LaBadie wrote: On Sat, Jan 04, 2003 at 04:35:48PM -0600, Douglas K. Rand wrote: And did you put a file exclude.gtar in there? Yes, I did, and that got rid of the message. But if amanda needs this file, why doesn't it just create it? Because it is a file you create specifying what you want to exclude. If you don't want to use it, don't list it in amanda.conf. It wasn't necessary with 2.4.2 If it's necessary for 2.4.3, then why isn't it installed with or created by that version? Jon Perhaps it is an added extra check that that should have been in Jon 2.4.2. Extra checking is not a bad thing. Jon The file is not necessary. I really liked how it behaved in 2.4.2. You told Amanda to tell gnu-tar to use an exclude file. Amanda didn't care if the exclude file was there or not, and actually gnu-tar didn't care very much either. Gnu-tar emits a warning that the exclude file doesn't exist, and so it won't use it. I'm surprised at your observations. gnutar on my system terminates with an error if the exclude file is missing. OPPS, ran some tests last evening and assumed -- never assume -- that the error message, error exit status, and very fast completion meant it did not do the tar dump. Just checked again. Turns out it does. Sorry for the mis-information. Jon, I wonder if that was one of the things adjusted in how tar works between 1.13-19 and 1.13.-25 because I can recall in the earlier days haveing it exit without generating the tarfile, and that was the reason at the time. Whenever it gained the ability to have a .exclude file in a local directory to be skipped seems to be about the right time frame to me. OTOH, I don't have either hand anywhere near a bible, so take it for what its worth, possibly nothing. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.21% setiathome rank, not too shabby for a WV hillbilly
Re: Upgrade to 2.4.3 has hiccup -- I take it back
On Sun, Jan 05, 2003 at 01:05:51AM -0500, Gene Heskett wrote: On Saturday 04 January 2003 18:42, Jon LaBadie wrote: On Sat, Jan 04, 2003 at 04:35:48PM -0600, Douglas K. Rand wrote: ... . Amanda didn't care if the exclude file was there or not, and actually gnu-tar didn't care very much either. Gnu-tar emits a warning that the exclude file doesn't exist, and so it won't use it. I'm surprised at your observations. gnutar on my system terminates with an error if the exclude file is missing. OPPS, ran some tests last evening and assumed -- never assume -- that the error message, error exit status, and very fast completion meant it did not do the tar dump. Just checked again. Turns out it does. Sorry for the mis-information. Jon, I wonder if that was one of the things adjusted in how tar works between 1.13-19 and 1.13.-25 because I can recall in the earlier days haveing it exit without generating the tarfile, and that was the reason at the time. self-directed sarcasm Who was it that wrote in the messages above, never assume? /self-directed sarcasm Gene's comment caused me to reconsider. My checked again from above included an assumption that I'm too embarassed to even describe. Let me try to correct myself once again. gnutar on my system terminates with an error if the exclude file is missing Don't ask why :), but I have 9 releases of gnutar on my system: $ ls -l *gtar* -rwxr-xr-x 2 jon staff 166676 Feb 14 2002 amgtar -r-xr-xr-x 2 root other 127544 Feb 14 2002 gtar-1.13 -rwxr-xr-x 1 root other 138404 Feb 14 2002 gtar-1.13.17 -rwxr-xr-x 1 jon staff 143944 Feb 14 2002 gtar-1.13.19 -rwxr-xr-x 1 jon staff 146264 Feb 14 2002 gtar-1.13.20 -rwxr-xr-x 1 jon staff 163952 Feb 14 2002 gtar-1.13.21 -rwxr-xr-x 1 jon staff 164048 Feb 14 2002 gtar-1.13.22 -rwxr-xr-x 1 jon staff 164744 Feb 14 2002 gtar-1.13.23 -rwxr-xr-x 1 jon staff 166612 Feb 14 2002 gtar-1.13.24 -rwxr-xr-x 2 jon staff 166676 Feb 14 2002 gtar-1.13.25 -r-xr-xr-x 2 root other 127544 Feb 14 2002 gtar-sfw Each of them, when run as follows, generate the same result. $ amgtar -X nosuchfile -cvf /tmp/tarball . amgtar: nosuchfile: No such file or directory amgtar: Error is not recoverable: exiting now and the output file /tmp/tarball is not created. So I am surprised by Doug's observation to the contrary. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Upgrade to 2.4.3 has hiccup
[root@backup root]# su amanda -c amcheck DailySet1 bash: /root/.bashrc: Permission denied Amanda Tape Server Host Check - Holding disk /var/tmp: 2330384 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape Indyme001 label ok Server check took 7.226 seconds Amanda Backup Client Hosts Check ERROR: backup: [Can't open exclude file '/usr/local/lib/amanda/exclude.gtar': No such file or directory] Client check: 10 hosts checked in 0.223 seconds, 1 problem found (brought to you by Amanda 2.4.3) Up until now, amanda has used /var/lib/amanda So I created /usr/local/lib/amanda/ and chowned it to amanda, but I still get the same message. -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Upgrade to 2.4.3 has hiccup
On Fri, Jan 03, 2003 at 11:12:18AM -0800, John Oliver wrote: [root@backup root]# su amanda -c amcheck DailySet1 bash: /root/.bashrc: Permission denied Amanda Tape Server Host Check - Holding disk /var/tmp: 2330384 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape Indyme001 label ok Server check took 7.226 seconds Amanda Backup Client Hosts Check ERROR: backup: [Can't open exclude file '/usr/local/lib/amanda/exclude.gtar': No such file or directory] Client check: 10 hosts checked in 0.223 seconds, 1 problem found (brought to you by Amanda 2.4.3) Up until now, amanda has used /var/lib/amanda So I created /usr/local/lib/amanda/ and chowned it to amanda, but I still get the same message. Did you put a file named exclude.gtar in /usr/local/lib/amanda ? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Upgrade to 2.4.3 has hiccup
On Fri, Jan 03, 2003 at 02:27:30PM -0600, Deb Baddorf wrote: Up until now, amanda has used /var/lib/amanda So I created /usr/local/lib/amanda/ and chowned it to amanda, but I still get the same message. On the client, right? In this case, sure... I did this locally. And did you put a file exclude.gtar in there? Yes, I did, and that got rid of the message. But if amanda needs this file, why doesn't it just create it? -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Upgrade to 2.4.3 has hiccup
On Friday 03 January 2003 14:12, John Oliver wrote: [root@backup root]# su amanda -c amcheck DailySet1 bash: /root/.bashrc: Permission denied Amanda Tape Server Host Check - Holding disk /var/tmp: 2330384 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape Indyme001 label ok Server check took 7.226 seconds Amanda Backup Client Hosts Check ERROR: backup: [Can't open exclude file '/usr/local/lib/amanda/exclude.gtar': No such file or directory] Client check: 10 hosts checked in 0.223 seconds, 1 problem found (brought to you by Amanda 2.4.3) Up until now, amanda has used /var/lib/amanda So I created /usr/local/lib/amanda/ and chowned it to amanda, but I still get the same message. This has the hints of leftover rpm installs of amanda. If you did the default prefix, then everything for the configs is in /usr/local/etc/amanda/configname and audit trails, indices and such will be in /usr/local/var/amanda/configname. However, the path to the exclude file is obtained from the working copy of configname/amanda.conf, so you may want to move the configs from /etc/amanda to /usr/local/etc/amanda if those are the ones you really want to use, and personally I'd set that amanda.conf so it looked in /usr/local/etc/amanda for that exclude file. I'd druther have all the variables in one location myself, but as long as it exists where it looks, it should be ok. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.21% setiathome rank, not too shabby for a WV hillbilly
Re: Upgrade to 2.4.3 has hiccup
And did you put a file exclude.gtar in there? Yes, I did, and that got rid of the message. But if amanda needs this file, why doesn't it just create it? Amanda doesn't need it --- but you told her to look for it. It's a file that YOU fill in, to say what to exclude from the gnutar backup. If you don't want to use it, remove the exclude= yada yada yada /exclude.gtar line from your dumptype definition. Deb Baddorf --- Deb Baddorf [EMAIL PROTECTED] 840-2289 You can't help getting older, but you don't have to get old. - George Burns IXOYE
Re: Upgrade to 2.4.3 has hiccup
On Fri, Jan 03, 2003 at 05:03:21PM -0500, Jon LaBadie wrote: On Fri, Jan 03, 2003 at 01:15:35PM -0800, John Oliver wrote: On Fri, Jan 03, 2003 at 02:27:30PM -0600, Deb Baddorf wrote: And did you put a file exclude.gtar in there? Yes, I did, and that got rid of the message. But if amanda needs this file, why doesn't it just create it? Because it is a file you create specifying what you want to exclude. If you don't want to use it, don't list it in amanda.conf. It wasn't necessary with 2.4.2 If it's necessary for 2.4.3, then why isn't it installed with or created by that version? -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Upgrade to 2.4.3 has hiccup
On Fri, Jan 03, 2003 at 02:34:32PM -0800, John Oliver wrote: On Fri, Jan 03, 2003 at 05:03:21PM -0500, Jon LaBadie wrote: On Fri, Jan 03, 2003 at 01:15:35PM -0800, John Oliver wrote: On Fri, Jan 03, 2003 at 02:27:30PM -0600, Deb Baddorf wrote: And did you put a file exclude.gtar in there? Yes, I did, and that got rid of the message. But if amanda needs this file, why doesn't it just create it? Because it is a file you create specifying what you want to exclude. If you don't want to use it, don't list it in amanda.conf. It wasn't necessary with 2.4.2 If it's necessary for 2.4.3, then why isn't it installed with or created by that version? Perhaps it is an added extra check that that should have been in 2.4.2. Extra checking is not a bad thing. The file is not necessary. Only if you leave the line uncommented in the dumptype, then the file is necessary. But an empty file does no good and amanda has no idea what you want to put in there so it can not be populated automatically. The amcheck error reminds you, create and put something into the file or get rid of the line in the dumptype. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
