tapetype Tandberg VS80 DLT
As requested in the readme I post this back to the list.
Tnx to Paul Bijnens for the new patched tapetype
define tapetype tandberg_VS80 {
comment just produced by tapetype prog (hardware compression off)
length 38602 mbytes
filemark 0 kbytes
speed 2781 kps
}
Re: gtar wrapper script (was SAP R/3 backup with amanda)
On Tuesday, 10. September 2002 09:43, Amon Ott wrote: On Monday, 9. September 2002 18:00, Jon LaBadie wrote: On Mon, Sep 09, 2002 at 10:10:30AM -0400, Bort, Paul wrote: There is a tar-wrapper script for people who don't have GNUTar or need to do something non-tar, like dumping a database. Search the amanda-users list archives for it. It works with 2.4.x. I have attached the script to which I think Paul refers. I saved it last January but never checked it out. Don't ask me if or how it works, Thank you - I will have a closer look and probably adapt and test it tomorrow. The tar wrapper script seems to work fine now, thank you. However, there is some strange Amanda 2.4.3b4 behaviour in amrecover: If you try to restore with an Amanda compilation (e.g. on another system), which had another --with-gnutar= value to configure, it just fails with an error that e.g. restore of /usr/local/sbin/tar-wrapper and the following exec failed. To me it seems that the GNUTAR backup type is not recognized, so amrecover assumes UNKNOWN and tries a string comparison to find the correct restore program instead of using the compiled path. -- Amon Ott LISA systems
Hostname lookups
Hi all On one of my hosts I run amanda for backups when I run amcheck it tells me --- Amanda Tape Server Host Check - Holding disk /var/amanda: 72958716 KB disk space available, using 68862716 KB NOTE: skipping tape-writable test Tape Test1-001 label ok NOTE: info dir /usr/local/var/amanda/test/curinfo/my host: does not exist NOTE: index dir /usr/local/var/amanda/test/index/my host: does not exist Server check took 5.020 seconds Amanda Backup Client Hosts Check ERROR: my host: [addr 192.168.2.215: hostname lookup failed] Client check: 1 host checked in 0.028 seconds, 1 problem found -- The ip addy it gives back is wrong.[192.168.2.215] should be 192.168.2.208 I added the ip/hostname in my /etc/hosts file I also double checked my dns forward and reverse lookups and all is well there. Any ideas ? I am stumped Mozzi
amcheck output
When running amcheck I get this NOTE: info dir /usr/local/var/amanda/test/curinfo/myhostname.domainname.com/_: does not exist Now I created the directory what else does it need ? Mozzi
RE: Can Amanda put its index on a tape?
Date: 18 Sep 2002 14:29:58 -0800 From: Anthony Valentine [EMAIL PROTECTED] Question: Can Amanda be setup so that it writes a copy of it's indexes to the beginning of each tape? Date: Thu, 19 Sep 2002 00:10:04 +0100 From: Niall O Broin [EMAIL PROTECTED] Subject: Re: Can Amanda put its index on a tape? That'd be a nice feature, but then a lot of things about time travel might be nice :-) I don't think it can be done in the general case, because taping will usually have started before the indices would be updated. Am I right in remembering that amanda has the ability not to start the backup of a particular machine until a given time? Could this mechanism be usurped to force a particular backup to be taped last? Another possibility would be to add to the priority mechanism. I guess this is really one for the hackers, so I hope they read this list too. It sounds fairly simple - but so does time travel :-) Chris Ritson (Computer Officer) Rm 618, Claremont Bridge, EMAIL: [EMAIL PROTECTED] School of Computing Science,PHONE: +44 191 222 8175 University of Newcastle,FAX : +44 191 222 8232 Newcastle on Tyne, UK NE1 7RU. http://www.cs.ncl.ac.uk/~c.r.ritson/
RE: Hostname lookups
Title: RE: Hostname lookups Hey Mozzi, There seems to be an issue with Amanda and reverse DNS lookups - I had many when I wanted to setup backup clients across multiple subnets. But in the end if you have your backup client having the ip/hostname of the backup server in it's /etc/hosts file you should be all set. Have you tried using the FQD of backup_server.domain.com.au in your hosts file on your client? Cheers, Gordon. -Original Message- From: Mozzi [mailto:[EMAIL PROTECTED]] Sent: Thursday, 19 September 2002 5:56 PM To: amanda Subject: Hostname lookups Hi all On one of my hosts I run amanda for backups when I run amcheck it tells me --- Amanda Tape Server Host Check - Holding disk /var/amanda: 72958716 KB disk space available, using 68862716 KB NOTE: skipping tape-writable test Tape Test1-001 label ok NOTE: info dir /usr/local/var/amanda/test/curinfo/my host: does not exist NOTE: index dir /usr/local/var/amanda/test/index/my host: does not exist Server check took 5.020 seconds Amanda Backup Client Hosts Check ERROR: my host: [addr 192.168.2.215: hostname lookup failed] Client check: 1 host checked in 0.028 seconds, 1 problem found -- The ip addy it gives back is wrong.[192.168.2.215] should be 192.168.2.208 I added the ip/hostname in my /etc/hosts file I also double checked my dns forward and reverse lookups and all is well there. Any ideas ? I am stumped Mozzi
Re: Hostname lookups
On Thu, Sep 19, 2002 at 09:55:49AM +0200, Mozzi wrote: Hi all On one of my hosts I run amanda for backups when I run amcheck it tells me --- Amanda Tape Server Host Check - Holding disk /var/amanda: 72958716 KB disk space available, using 68862716 KB NOTE: skipping tape-writable test Tape Test1-001 label ok NOTE: info dir /usr/local/var/amanda/test/curinfo/my host: does not exist NOTE: index dir /usr/local/var/amanda/test/index/my host: does not exist Server check took 5.020 seconds Amanda Backup Client Hosts Check ERROR: my host: [addr 192.168.2.215: hostname lookup failed] Client check: 1 host checked in 0.028 seconds, 1 problem found -- The ip addy it gives back is wrong.[192.168.2.215] should be 192.168.2.208 I added the ip/hostname in my /etc/hosts file I also double checked my dns forward and reverse lookups and all is well there. Any ideas ? I am stumped There are about 7 items on this in the FOM. Have you checked them out? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: gtar wrapper script (was SAP R/3 backup with amanda)
On Thu, Sep 19, 2002 at 09:48:32AM +0200, Amon Ott wrote: The tar wrapper script seems to work fine now, thank you. However, there is some strange Amanda 2.4.3b4 behaviour in amrecover: If you try to restore with an Amanda compilation (e.g. on another system), which had another --with-gnutar= value to configure, it just fails with an error that e.g. restore of /usr/local/sbin/tar-wrapper and the following exec failed. To me it seems that the GNUTAR backup type is not recognized, so amrecover assumes UNKNOWN and tries a string comparison to find the correct restore program instead of using the compiled path. I get something similar happening on my 2.4.2 system. On my w2k/cygwin box, winnie, gtar is in a different location than on my tapehost, butch. Yet if I put a copy of gtar on butch, in the same location as on winnie, then try to do an amrecover it still says the gtar program is not there. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: gtar wrapper script (was SAP R/3 backup with amanda)
On Thursday 19 September 2002 03:48, Amon Ott wrote: On Tuesday, 10. September 2002 09:43, Amon Ott wrote: On Monday, 9. September 2002 18:00, Jon LaBadie wrote: On Mon, Sep 09, 2002 at 10:10:30AM -0400, Bort, Paul wrote: There is a tar-wrapper script for people who don't have GNUTar or need to do something non-tar, like dumping a database. Search the amanda-users list archives for it. It works with 2.4.x. I have attached the script to which I think Paul refers. I saved it last January but never checked it out. Don't ask me if or how it works, Thank you - I will have a closer look and probably adapt and test it tomorrow. The tar wrapper script seems to work fine now, thank you. However, there is some strange Amanda 2.4.3b4 behaviour in amrecover: If you try to restore with an Amanda compilation (e.g. on another system), which had another --with-gnutar= value to configure, it just fails with an error that e.g. restore of /usr/local/sbin/tar-wrapper and the following exec failed. To me it seems that the GNUTAR backup type is not recognized, so amrecover assumes UNKNOWN and tries a string comparison to find the correct restore program instead of using the compiled path. Have you tried sneakernetting the right version of gnutar to the machine, and putting it in the same place as it was configured for? Versions of gnutar before 1.13-19 are also likely suspects, and most are using 1.13-25 now. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: nice web based frontend
On Thursday 19 September 2002 01:45, Neil wrote: Hi guys, My amanda is now up and running. I can backup and restore filesystems now. But there is one thing that I noticed that really brought me to the point where I ask myself why did it do it?. I was backing up /var and it has only 20 megs only and I got 4gig in my tape. 20 megs? Mmmm, mine is about 340. But then RH's up2date keeps its download cache in there. Post your disklist someplace please. I executed su amanda -c amdump Daily. Backup went fine. I executed it again, and it was asking me to insert the tape on slot 2, 3, 4 and so on. This is normal. Amanda will not reuse the same tape until the tapecycle number of tapes has been used, as set in your amanda.conf. What do you think about this? Should it just overwrite the earlier backup? No, see above. Another one... I have in amanda crontab that it executes amdump every Saturday, 10pm. Do I need to rewind the tape before amdump backs it up? No, amanda will do that. But most folks have an amcheck run someplace before that so it will email you if the tape it needs is not available. What I just wanted is to keep overwriting my old Saturday backup since I only have 1 tape for now. Please check out my amanda.conf in http://restricted.dyndns.org/amanda.conf Your tapecycle is set to 25, and your mailto isn't you as normal user. you only have one tape, and dumpcycle is 4 weeks, with runspercycle at 20. Also the tapetype you used is only a 1970 megger, how did you get 4 gigs on it? A 500 meg holding disk is not adequate for the average home system even. A successfull run will leave the holding disk empty, but the capcity to act as a buffer between the fast disks and the relatively slow tape make it a huge time saver in the overlal scheme of things. One should have something in excess of 2x a tapes capacity unless you have both a fast tape, and its bigger than your whole hard drive setup. This all needs to be adjusted. Is it possible with amanda that it is able to backup and restore a whole unix operating system(ex. FreeBSD). No, because you need at least a working minimal install with the filesystems formatted, and dd and tar plus whatever decompressor was used to make the tapes compressions available before a restore can be started. Such a system can be had from most of the one floppy boots however. The reason I asked this is because of AIX unix backup/restore. It's quite cool. Even the tape was bootable. That would be provided the bios could be set to boot from tape. I personally have not seen such a bios except for a very old NCR machine we scrapped for its cabinet. Its boot device was some sort of an audio casette based drive, but the drive was fully servo'd, triple motors and all that plus its heads were visibly shot. It also had 2 of the 3M ten meg removable (the blue pie case with a 14 disk in it) drives, to say it was a bit of jurrasic park technology wasn't an exageration. So here is what I wanted: 1. Attach a second harddisk on the computer 2. Restore the whole backed up FreeBSD to the second harddisk 3. Remove the second harddisk and connect it to another machine I don't see any reason why that couldn't be done provided the controllers are compatible. Lastly, as my subject goes, is there any good web-based frontend for Amanda? No. And likely never will be since thats not the main focus of the amanda design, being as rock-solid dependable as the drive itself has a much higher priority. Someone mentioned he was doing a gui for amrestore a few weeks back but I haven't seen a release of any code noted here on this list. However, in the case of a *real* restore, rather than just going back after a file that was accidentally deleted, where are you gonna get the gui to do the restore with? Pretty good question, that. :-( Amanda's basic tenet is to remove as much as possible, the human operator and his mistakes from the backup reliability picture. To that end its designed to be run as a cron job, with a tape changer if possible, with the only human intervention being the changing of the tapes when required. The human part other than shuffling tapes should only come into the picture when its time to make a restore, something you wouldn't wish to happen often enough to be well trained in doing, and one of the reasons a test restore should be done of a few files to trash directory once in a while. Thank you guys. Ronneil -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: amcheck output
On Thursday 19 September 2002 04:16, Mozzi wrote: When running amcheck I get this NOTE: info dir /usr/local/var/amanda/test/curinfo/myhostname.domainname.com/_: does not exist Now I created the directory what else does it need ? Mozzi NOTE type advisories from amcheck aren't real problems as they will be created when amdump runs. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: win32
I tried for days to get it to work, NO luck. I decided to rewrite the amandad in perl (doesn't need any external programs other than Perl and a few modules). I currently have a VERY alpha version of this working here. I should be ready to release 0.02 next week. Is anyone interested? Jim On Wed, 11 Sep 2002, Galen Johnson wrote: Hello gang, A while back I had sent a request regarding backing up windows machines without having to deal with samba. Someone had responded with the win32 Amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully? *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.266484 secs) *** Qmail-Scanner Envelope Details End ***
Re: win32
If it handles exclusions, hell yes. My users are a lot of analysis engineers and I need to be able to exclude some HUGE interim files made during analasys processing. Jim Buttafuoco wrote: [EMAIL PROTECTED]"> I tried for days to get it to work, NO luck. I decided to rewrite the amandad in perl (doesn't need any external programs other than Perl and a few modules). I currently have a VERY alpha version of this working here. I should be ready to release 0.02 next week. Is anyone interested?Jim On Wed, 11 Sep 2002, Galen Johnson wrote: Hello gang,A while back I had sent a request regarding backing up windows machines without having to deal with samba. Someone had responded with the win32 Amanda client on sourceforge. I have looked it up and it seems like it'll do what I want. However, it hasn't been touched in 18 months. Is anyone currently using this with Amanda 2.4.3.b4? I downloaded this package but have been unable to get it to work - anyone using it successfully?*** Qmail-Scanner Envelope Details Begin ***X-Qmail-Scanner-Mail-From: "[EMAIL PROTECTED]" via maat.reeusda.govX-Qmail-Scanner-Rcpt-To: "[EMAIL PROTECTED]"X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.266484 secs)*** Qmail-Scanner Envelope Details End ***
Re: Hostname lookups[continued]
Gene Heskett wrote: k 5.020 seconds Amanda Backup Client Hosts Check ERROR: my host: [addr 192.168.2.215: hostname lookup failed] Client check: 1 host checked in 0.028 seconds, 1 problem found -- The ip addy it gives back is wrong.[192.168.2.215] should be 192.168.2.208 I added the ip/hostname in my /etc/hosts file I also double checked my dns forward and reverse lookups and all is well there. How about the entry in .amandahosts? Now I get this Amanda Backup Client Hosts Check ERROR: client1.domain.com: [backuphost.domain.com.84.25.196.in-addr.arpa: hostname lookup failed] ERROR: client2.domain.com: [backuphost.domain.com.84.25.196.in-addr.arpa: hostname lookup failed] Client check: 2 hosts checked in 0.036 seconds, 2 problems found When I do a reverse lookup for the backuphost from the backuphost and from both the clients I get the correct response Also for both the clients # host ip addy So my os (Linux) is doing correct resolving and reverse lookups. The entry's on my named server have also been checked. My .amandahosts files on the clients and backuphost are checked and correct. Allowing the clients in as root on backuphost and backuphost in as amanda on clients I have tried putting the clients in the /etc/hosts file and taken them out I have checked my /tmp/amanda files And done searches in the mail archives and the faq o matic All hosts are on the same subnet on the same (cisco)switch Have I missed something ? Still stumped Mozzi
Processing Time
I cron schedule my amanda dump for 12:45 am, but it doesn't complete until about 9:00am. If I look at my switch graphs, the data transfer only takes about 1 hour. What is it doing the rest of the time???
Re: Processing Time
On Thu, Sep 19, 2002 at 08:52:31AM -0400, Jason Greenberg wrote: I cron schedule my amanda dump for 12:45 am, but it doesn't complete until about 9:00am. If I look at my switch graphs, the data transfer only takes about 1 hour. What is it doing the rest of the time??? Writing to the tape. Amanda collects data to the holding disk as quickly as she can (within the limits of bandwidth usage specified in the configuration) and stores it until the tape is ready for it. Tapes are a lot slower than modern networks.
Re: Processing Time
--On Thursday, September 19, 2002 08:52:31 -0400 Jason Greenberg [EMAIL PROTECTED] wrote: I cron schedule my Amanda dump for 12:45 am, but it doesn't complete until about 9:00am. If I look at my switch graphs, the data transfer only takes about 1 hour. What is it doing the rest of the time??? Look at your daily report, it tells you how long it took to dump and tape each disklist entry and the total dump and tape time. If you want to know what's going on while Amanda is still running, then run amstatus and it will tell you. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: win32
On Sep 18, JC Simonetti wrote: | If someone is interested in going through the development | of this client, we might start the development again... But | I cannot do it alone, I do not have enough time. What i don't understand is why noone's actually looked at writing a native port of amandad or why NTTAR is used rather than ntbackup or some other native tool. (I don't believe NTTAR will work for everything, for instance MS Exchange..) IMO, the samba hack is a nasty kludge, and totally inappropriate for a lot of things as it doesn't handle extended attributes (such as ACLs). The amanda-win32 looked promising, but nothing's been happening with it for a long time as people have mentioned. And it is based on the PW32 SF project which is in the same state of abandonment as amanda-win32, so you're actually looking at 2 projects to maintain, not just one. Also, it seems that it would be much less work to actually port the existing (UNIX) amanda source (at least or at most?;) the client parts. Having a separate project really doesn't seem right.
Re: Processing Time
On Thursday 19 September 2002 08:52, Jason Greenberg wrote: I cron schedule my amanda dump for 12:45 am, but it doesn't complete until about 9:00am. If I look at my switch graphs, the data transfer only takes about 1 hour. What is it doing the rest of the time??? Try running amplot, you might be able to decode that better than I. It will show you what it was doing and for how long. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
What can you say about this?
This was the report I got last night during my amdump test. What can you say
about it?
I tried doing an mt erase 0 but looks like that the previous label is
still there. I even tried su amanda -c amlabel -f Daily Daily01, it forces
it but I got a feeling that the old label is still there.
What would be the command to totally erase everything on my tape, including
the labels?
REPORT---
From: User Amanda [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: 19 Sep 2002, 02:06:09 AM
Subject: Daily AMANDA MAIL REPORT FOR September 19, 2002
These dumps were to tape Daily01.
The next tape Amanda expects to use is: Daily001.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 0:51
Dump Time (hrs:min)0:46 0:46 0:00
Output Size (meg)2062.2 2061.90.4
Original Size (meg) 2062.2 2061.90.4
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped3 2 1 (1:1)
Avg Dump Rate (k/s) 761.2 763.1 49.5
Tape Time (hrs:min)0:47 0:46 0:00
Tape Size (meg) 2062.3 2061.90.4
Tape Used (%) 106.9 106.80.0 (level:#disks ...)
Filesystems Taped 3 2 1 (1:1)
Avg Tp Write Rate (k/s) 756.4 757.4 102.5
NOTES:
planner: buko.restricted.dyndns.org /var 20020919 0 [dumps too big, full
dump
delayed]
taper: tape Daily01 kb 2111840 fm 3 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
buko.restric / 0 44480 44512 --0:361246.1 0:56 796.4
buko.restric /usr0 20668802066912 -- 45:31 756.8 45:32 756.6
buko.restric /var1 360416 --0:07 49.5 0:04 102.5
(brought to you by Amanda version 2.4.3b4)
Re: Hostname lookups[continued]
On Thursday 19 September 2002 08:57, Mozzi wrote: Gene Heskett wrote: k 5.020 seconds Amanda Backup Client Hosts Check ERROR: my host: [addr 192.168.2.215: hostname lookup failed] Client check: 1 host checked in 0.028 seconds, 1 problem found -- The ip addy it gives back is wrong.[192.168.2.215] should be 192.168.2.208 I added the ip/hostname in my /etc/hosts file I also double checked my dns forward and reverse lookups and all is well there. How about the entry in .amandahosts? Now I get this Amanda Backup Client Hosts Check ERROR: client1.domain.com: [backuphost.domain.com.84.25.196.in-addr.arpa: hostname lookup failed] ERROR: client2.domain.com: [backuphost.domain.com.84.25.196.in-addr.arpa: hostname lookup failed] Client check: 2 hosts checked in 0.036 seconds, 2 problems found Now you've got me a bit puzzled, mainly because I only see 3 of the 4 numbers of the IP address in the reports above. And not having seen this error, I can't state that its odd or normal. Also, my debug logs don't seem to contain this info either, sorry. When I do a reverse lookup for the backuphost from the backuphost and from both the clients I get the correct response Also for both the clients # host ip addy So my os (Linux) is doing correct resolving and reverse lookups. The entry's on my named server have also been checked. My .amandahosts files on the clients and backuphost are checked and correct. Allowing the clients in as root on backuphost and backuphost in as amanda on clients I have tried putting the clients in the /etc/hosts file and taken them out I have checked my /tmp/amanda files And done searches in the mail archives and the faq o matic All hosts are on the same subnet on the same (cisco)switch Have I missed something ? Still stumped Thats not too bad if the stump came equipt with a jug of good clear lightning. :-) -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: gtar wrapper script (was SAP R/3 backup with amanda)
On Thursday, 19. September 2002 14:06, Gene Heskett wrote: On Thursday 19 September 2002 03:48, Amon Ott wrote: However, there is some strange Amanda 2.4.3b4 behaviour in amrecover: If you try to restore with an Amanda compilation (e.g. on another system), which had another --with-gnutar= value to configure, it just fails with an error that e.g. restore of /usr/local/sbin/tar-wrapper and the following exec failed. To me it seems that the GNUTAR backup type is not recognized, so amrecover assumes UNKNOWN and tries a string comparison to find the correct restore program instead of using the compiled path. Have you tried sneakernetting the right version of gnutar to the machine, and putting it in the same place as it was configured for? Sure, I have put the tar-wrapper whereever it might be looked for. But it only worked, if amrecover was compiled with the same GNUTAR path as on the original client. Looking into the amrecover code showed that a detected GNUTAR backup would lead to the tar compiled into amrecover, so I assumed that the recognition of this backup type failed. Versions of gnutar before 1.13-19 are also likely suspects, and most are using 1.13-25 now. Even a copy of original tar to the other location did not work. Amon. -- Amon Ott LISA systems
Re: What can you say about this?
--On Thursday, September 19, 2002 09:48:22 -0500 Neil
[EMAIL PROTECTED] wrote:
This was the report I got last night during my amdump test. What can you say about
it?
I tried doing an mt erase 0 but looks like that the previous label is still there.
I even tried su amanda -c amlabel -f Daily Daily01, it forces it but I got a
feeling that the old label is still there.
What would be the command to totally erase everything on my tape, including the
labels?
amlabel -f does rewrite the label no matter what label used to be there.
It looks like Amanda took the Daily01 label and did a backup to it.
It also appears that might have been the only tape you labeled and
Amanda is looking for another tape matching labelstr in your config, so
it was looking for Daily001. If you had already labeled a Daily02 it
would have asked for that.
If you were expecting Amanda to keep writing to the same tape, it
won't until you've completed tapecycle number of runs.
Frank
REPORT---
From: User Amanda [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: 19 Sep 2002, 02:06:09 AM
Subject: Daily AMANDA MAIL REPORT FOR September 19, 2002
These dumps were to tape Daily01.
The next tape Amanda expects to use is: Daily001.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 0:51
Dump Time (hrs:min)0:46 0:46 0:00
Output Size (meg)2062.2 2061.90.4
Original Size (meg) 2062.2 2061.90.4
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped3 2 1 (1:1)
Avg Dump Rate (k/s) 761.2 763.1 49.5
Tape Time (hrs:min)0:47 0:46 0:00
Tape Size (meg) 2062.3 2061.90.4
Tape Used (%) 106.9 106.80.0 (level:#disks ...)
Filesystems Taped 3 2 1 (1:1)
Avg Tp Write Rate (k/s) 756.4 757.4 102.5
NOTES:
planner: buko.restricted.dyndns.org /var 20020919 0 [dumps too big, full dump
delayed]
taper: tape Daily01 kb 2111840 fm 3 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
buko.restric / 0 44480 44512 --0:361246.1 0:56 796.4
buko.restric /usr0 20668802066912 -- 45:31 756.8 45:32 756.6
buko.restric /var1 360416 --0:07 49.5 0:04 102.5
(brought to you by Amanda version 2.4.3b4)
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
RE: Hostname lookups[continued]
When I first installed amanda I had this problem too, and fixed it by making sure .amanahosts had correct permissions and correct contents. Here's the specs, in the case when an Amanda server is also an Amanda Client. Server .amandahosts (perms 400) server.com amanda server.com root client1.com root client2.com root client3.com root Client .amandahosts (perms 660) --- server.com amanda Michael Martinez System Administrator -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 11:01 AM To: Mozzi Cc: amanda Subject: Re: Hostname lookups[continued] On Thursday 19 September 2002 08:57, Mozzi wrote: Gene Heskett wrote: k 5.020 seconds Amanda Backup Client Hosts Check ERROR: my host: [addr 192.168.2.215: hostname lookup failed] Client check: 1 host checked in 0.028 seconds, 1 problem found -- The ip addy it gives back is wrong.[192.168.2.215] should be 192.168.2.208 I added the ip/hostname in my /etc/hosts file I also double checked my dns forward and reverse lookups and all is well there. How about the entry in .amandahosts? Now I get this Amanda Backup Client Hosts Check ERROR: client1.domain.com: [backuphost.domain.com.84.25.196.in-addr.arpa: hostname lookup failed] ERROR: client2.domain.com: [backuphost.domain.com.84.25.196.in-addr.arpa: hostname lookup failed] Client check: 2 hosts checked in 0.036 seconds, 2 problems found Now you've got me a bit puzzled, mainly because I only see 3 of the 4 numbers of the IP address in the reports above. And not having seen this error, I can't state that its odd or normal. Also, my debug logs don't seem to contain this info either, sorry. When I do a reverse lookup for the backuphost from the backuphost and from both the clients I get the correct response Also for both the clients # host ip addy So my os (Linux) is doing correct resolving and reverse lookups. The entry's on my named server have also been checked. My .amandahosts files on the clients and backuphost are checked and correct. Allowing the clients in as root on backuphost and backuphost in as amanda on clients I have tried putting the clients in the /etc/hosts file and taken them out I have checked my /tmp/amanda files And done searches in the mail archives and the faq o matic All hosts are on the same subnet on the same (cisco)switch Have I missed something ? Still stumped Thats not too bad if the stump came equipt with a jug of good clear lightning. :-) -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: What can you say about this?
Thanks Frank,
I only have 1 tape at the moment. I am just doing it for testing.
I wanted amanda to only backup once every week, every sat, 11:00pm.
It's ok with me if amanda will overwrite that same tape.
I am going to post my amanda.conf again tonight since I am in the office
right now.
Frank Smith writes:
--On Thursday, September 19, 2002 09:48:22 -0500 Neil
[EMAIL PROTECTED] wrote:
This was the report I got last night during my amdump test. What can you
say about it?
I tried doing an mt erase 0 but looks like that the previous label is
still there. I even tried su amanda -c amlabel -f Daily Daily01, it
forces it but I got a feeling that the old label is still
What would be the command to totally erase everything on my tape,
including the labels?
amlabel -f does rewrite the label no matter what label used to be there.
It looks like Amanda took the Daily01 label and did a backup to it.
It also appears that might have been the only tape you labeled and
Amanda is looking for another tape matching labelstr in your config, so
it was looking for Daily001. If you had already labeled a Daily02 it
would have asked for that.
If you were expecting Amanda to keep writing to the same tape, it
won't until you've completed tapecycle number of runs.
Frank
REPORT---
From: User Amanda [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: 19 Sep 2002, 02:06:09 AM
Subject: Daily AMANDA MAIL REPORT FOR September 19, 2002
-
---
These dumps were to tape Daily01.
The next tape Amanda expects to use is: Daily001.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 0:51
Dump Time (hrs:min)0:46 0:46 0:00
Output Size (meg)2062.2 2061.90.4
Original Size (meg) 2062.2 2061.90.4
Avg Compressed Size (%) -- -- --(level:#disks
...)
Filesystems Dumped3 2 1 (1:1)
Avg Dump Rate (k/s) 761.2 763.1 49.5
Tape Time (hrs:min)0:47 0:46 0:00
Tape Size (meg) 2062.3 2061.90.4
Tape Used (%) 106.9 106.80.0 (level:#disks
...)
Filesystems Taped 3 2 1 (1:1)
Avg Tp Write Rate (k/s) 756.4 757.4 102.5
NOTES:
planner: buko.restricted.dyndns.org /var 20020919 0 [dumps too big, full
dump
delayed]
taper: tape Daily01 kb 2111840 fm 3 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
buko.restric / 0 44480 44512 --0:361246.1 0:56 796.4
buko.restric /usr0 20668802066912 -- 45:31 756.8 45:32 756.6
buko.restric /var1 360416 --0:07 49.5 0:04 102.5
(brought to you by Amanda version 2.4.3b4)
--
Frank Smith
[EMAIL PROTECTED]
Systems Administrator Voice:
512-374-4673
Hoover's Online Fax:
512-374-4501
Re: Hostname lookups[continued]
On Thursday 19 September 2002 11:31, Martinez, Michael - CSREES/ISTM wrote: When I first installed amanda I had this problem too, and fixed it by making sure .amanahosts had correct permissions and correct contents. Here's the specs, in the case when an Amanda server is also an Amanda Client. Server .amandahosts (perms 400) server.com amanda server.com root client1.com root client2.com root client3.com root Client .amandahosts (perms 660) --- server.com amanda Michael Martinez System Administrator Thanks Michael, I had forgotten that little but very important detail (again). Can I blame it on alzheimers? Memory, second thing to go you know. Getting old does not come highly recommended from those who have done so. It makes practice at apologizing unneccessary because you do it often enough for real to stay in practice. :-) These perms are very important, and amanda will reject excessive perms on this .amandahosts file. -Original Message- [...] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Weird permission problem running amdump
Hi, everyone, OK, I admit it. amanda is kicking my you-know-what. amdump is failing because it's unable to write it's index files. Why? From the errors it looks like a permissions problem, but the directory is owned by amanda and right now I've got everything opened up to chmod 777. There error messages I'm getting look like: pip/users5 lev 0 FAILED [err create /home/amanda/DailySet1/index/pip/_users5/20020919_0.gz.tmp: Permission denied] This is amanda 2.4.2p2 running on Red Hat 7.3.94 (null/RH8 beta). OK, I'm still doing something simple and stupid wrong. Any clues what that might be? Thanks, Caity
Help compile tapetype.c
Hey guys, I need help on compiling tapetype.c I found out that I can't just use the defined tapetype in amanda.conf. It works but the size will be small. I found out from dmesg about my tape: sa0: HP C1533A A708 Removable Sequential Access SCSI-2 device Then searched google with search pattern HP C1533A tapetype. I found this link, http://amanda.sourceforge.net/fom-serve/cache/72.html. I also learned from that link that there is a program called tapetype. I search my source and found tapetype.c but I am having problems compiling it. FYI, my machine is on FreeBSD 4.6 STABLE. Thanks in advance. Ronneil
Re: Weird permission problem running amdump
On Thursday 19 September 2002 17:15, Caitlyn M. Martin wrote: Hi, everyone, OK, I admit it. amanda is kicking my you-know-what. amdump is failing because it's unable to write it's index files. Why? From the errors it looks like a permissions problem, but the directory is owned by amanda and right now I've got everything opened up to chmod 777. There error messages I'm getting look like: pip/users5 lev 0 FAILED [err create /home/amanda/DailySet1/index/pip/_users5/20020919_0.gz.tmp: Permission denied] This is amanda 2.4.2p2 running on Red Hat 7.3.94 (null/RH8 beta). OK, I'm still doing something simple and stupid wrong. Any clues what that might be? Thanks, Caity The only thing that comes to mind quickly is probably related to the question/statement you do have a user amanda, who is a member of group disk, don't you? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Help compile tapetype.c
On Thursday 19 September 2002 21:52, Neil wrote: Hey guys, I need help on compiling tapetype.c I found out that I can't just use the defined tapetype in amanda.conf. It works but the size will be small. I found out from dmesg about my tape: sa0: HP C1533A A708 Removable Sequential Access SCSI-2 device Then searched google with search pattern HP C1533A tapetype. I found this link, http://amanda.sourceforge.net/fom-serve/cache/72.html. I also learned from that link that there is a program called tapetype. I search my source and found tapetype.c but I am having problems compiling it. FYI, my machine is on FreeBSD 4.6 STABLE. Thanks in advance. Ronneil Are you saying that when you type make tapetype while cd'd to the directory that tapetype.c is in, that it doesn't build a tapetype executable in that directory? If thats the case, you may not have a complete development install. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Help compile tapetype.c
Gene Heskett writes: Are you saying that when you type make tapetype while cd'd to the directory that tapetype.c is in, that it doesn't build a tapetype executable in that directory? If thats the case, you may not have a complete development install. Yup, exactly. What should I do then? Thanks. I apologize since my information was very few. Neil
Re: Help compile tapetype.c
On Friday 20 September 2002 00:54, Neil wrote: Gene Heskett writes: Are you saying that when you type make tapetype while cd'd to the directory that tapetype.c is in, that it doesn't build a tapetype executable in that directory? If thats the case, you may not have a complete development install. Yup, exactly. What should I do then? Install the development stuff? Thanks. I apologize since my information was very few. Neil -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Help compile tapetype.c
I have downloaded from sourceforge. I tried make tapetype in tape-src direcoty. This is what I got. # make tapetype cc -O -pipe tapetype.c -o tapetype In file included from /usr/local/src-backup/cvs/amanda/common-src/amanda.h:219, from tapetype.c:32: /usr/include/netinet/in.h:233: syntax error before `in_addr_t' /usr/include/netinet/in.h:285: syntax error before `u_char' In file included from /usr/include/netinet/in.h:467, from /usr/local/src-backup/cvs/amanda/common-src/amanda.h:219, from tapetype.c:32: /usr/include/netinet6/in6.h:122: syntax error before `u_int8_t' /usr/include/netinet6/in6.h:144: syntax error before `u_int8_t' /usr/include/netinet6/in6.h:149: syntax error before `u_int32_t' /usr/include/netinet6/in6.h:612: syntax error before `*' /usr/include/netinet6/in6.h:614: syntax error before `*' /usr/include/netinet6/in6.h:614: warning: data definition has no type or storage class /usr/include/netinet6/in6.h:615: syntax error before `u_int8_t' /usr/include/netinet6/in6.h:616: syntax error before `u_int8_t' /usr/include/netinet6/in6.h:631: syntax error before `u_int8_t' /usr/include/netinet6/in6.h:636: syntax error before `u_int8_t' /usr/include/netinet6/in6.h:638: syntax error before `u_int8_t' tapetype.c: In function `main': tapetype.c:226: warning: assignment makes pointer from integer without a cast tapetype.c:233: warning: assignment makes pointer from integer without a cast tapetype.c:283: `optind' undeclared (first use in this function) tapetype.c:283: (Each undeclared identifier is reported only once tapetype.c:283: for each function it appears in.) tapetype.c:288: `O_RDWR' undeclared (first use in this function) *** Error code 1 Stop in /usr/local/src-backup/cvs/amanda/tape-src.
