Re: Full backup worked, incrementals fail
I'm guessing that was mentioned somewhere because it sounds vaguely familiar, I just can't place it. I just read the seciton on 'dump' in Unix Backup and Recovery and they didn't seem to mention that, but the error message and your comments had me leaning that way and the manpage removed all doubt (I'm on Redhat 9 linux): files-to-dump is either a mountpoint of a filesystem or a list of files and directories to be backed up as a subset of a filesystem. In the for- mer case, either the path to a mounted filesystem or the device of an unmounted filesystem can be used. In the latter case, certain restric- tions are placed on the backup: -u is not allowed, the only dump level that is supported is -0 and all the files and directories must reside on the same filesystem. Thanks, Fran You need to use GNU tar (be sure its 1.13.19 or greater) to do incrementals of subdirectories. Some dumps only do entire filesystems, and some will let you do full dumps of a subdirectory, but I don't think any will do incrementals of one. frank
host down? [again]
sorry fo the uncomplete previous message! hi, I'm getting something really strange lattely from amanda. when I use for the first time ``amcheck DailySet'', a lot of machines seems to be down ``selfcheck request timed out. Host down?''. When I relauched the ``amcheck DailySet'' then maybe only a few machines are down. And after three launches (but often only 2 are enough) all the machines reply correctly. Server (obssf5) clients (obssb10, ,...) I've checked the: ---amanda email--- FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to obssb10 timed out. .. obssb10/export/diskA1 RESULTS MISSING . obssb10 /export/diskA1 MISSING --- ---obssb10--- /tmp/amanda on obssb10 (client) and I only found one file related! /tmp/amanda/amandad...debug under obssb10: it looks okay (no errors) ---obssf5--- /tmp/amanda there was only amtrmlog...debug amtrmidx...debug with not really interesting information thanks in advance! briner
Re: amanda server on sco 5.0.6
Eric Siegerman said: snipped Can I just remove all references to changer-src from the configure script? I don't need a tape changer. Would I break amanda-server if I tried to compile without changer-src? Not sure; try it and see... OK, removed all from configure, did make clean, re-ran configure, ran make. Everything compiles OK. I installed everything on another SCO 5.0.6 machine. I add the folders and config files that the amanda server and client look for. amcheck runs OK, so I try to run amlabel REDailySet1 REDS1tape01. Now I get a whole bunch of errors like: /usr/local/etc/amanda/REDailySet1/amanda.conf, line 1: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 1: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 2: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 2: end of line expected for every line in the config file. I'm guessing the amanda.conf is fine, because I copied it from a working configuration on Linux and only changed a few specifics. Line 1 should be OK: org Regency DailySet1 So if amlable is having trouble with this line, but this line appears syntactically correct and doesn't cause warnings for amcheck, doesn't it indicate some sort of trouble with my compiled amlabel? Could commenting out changer-src have caused this? Or is it something else? -- Kurt Yoder Sport Health network administrator
RE: Full backup worked, incrementals fail
[EMAIL PROTECTED] writes: You need to use GNU tar (be sure its 1.13.19 or greater) to do incrementals of subdirectories. Some dumps only do entire filesystems, and some will let you do full dumps of a subdirectory, but I don't think any will do incrementals of one. Actually, we found last week that ... or greater might not be right. It turns out that there were some changes in the latest version of GNUTAR (v1.13.92) that basically break the indexing function. Version 1.13.25 is be your best bet. -- Mark
Re: host down? [again]
On Tuesday 23 December 2003 04:08, BRINER Cedric wrote: sorry fo the uncomplete previous message! hi, I'm getting something really strange lattely from amanda. when I use for the first time ``amcheck DailySet'', a lot of machines seems to be down ``selfcheck request timed out. Host down?''. When I relauched the ``amcheck DailySet'' then maybe only a few machines are down. And after three launches (but often only 2 are enough) all the machines reply correctly. Server (obssf5) clients (obssb10, ,...) I've checked the: ---amanda email--- FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to obssb10 timed out. .. obssb10/export/diskA1 RESULTS MISSING . obssb10 /export/diskA1 MISSING --- ---obssb10--- /tmp/amanda on obssb10 (client) and I only found one file related! /tmp/amanda/amandad...debug under obssb10: it looks okay (no errors) ---obssf5--- /tmp/amanda there was only amtrmlog...debug amtrmidx...debug with not really interesting information thanks in advance! briner I think I'd run tcpdump or etherape and see if something is eating your network bndwidth. Or recheck the network configs. Is there a firewall involved? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: amanda server on sco 5.0.6
On Tuesday 23 December 2003 08:53, Kurt Yoder wrote: Eric Siegerman said: snipped Can I just remove all references to changer-src from the configure script? I don't need a tape changer. Would I break amanda-server if I tried to compile without changer-src? Not sure; try it and see... OK, removed all from configure, did make clean, re-ran configure, ran make. Everything compiles OK. I installed everything on another SCO 5.0.6 machine. I add the folders and config files that the amanda server and client look for. amcheck runs OK, so I try to run amlabel REDailySet1 REDS1tape01. Now I get a whole bunch of errors like: /usr/local/etc/amanda/REDailySet1/amanda.conf, line 1: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 1: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 2: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 2: end of line expected for every line in the config file. I'm guessing the amanda.conf is fine, because I copied it from a working configuration on Linux and only changed a few specifics. Line 1 should be OK: org Regency DailySet1 So if amlable is having trouble with this line, but this line appears syntactically correct and doesn't cause warnings for amcheck, doesn't it indicate some sort of trouble with my compiled amlabel? Could commenting out changer-src have caused this? Or is it something else? Is there a missmatch between the system end of line convention, like one is expecting a crlf and the other is lf only? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: amanda server on sco 5.0.6
Gene Heskett said: snipped So if amlable is having trouble with this line, but this line appears syntactically correct and doesn't cause warnings for amcheck, doesn't it indicate some sort of trouble with my compiled amlabel? Could commenting out changer-src have caused this? Or is it something else? Is there a missmatch between the system end of line convention, like one is expecting a crlf and the other is lf only? There shouldn't be. They're both Unix. Also, if there were a mismatch, wouldn't amcheck complain about it? -- Kurt Yoder Sport Health network administrator
Dump Vs Tar tradeoffs (if any)
Title: Dump Vs Tar tradeoffs (if any) All, We are still new to Amanda and would greatly appreciate some advise on how to best configure the system What are the advantages or disadvantages to using tar instead of dump? Is there a difference in restoring a single file? a file system? or the whole system? (other then changing restore to tar x) If it helps, we are using HP/UX 11i (on an N class system) to backup about 10 client (HP/UX 11, HP/UX 11i, and Linux) onto LTO media using a C7200 silo/changer. Thank you, George Henson
Re: amanda server on sco 5.0.6
On Tuesday 23 December 2003 11:01, Kurt Yoder wrote: Gene Heskett said: snipped So if amlable is having trouble with this line, but this line appears syntactically correct and doesn't cause warnings for amcheck, doesn't it indicate some sort of trouble with my compiled amlabel? Could commenting out changer-src have caused this? Or is it something else? Is there a missmatch between the system end of line convention, like one is expecting a crlf and the other is lf only? There shouldn't be. They're both Unix. Also, if there were a mismatch, wouldn't amcheck complain about it? I'd certainly think so Kurt. Maybe it does have something to do with commenting out the changer-src stuffs. Browseing the amlabel srcs might be informative. But you knew that, and I'm just prattling. :) -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
AMdump does not run
Hello folks, as an Amanda newbie I don't know how to imterpret this log. Can you help me? I see two problems: he does not find the tape. That is probably a problem with the changer (I'm using chg-zd-mtx on a HP Autoloader): I'll check the conf-file. The other problem is the message can't switch to incremental dump. What does Amanda want to tell me here? Or is this simply a follow-up from the first error? Background info: I had a test dump on the holding disk and started all over like described in the FAQ (deleting all the files). Does Amanda still 'remember' the first Full backup? = *** A TAPE ERROR OCCURRED: [label Daily02 or new tape not found in rack]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next 6 tapes Amanda expects to used are: Daily02, Daily03, Daily04, Daily05, Daily06, Daily01. FAILURE AND STRANGE DUMP SUMMARY: chef /boot lev 0 FAILED [can't switch to incremental dump] mary /boot lev 0 FAILED [can't switch to incremental dump] mary /data/a/data/aktuell/151_EVA lev 0 FAILED [can't switch to incremental dump] [..] = -- Greetings Stefan Hackenthal[EMAIL PROTECTED] Aldebaran GmbH, Im Moore 26, 30167 Hannover, Telefon 0511-270 416 21
Re: Dump Vs Tar tradeoffs (if any)
George, It's not the only reason I'm sure, but if you wish to exclude files from your archive you must use tar. Dump does not allow this. Drew On Tue, 2003-12-23 at 11:42, Henson, George Mr JMLFDC wrote: All, We are still new to Amanda and would greatly appreciate some advise on how to best configure the system What are the advantages or disadvantages to using tar instead of dump? Is there a difference in restoring a single file? a file system? or the whole system? (other then changing restore to tar x) If it helps, we are using HP/UX 11i (on an N class system) to backup about 10 client (HP/UX 11, HP/UX 11i, and Linux) onto LTO media using a C7200 silo/changer. Thank you, George Henson
RE: Dump Vs Tar tradeoffs (if any)
Yes, one of the big differences is that 'tar' lets you break up larger filesystems into smaller, more manageable DLEs, as well as excluding specific files or file patterns. Be sure that you use 'tar' version 1.13.25 -- nothing older, and nothing newer, until you hear that someone has certified it to be compatible with Amanda. (The latest version, 1.13.92, causes indexing not to work.) Also, I've found that 'tar' seems to take longer in the estimate phase than do 'dump' (and 'vxdump'), but for all I know, that could be due to local influences (e.g., disk traffic). Or has anyone else also found it to be the case that 'tar' estimates take longer than those from 'dump'? -- Mark
Re: AMdump does not run
--On Tuesday, December 23, 2003 17:53:52 +0100 Stefan Hackenthal [EMAIL PROTECTED] wrote: Hello folks, as an Amanda newbie I don't know how to imterpret this log. Can you help me? I see two problems: he does not find the tape. That is probably a problem with the changer (I'm using chg-zd-mtx on a HP Autoloader): I'll check the conf-file. Either a changer config problem or you haven't labeled the tapes. The other problem is the message can't switch to incremental dump. What does Amanda want to tell me here? Or is this simply a follow-up from the first error? It's telling you that either your config is set to only do fulls or you've never done a full before on those filesystems so there is nothing to run an incremental against (or possibly there is not enough space on the holding disk, but I think that gives a different error.) Frank Background info: I had a test dump on the holding disk and started all over like described in the FAQ (deleting all the files). Does Amanda still 'remember' the first Full backup? = *** A TAPE ERROR OCCURRED: [label Daily02 or new tape not found in rack]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next 6 tapes Amanda expects to used are: Daily02, Daily03, Daily04, Daily05, Daily06, Daily01. FAILURE AND STRANGE DUMP SUMMARY: chef /boot lev 0 FAILED [can't switch to incremental dump] mary /boot lev 0 FAILED [can't switch to incremental dump] mary /data/a/data/aktuell/151_EVA lev 0 FAILED [can't switch to incremental dump] [..] = -- Greetings Stefan Hackenthal[EMAIL PROTECTED] Aldebaran GmbH, Im Moore 26, 30167 Hannover, Telefon 0511-270 416 21 -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda server on sco 5.0.6
Gene Heskett said: On Tuesday 23 December 2003 11:01, Kurt Yoder wrote: Gene Heskett said: snipped So if amlable is having trouble with this line, but this line appears syntactically correct and doesn't cause warnings for amcheck, doesn't it indicate some sort of trouble with my compiled amlabel? Could commenting out changer-src have caused this? Or is it something else? Is there a missmatch between the system end of line convention, like one is expecting a crlf and the other is lf only? There shouldn't be. They're both Unix. Also, if there were a mismatch, wouldn't amcheck complain about it? I'd certainly think so Kurt. Maybe it does have something to do with commenting out the changer-src stuffs. Browseing the amlabel srcs might be informative. But you knew that, and I'm just prattling. :) Eh... forgive me, but I am a bit allergic to C source. Just not that familiar with it. Someday... OK, I figured out the problem with make. I think my sources got messed up somehow. So I re-downloaded a virgin copy and configure/make/make install worked without and changer-src trickery. However, I'm still faced with the same problem when trying to run amlabel. Maybe someone on the list can recommend something to try based on what is in my configs, plust the errors I am getting? Here's output of amlabel REDailySet1 REDS1tape01: /usr/local/etc/amanda/REDailySet1/amanda.conf, line 1: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 1: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 2: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 2: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 3: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 6: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 6: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 7: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 7: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 8: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 8: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 10: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 10: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 11: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 11: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 12: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 12: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 14: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 14: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 15: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 15: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 18: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 18: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 19: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 19: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 20: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 20: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 21: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 21: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 23: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 23: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 24: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 24: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 25: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 25: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 26: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 26: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 27: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 28: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 28: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 29: configuration keyword expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 29: end of line expected /usr/local/etc/amanda/REDailySet1/amanda.conf, line 30:
RE: Dump Vs Tar tradeoffs (if any)
On Tue, 23 Dec 2003 [EMAIL PROTECTED] wrote: Also, I've found that 'tar' seems to take longer in the estimate phase than do 'dump' (and 'vxdump'), but for all I know, that could be due to local influences (e.g., disk traffic). Or has anyone else also found it to be the case that 'tar' estimates take longer than those from 'dump'? Tar has to stat every file to find out how much is going to be backed up. Dump just has to look at the filesystem as a whole. Far less work involved. -Mitch
Issue with tape changer configuration
Title: Issue with tape changer configuration All, We new to Amanda and are having an issue getting the bar code reader to work in our tape changer. We have an HP C7200 (2 LTO drives/20 media slots) connected to an N class HP Server (HP/UX 11i amanda-2.4.4). The HP supplied utils (ltt tools) are able to read the barcode info from the tape silo, move the tapes, and inventory the robot with no known issues. I have tried to configure the chg-scsi interface with marginal success. If I turn off the barcode reader (havebarcode 0) then I can get Amanda to run backups and amtape seems to act normal. If I understand correctly, this also means the system must do a linear search for the media in the silo, instead of using the barcode info. Once I turn on the bar code reader (havebarcode 1) then I error messages from amtape and backups fail. When I try using the chg-scsi (chg-scsi -slot 3) command directly to move the media from slot n into the drive, it moves the media, but then reports an error: BarCode == 1 and enubarcode == 1 with and exit status of 2 If I issue the same command again it returns success. The other oddity I have noticed is if I issue the command to inventory the silo (chg-scsi -inventory) the label file grows very quickly to fill the disk. Thank you in advance, George Henson
Re: NT backup
hello again! i got the samba working so i can talk with the ms box. now i'm trying to get the amanda win32 working to try and backup the system. i am connecting to the MS box but i am getting an error that i can't seem to figure out when i'm running amcheck. -bash-2.05b$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 28918452 KB disk space available, that's plenty amcheck-server: slot 4: date 20031205 label DailySet103 (exact label match) NOTE: skipping tape-writable test Tape DailySet103 label ok Server check took 0.320 seconds Amanda Backup Client Hosts Check ERROR: NAK hccdevelop03: execute access to /usr/amanda/libexec/selfcheck denied Client check: 2 hosts checked in 0.135 seconds, 1 problem found the directory setup on the MS machine does not contain anything called selfcheck. do i need this here or should it be running from my linux machine? also, on my MS maching i do not have a folder under usr called lib. again is this a problem. Thanks for all the help. I'm just getting started with this and i tend to get stuck A LOT!!! jess On Mon, 2003-12-22 at 17:33, Gene Heskett wrote: On Monday 22 December 2003 15:52, jessica blackburn wrote: Hello! I'm trying to back up an NT file system using a Linux file system. I currently run amanda on my linux machine, however, i'm having numerous problems attempting to get the nt systems backed-up. i've tried both the amanda win32 and the samba and cannot get either to work. using samba i am able to look at the linux machine from the nt machine but i've been unsuccessful the other way. when using the win32 i am getting the error host down and 1 problem found. any recommendations on which approach to take and how best to tackle this? any and all help is greatly appreciated!! thanks! jess Hirzel Canning Company Northwood, OH [EMAIL PROTECTED] I take it that you are not aware that the NT filesystem is rated read only by the linux drivers? I do not know if thats because its such a moving target, or if doing the correct write things requires using something patented by M$. However, I'd investigate the latest cifs, aka samba stuff, and see if a bridge could be built using it. Make sure you are using the latest cifs release on the NT box, and the latest samba 3.0something on the amanda server. That might have a chance of working. There is also another group whose name escapes me ATM, who have had some success getting amanda as a client to work on windows boxes, so you might want to investigate that route too.
Re: NT backup
jessica blackburn said: hello again! i got the samba working so i can talk with the ms box. now i'm trying to get the amanda win32 working to try and backup the system. i am connecting to the MS box but i am getting an error that i can't seem to figure out when i'm running amcheck. -bash-2.05b$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 28918452 KB disk space available, that's plenty amcheck-server: slot 4: date 20031205 label DailySet103 (exact label match) NOTE: skipping tape-writable test Tape DailySet103 label ok Server check took 0.320 seconds Amanda Backup Client Hosts Check ERROR: NAK hccdevelop03: execute access to /usr/amanda/libexec/selfcheck denied Client check: 2 hosts checked in 0.135 seconds, 1 problem found This looks an awful lot like an amanda-win32-client error. Are you sure you're actually using samba in your disklist? It should look like machine_with_smbclient //hccdevelop03/c$ user-tar if it looks like hccdevelop03 /mnt_c user-tar you're still using win32 client -- Kurt Yoder Sport Health network administrator
Re: NT backup
I think im using the amanda win32 because i could get samba to see the files of the MS box but not back them up. so, i moved on the try the win32. do i need to use samba and win32 together? or just one over the other? and if so which is better? On Tue, 2003-12-23 at 14:19, Kurt Yoder wrote: jessica blackburn said: hello again! i got the samba working so i can talk with the ms box. now i'm trying to get the amanda win32 working to try and backup the system. i am connecting to the MS box but i am getting an error that i can't seem to figure out when i'm running amcheck. -bash-2.05b$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 28918452 KB disk space available, that's plenty amcheck-server: slot 4: date 20031205 label DailySet103 (exact label match) NOTE: skipping tape-writable test Tape DailySet103 label ok Server check took 0.320 seconds Amanda Backup Client Hosts Check ERROR: NAK hccdevelop03: execute access to /usr/amanda/libexec/selfcheck denied Client check: 2 hosts checked in 0.135 seconds, 1 problem found This looks an awful lot like an amanda-win32-client error. Are you sure you're actually using samba in your disklist? It should look like machine_with_smbclient //hccdevelop03/c$ user-tar if it looks like hccdevelop03 /mnt_c user-tar you're still using win32 client
Re: NT backup
jessica blackburn said: I think im using the amanda win32 because i could get samba to see the files of the MS box but not back them up. so, i moved on the try the win32. do i need to use samba and win32 together? or just one over the other? and if so which is better? That's odd. You should be able to read/copy the files using smbclient if you can see them. Did you try manually connecting using smbclient? You should be able to use smbclient to copy a file from the windows machine to your linux machine. If this works, amanda's samba connection should work too. I was using the win32 client for a while, but found it troublesome. You can't verify the amanda backups, because they are in nttar format. So you have no idea whether the backups are actually working. Also, I wasn't able to get nttar to restore any backups using the included gui. I had to manually dump the whole backup file to the windows machine, then use nttar to extract individual files; very time consuming and inefficient. Plus, the win32 backups would inexplicably fail frequently. So I just gave up on it altogether. -- Kurt Yoder Sport Health network administrator
Re: NT backup
On Tue, Dec 23, 2003 at 02:07:07PM -0500, jessica blackburn wrote: i got the samba working so i can talk with the ms box. now i'm trying to get the amanda win32 working to try and backup the system. i am connecting to the MS box but i am getting an error that i can't seem to figure out when i'm running amcheck. -bash-2.05b$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check Amanda Backup Client Hosts Check ERROR: NAK hccdevelop03: execute access to /usr/amanda/libexec/selfcheck denied Client check: 2 hosts checked in 0.135 seconds, 1 problem found the directory setup on the MS machine does not contain anything called selfcheck. This, I believe, is the root of the above-reported problem. do i need this here or should it be running from my linux machine? also, on my MS maching i do not have a folder under usr called lib. again is this a problem. Well, if you want the MS box's selfcheck to work, you do need a nominally-functional selfcheck on that box. It (selfcheck) is not necessary for the backups themselves to work, though. Thanks for all the help. I'm just getting started with this and i tend to get stuck A LOT!!! The MS/win32 stuff tends to be a lot more confusing than more reasonable system are. :-} Peace, david -- David H. Wolfskill [EMAIL PROTECTED]
Re: Dump Vs Tar tradeoffs (if any)
On Tue, Dec 23, 2003 at 11:42:14AM -0500, Henson, George Mr JMLFDC wrote: What are the advantages or disadvantages to using tar instead of dump? (This is partially brief repetition, but also contains new points.) In dump's favour: - The estimate phase is faster - It doesn't change any of the timestamps of files it's backing up (tar doesn't change mtime either of course, but can't avoid changing either atime or ctime (actually, I recently read that Solaris provides a way, if you're root, but I don't know whether GNU tar takes advantage of it) - You can do interactive restores natively. (amrecover gives you the same functionality, regardless of dump vs. tar, so this difference *only* applies if Amanda isn't in the loop at restore time, or if you don't have the index files, which amrecover requires.) - Dump programs are customized to the local file system's idiosyncracies. I'm guessing (but don't know) that this means that dump can back up system-dependent metadata that tar has no clue about (ACLs, Linux ext2 chattr flags, FreeBSD's chflags variant thereof, and the like) In tar's favour: - You can exclude files - You can split a partition into multiple DLE's. This is necessary if you have partitions larger than will fit on a single tape, since Amanda can't split a single dump onto multiple tapes (not yet anyway; work is in progress, hooray!). - Dump is reported to be undependable on Linux -- Linus says so, anyway. (He has a thing against dump, so doesn't see that as a problem, but IMO it's because Linux has deviated from standard UNIX in undesirable ways. Regardless of blame, though, it's an issue to be dealt with.) - Backups are portable. The downside of every dump being customized to its file system is that you very likely can't restore a dump from platform X using platform Y's restore. I've never tried cross-file-system restores on the same box (restoring from a Solaris VXFS dump onto a Solaris ufs partition, for example), but I imagine that whether you can get away with it depends on the specific combination and the specific platform. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
Re: amanda server on sco 5.0.6
On Tuesday 23 December 2003 12:35, Kurt Yoder wrote:
Gene Heskett said:
On Tuesday 23 December 2003 11:01, Kurt Yoder wrote:
Gene Heskett said:
snipped
So if amlable is having trouble with this line, but this line
appears syntactically correct and doesn't cause warnings for
amcheck, doesn't it indicate some sort of trouble with my
compiled
amlabel? Could commenting out changer-src have caused this? Or
is it
something else?
Is there a missmatch between the system end of line convention,
like one is expecting a crlf and the other is lf only?
There shouldn't be. They're both Unix. Also, if there were a
mismatch, wouldn't amcheck complain about it?
I'd certainly think so Kurt. Maybe it does have something to do
with
commenting out the changer-src stuffs. Browseing the amlabel srcs
might be informative. But you knew that, and I'm just prattling.
:)
Eh... forgive me, but I am a bit allergic to C source. Just not that
familiar with it. Someday...
OK, I figured out the problem with make. I think my sources got
messed up somehow. So I re-downloaded a virgin copy and
configure/make/make install worked without and changer-src trickery.
However, I'm still faced with the same problem when trying to run
amlabel. Maybe someone on the list can recommend something to try
based on what is in my configs, plust the errors I am getting?
This is odd. I haven't noted any changes to amlabel of late, and it
worked the last time I used it with the -f option just fine.
Whats happened here is going to have to be troubleshot on a system
either with the good data moved out of the way, or on a throwaway
system. Has anyone else encountered this?
Here's output of amlabel REDailySet1 REDS1tape01:
/usr/local/etc/amanda/REDailySet1/amanda.conf, line 1:
configuration keyword expected
/usr/local/etc/amanda/REDailySet1/amanda.conf, line 1: end of line
expected
/usr/local/etc/amanda/REDailySet1/amanda.conf, line 2:
configuration keyword expected
/usr/local/etc/amanda/REDailySet1/amanda.conf, line 2: end of line
expected
[snip the rest which repeats for the length of his amanda.conf]
Here's my /usr/local/etc/amanda/REDailySet1/amanda.conf:
org Regency DailySet1
dumpcycle 7 days# the number of days in the normal dump
cycle tapecycle 7 tapes # the number of tapes in rotation
runspercycle 7
bumpsize 20 MB # minimum savings (threshold) to bump level
1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
labelstr REDS1tape[0-9][0-9]*
infofile /usr/local/amanda/lib/REDailySet1/curinfo
logfile /usr/local/amanda/log/REDailySet1/log
indexdir /usr/local/amanda/lib/REDailySet1/index
includefile /usr/local/etc/amanda/amanda.conf.main
Here's my /usr/local/etc/amanda/amanda.conf.main:
mailto [EMAIL PROTECTED]
dumpuser backup
inparallel 4
netusage 36000
tapedev /dev/nrStp0
reserve 25
tapetype DDS3
holdingdisk hold1 {
comment Main holding disk
directory /usr/local/amanda/holdingdisk
use 4 GB
}
etimeout 3200
dtimeout 3600
ctimeout 60
columnspec
Disk=1:10,HostName=0:10,Level=1:2,OrigKB=1:9,OutKB=1:9,Compress=1:6
,DumpTime=1:7,DumpRate=1:7,TapeTime=1:7,TapeRate=1:7
define tapetype QIC-60 {
comment Archive Viper
length 60 mbytes
filemark 100 kbytes
speed 100 kbytes
}
define tapetype DEC-DLT2000 {
comment DEC Differential Digital Linear Tape 2000
length 15000 mbytes
filemark 8 kbytes
speed 1250 kbytes
}
define tapetype DLT {
comment DLT tape drives
length 2 mbytes
filemark 2000 kbytes
speed 1500 kbytes
}
define tapetype DLT-80 {
comment DLT 40/80 tape drive produced by tapetype program
length 37595 mbytes
filemark 32 kbytes
speed 5608 kps
}
define tapetype SURESTORE-1200E {
comment HP AutoLoader
length 3900 mbytes
filemark 100 kbytes
speed 500 kbytes
}
define tapetype EXB-8500 {
comment Exabyte EXB-8500 drive on decent machine
length 4200 mbytes
filemark 48 kbytes
speed 474 kbytes
}
define tapetype EXABYTE {
comment Exabyte EXB-8200 drive on decent machine
length 2200 mbytes
filemark 2130 kbytes
speed 240 kbytes
}
define tapetype EXB-8200 {
comment Exabyte EXB-8200 drive on decent machine
length 2200 mbytes
filemark 2130 kbytes
speed 240 kbytes
}
define tapetype HP-DAT {
comment DAT tape drives
length 1900 mbytes
filemark 100 kbytes
speed 500 kbytes
}
define tapetype DAT {
comment DAT tape drives
length 1000 mbytes
filemark 100 kbytes
speed 100 kbytes
Re: Issue with tape changer configuration
On Tuesday 23 December 2003 13:57, Henson, George Mr JMLFDC wrote: All, We new to Amanda and are having an issue getting the bar code reader to work in our tape changer. We have an HP C7200 (2 LTO drives/20 media slots) connected to an N class HP Server (HP/UX 11i amanda-2.4.4). The HP supplied utils (ltt tools) are able to read the barcode info from the tape silo, move the tapes, and inventory the robot with no known issues. I have tried to configure the chg-scsi interface with marginal success. If I turn off the barcode reader (havebarcode 0) then I can get Amanda to run backups and amtape seems to act normal. If I understand correctly, this also means the system must do a linear search for the media in the silo, instead of using the barcode info. Once I turn on the bar code reader (havebarcode 1) then I error messages from amtape and backups fail. When I try using the chg-scsi (chg-scsi -slot 3) command directly to move the media from slot n into the drive, it moves the media, but then reports an error: BarCode == 1 and enubarcode == 1 with and exit status of 2 The above is I hope a typu? enubarcode s/b emubarcode, but... I think they are mutually exclusive. Also, at one point I recall reading somebodies notes, maybe Thomas Hepper's, that because of a lack of access to barcode equipt changers, the barcode stuff had been turned off. But I haven't looked at that recently, and fixes could have come into the tree at any time in the last 18 months without my taking real note of it. Does anyone else recall the status of the barcode code? My ageing grey matter isn't very clear on this. If I issue the same command again it returns success. The other oddity I have noticed is if I issue the command to inventory the silo (chg-scsi -inventory) the label file grows very quickly to fill the disk. Thats certainly a no-no. :( Thank you in advance, George Henson -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: NT backup
On Tuesday 23 December 2003 14:07, jessica blackburn wrote: hello again! i got the samba working so i can talk with the ms box. now i'm trying to get the amanda win32 working to try and backup the system. i am connecting to the MS box but i am getting an error that i can't seem to figure out when i'm running amcheck. -bash-2.05b$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 28918452 KB disk space available, that's plenty amcheck-server: slot 4: date 20031205 label DailySet103 (exact label match) NOTE: skipping tape-writable test Tape DailySet103 label ok Server check took 0.320 seconds Amanda Backup Client Hosts Check ERROR: NAK hccdevelop03: execute access to /usr/amanda/libexec/selfcheck denied Client check: 2 hosts checked in 0.135 seconds, 1 problem found the directory setup on the MS machine does not contain anything called selfcheck. do i need this here or should it be running from my linux machine? also, on my MS maching i do not have a folder under usr called lib. again is this a problem. Tisn't lib, its 'amanda/libexec', as in $prefix/libexec/selfcheck, and it should be executable (I think, its a winderz box, me not winderz expert) by amanda. Go re-read the installation instructs for the win32 client version dbl check it from the top down. Aka, yes, its a problem :) Here, on my only client, there isn't an 'amanda' in that path, just /usr/local/libexec/selfcheck etc. There is also no firewall as its on the other side of the client machine here. However, IIRC that would have been set in the configure that built that win32 client object, so its a no brainer as long as they actually match, or at least I'd assume that till informed otherwise. Thanks for all the help. I'm just getting started with this and i tend to get stuck A LOT!!! We all did the first time. :-) jess On Mon, 2003-12-22 at 17:33, Gene Heskett wrote: On Monday 22 December 2003 15:52, jessica blackburn wrote: Hello! I'm trying to back up an NT file system using a Linux file system. I currently run amanda on my linux machine, however, i'm having numerous problems attempting to get the nt systems backed-up. i've tried both the amanda win32 and the samba and cannot get either to work. using samba i am able to look at the linux machine from the nt machine but i've been unsuccessful the other way. when using the win32 i am getting the error host down and 1 problem found. any recommendations on which approach to take and how best to tackle this? any and all help is greatly appreciated!! thanks! jess Hirzel Canning Company Northwood, OH [EMAIL PROTECTED] I take it that you are not aware that the NT filesystem is rated read only by the linux drivers? I do not know if thats because its such a moving target, or if doing the correct write things requires using something patented by M$. However, I'd investigate the latest cifs, aka samba stuff, and see if a bridge could be built using it. Make sure you are using the latest cifs release on the NT box, and the latest samba 3.0something on the amanda server. That might have a chance of working. There is also another group whose name escapes me ATM, who have had some success getting amanda as a client to work on windows boxes, so you might want to investigate that route too. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: NT backup
On Tuesday 23 December 2003 14:19, Kurt Yoder wrote: jessica blackburn said: hello again! i got the samba working so i can talk with the ms box. now i'm trying to get the amanda win32 working to try and backup the system. i am connecting to the MS box but i am getting an error that i can't seem to figure out when i'm running amcheck. -bash-2.05b$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 28918452 KB disk space available, that's plenty amcheck-server: slot 4: date 20031205 label DailySet103 (exact label match) NOTE: skipping tape-writable test Tape DailySet103 label ok Server check took 0.320 seconds Amanda Backup Client Hosts Check ERROR: NAK hccdevelop03: execute access to /usr/amanda/libexec/selfcheck denied Client check: 2 hosts checked in 0.135 seconds, 1 problem found This looks an awful lot like an amanda-win32-client error. Are you sure you're actually using samba in your disklist? It should look like machine_with_smbclient //hccdevelop03/c$ user-tar if it looks like hccdevelop03 /mnt_c user-tar you're still using win32 client Yes, and let me toss in my thoughts re using samba/cifs. 1. Unless the NTFS supports the time stamps that unix does, amanda's concept of an incremental is a level 0 because it cannot tell from the times reported over the samba link if it backed up that file last night or not, so it does a fresh backup everynight of such stuff. 2. Because not all perms are properly reported by the samba/cifs link, perms on the restored files may, and probably will, be fubar'd somewhere along the line. For those 2 reasons, I would much prefer the win32 client, which can *probably* handle those two cases more accurately than the cifs/samba linkage can. However, like most on this list, I have little knowledge of the win32 client, never having seen it. So I'll certainly defer to someone who does have it working. Please speak up, whoever you are! -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: NT backup
On Tuesday 23 December 2003 14:24, jessica blackburn wrote: I think im using the amanda win32 because i could get samba to see the files of the MS box but not back them up. so, i moved on the try the win32. do i need to use samba and win32 together? or just one over the other? and if so which is better? They would be two seperate programs Jessica. Having samba lets you look at the files, move or copy them to/from your machine generally gives the human an eye into things. But the win32 client should be able to run regardless of the samba connection status. On Tue, 2003-12-23 at 14:19, Kurt Yoder wrote: jessica blackburn said: hello again! i got the samba working so i can talk with the ms box. now i'm trying to get the amanda win32 working to try and backup the system. i am connecting to the MS box but i am getting an error that i can't seem to figure out when i'm running amcheck. -bash-2.05b$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 28918452 KB disk space available, that's plenty amcheck-server: slot 4: date 20031205 label DailySet103 (exact label match) NOTE: skipping tape-writable test Tape DailySet103 label ok Server check took 0.320 seconds Amanda Backup Client Hosts Check ERROR: NAK hccdevelop03: execute access to /usr/amanda/libexec/selfcheck denied Client check: 2 hosts checked in 0.135 seconds, 1 problem found This looks an awful lot like an amanda-win32-client error. Are you sure you're actually using samba in your disklist? It should look like machine_with_smbclient //hccdevelop03/c$ user-tar if it looks like hccdevelop03 /mnt_c user-tar you're still using win32 client -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
amstatus.cgi: happy christmas
Dear amanda users, a new output of amstatus.cgi is available at http://www.osgev.de/other/amanda/index.html This is the outcome of a dump of more than 80 partitions (*1), formatted to be useful for the curious. The upper part is a table of backed up partitions, indicating progress by color and by means of the percentage bars for %dumped and %taped. As the sample is made from a finished dump, the percentages ain't too interesting (100%/0% for all partitions), but note, that these bars are life when a backup is in progress. The lower part, very tall (in this version), displays detailed information of what Amanda did/does. Time passes top - bottom, with a resolution of 1 pixel = 1 second, interesting points in time given literally in the very left column. The next (leftmost graphic) column visualizes taper activity. Following columns show dumpers working in parallel. All these columns indicate progress in time by height of a triangle and progress in % by width of that triangle. Please note, that you may simply click the '%dumped' and '%taped' cells to jump to the corresponding dumper/taper detailed activity. Did you notice the highlight (dumper: yellow bar, taper: red bar) to the right of the details? If not, you should ENABLE JavaScript (no abuse by me, never ever). If you have JavaScript available and active you will see textual information about a detail step, when moving the mouse over one of the triangle visualisation of activity. Also note, that clicking on a triangle brings you back to the overview table. Hope you enjoy this, happy holidays Georg -- ___ ___ | + | |__Georg Rehfeld Woltmanstr. 12 20097 Hamburg |_|_\ |___ [EMAIL PROTECTED]+49 (40) 23 53 27 10 (Delete .nospam from mail address) (*1) dump done by Nicolas Ecarnot, who was so kind to allow me to use his dump files output as the sample
Re: amstatus.cgi: happy christmas
On Wednesday 24 December 2003 00:21, Georg Rehfeld wrote: Dear amanda users, a new output of amstatus.cgi is available at http://www.osgev.de/other/amanda/index.html This is the outcome of a dump of more than 80 partitions (*1), formatted to be useful for the curious. The upper part is a table of backed up partitions, indicating progress by color and by means of the percentage bars for %dumped and %taped. As the sample is made from a finished dump, the percentages ain't too interesting (100%/0% for all partitions), but note, that these bars are life when a backup is in progress. The lower part, very tall (in this version), displays detailed information of what Amanda did/does. Time passes top - bottom, with a resolution of 1 pixel = 1 second, interesting points in time given literally in the very left column. You're right, its very tall. However if this is a live display one could leave running, to be updated at a long enough interval as to not impinge on the progress of the backup, it might be educational on fine tuning things. Thank you and Merry Christmas to you and yours. The next (leftmost graphic) column visualizes taper activity. Following columns show dumpers working in parallel. All these columns indicate progress in time by height of a triangle and progress in % by width of that triangle. Please note, that you may simply click the '%dumped' and '%taped' cells to jump to the corresponding dumper/taper detailed activity. Did you notice the highlight (dumper: yellow bar, taper: red bar) to the right of the details? If not, you should ENABLE JavaScript (no abuse by me, never ever). If you have JavaScript available and active you will see textual information about a detail step, when moving the mouse over one of the triangle visualisation of activity. Also note, that clicking on a triangle brings you back to the overview table. Hope you enjoy this, happy holidays Georg -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
