amlabel: not an amanda tape ???
Please, ANY ideas ??? amanda is version 2.5.1p1-2.1 , running on debian: # uname -a Linux erda 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 GNU/Linux Trying to setup a VXA-2 manual load tape drive with amanda. Same tape that I used earlier today with amtapetype, and successfully got a tapetype definition. Now, I want to label this same tape, and perform the first backup. # sudo -u backup amlabel -f DailySet1 backup.001 rewinding, reading label, not an amanda tape (Invalid argument) rewinding, writing label backup.001, checking label amlabel: not an amanda tape (Invalid argument) What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: amlabel: not an amanda tape ??? [ SOLVED ]
[ [ [ Anybody else seeing this?
amanda-users@amanda.org:
204.127.192.17 does not like recipient.
Remote host said: 550 [PERMFAIL] destination not valid within DNS
Giving up on 204.127.192.17. ] ] ]
Eureka!
# sudo mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x81 (DLT 15GB compressed).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
Changed /etc/stinit.def:
manufacturer=EXABYTE model = VXA-2 {
auto-lock
can-bsr
can-partitions
mode1 blocksize=32768 compression=0
}
Now:
# sudo mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=1, partition=0.
Tape block size 32768 bytes. Density code 0x81 (DLT 15GB compressed).
Soft error count since last status=0
General status bits on (101):
ONLINE IM_REP_EN
And:
# sudo -u backup amlabel -f DailySet1 backup.001
rewinding, reading label backup.001, tape is active
rewinding, writing label backup.001, checking label, done.
* Stefan G. Weichinger [EMAIL PROTECTED] [2007:08:01:14:32:04+0200] scribed:
Michael D Schleif schrieb:
Please, ANY ideas ???
amanda is version 2.5.1p1-2.1 , running on debian:
# uname -a
Linux erda 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64
GNU/Linux
Trying to setup a VXA-2 manual load tape drive with amanda.
Same tape that I used earlier today with amtapetype, and successfully
got a tapetype definition.
Now, I want to label this same tape, and perform the first backup.
# sudo -u backup amlabel -f DailySet1 backup.001
rewinding, reading label, not an amanda tape (Invalid argument)
rewinding, writing label backup.001, checking label
amlabel: not an amanda tape (Invalid argument)
What do you think?
(I thought: Should I reply or not? ;-) )
What's the definition of labelstr in your amanda.conf?
Your label does not fit that definition.
Stefan
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
amlabel: amlabel: not an amanda tape ???
amanda is version 2.5.1p1-2.1 , running on debian: # uname -a Linux erda 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 GNU/Linux Trying to setup a VXA-2 manual load tape drive with amanda. Same tape that I used earlier today with amtapetype, and successfully got a tapetype definition. Now, I want to label this same tape, and perform the first backup. # sudo -u backup amlabel -f DailySet1 backup.001 rewinding, reading label, not an amanda tape (Invalid argument) rewinding, writing label backup.001, checking label amlabel: not an amanda tape (Invalid argument) What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Problems using amanda to backup SMB shares
* Jon LaBadie [EMAIL PROTECTED] [2006:07:12:17:49:06-0400] scribed:
On Wed, Jul 12, 2006 at 09:31:09AM -0500, Michael D Schleif wrote:
* Jon LaBadie [EMAIL PROTECTED] [2006:07:12:00:09:07-0400] scribed:
snip /
When asked to, and if run by root, they record the date and
time and level of the dumps in a file /etc/dumpdates. This
file then can be used by dump in the future to decide what
needs backing up at various dump levels.
Tar does not have this built-in, so amanda mimics it in
/etc/amandates.
My point is, on _my_ amanda server, that files does NOT exist:
# sudo ls /etc/ama*
Password:
/etc/amandahosts /etc/amandapass
/etc/amanda:
DailySet1 crontab.amanda
What am I missing?
On each client that is using tar for dumping you need
/etc/amandadates, owned by client's amandauser/group,
rw by usergroup
If your server is also a client, then you need that file.
My point is that I do NOT have any /etc/amandates on server, NOR
clients. Although, Olivier Nicole states that I can simply create my
own, and amanda will use it; I remain unclear about this file, because I
do NOT find it documented anywhere ?!?!
amandahosts should be .amandahosts and it should not
be in /etc, but in the home directory of amandauser.
Well, Debian uses /etc/amandahosts on server and clients:
# dpkg -S /etc/amandahosts
amanda-common: /etc/amandahosts
BTW in your line:
# sudo ls /etc/ama*
Do you really need to sudo to execute ls on the /etc dir?
Particularly if you are already running as root ('# ' prompt).
Actually, I am NOT root; and I have a more complex prompt, which I edit
to simplify my posts:
[EMAIL PROTECTED]:~
# sudo ls -al /etc/amanda*
-rw--- 1 backup backup 182 Oct 8 2005 /etc/amandahosts
-rw--- 1 backup backup 455 Jul 29 2004 /etc/amandapass
/etc/amanda:
total 12
drwxrwx--- 3 backup backup 1024 May 27 11:36 .
drwxr-xr-x 149 root root 7168 Jul 13 03:11 ..
drwxrwx--- 3 backup backup 3072 Jul 13 05:49 DailySet1
-rw-rw 1 backup backup 490 Nov 2 2003 crontab.amanda
Thank you, for your participation in these issues ...
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
Re: Problems using amanda to backup SMB shares
* Jon LaBadie [EMAIL PROTECTED] [2006:07:12:00:09:07-0400] scribed: snip / When asked to, and if run by root, they record the date and time and level of the dumps in a file /etc/dumpdates. This file then can be used by dump in the future to decide what needs backing up at various dump levels. Tar does not have this built-in, so amanda mimics it in /etc/amandates. My point is, on _my_ amanda server, that files does NOT exist: # sudo ls /etc/ama* Password: /etc/amandahosts /etc/amandapass /etc/amanda: DailySet1 crontab.amanda What am I missing? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Problems using amanda to backup SMB shares
* Jon LaBadie [EMAIL PROTECTED] [2006:07:11:11:59:30-0400] scribed: On Tue, Jul 11, 2006 at 11:30:23AM -0400, Nathan Weston wrote: snip / As for the second problem, I don't see anything in the .debug files that gives me a clue. The permissions for /etc/amandates look like this: -rw-r- 1 amandabackup disk 0 Jul 10 17:20 /etc/amandates My pre-built amanda server does use 'amandabackup' and 'disk' as the amanda user and group. Make sure your's does too and not something like amanda/wheel or some other combo. My amandates file's permissions are 664, not 640. If the owner is correct, maybe amanda expects to write to the file via group, not owner permissions. OK, I give up! What is /etc/amandates? I am running 2.5.0p2 ; and I have not found any reference to this file ; -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: /tmp/amanda needs 64KB, only has -2147483648KB available
* Rémi Demarthe [EMAIL PROTECTED] [2006:06:15:15:07:51+0200] scribed: Hello all, When I run amcheck, I've got this result : ERROR: services4.obs-besancon.fr: [dir /tmp/amanda needs 64KB, only has -2147483648KB available.] ERROR: services4.obs-besancon.fr: [dir /var/log/amanda needs 64KB, only has -2147483648KB available.] ERROR: services4.obs-besancon.fr: [dir /var/lib needs 64KB, only has -2147483648KB available.] ERROR: services2.obs-besancon.fr: [dir /tmp/amanda needs 64KB, only has -2147483648KB available.] ERROR: services2.obs-besancon.fr: [dir /var/log/amanda needs 64KB, only has -2147483648KB available.] ERROR: services2.obs-besancon.fr: [dir /var/lib needs 64KB, only has -2147483648KB available.] What is the OS and version for services4.obs-besancon.fr? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: missing result ... in ... response ???
* Paul Bijnens [EMAIL PROTECTED] [2006:05:29:14:13:00+0200] scribed: snip / Jean-Louis created a patch for 2.5.0, which break at 64K (just as 2.4.x), which fixes your problem. Yes. As I stated earlier, it is better for me to use debian packages; rather than attempting to maintain personal compilations ... It fixes it until you hit the 64Kbyte limit, at which time, 2.5.1 or 2.5.2 will have removed that limit, we hope. OK. Just to clarify, do I understand you correctly, that amanda developers are working on solution to this problem, and some expectation has been set (by them?) that these subsequent dot releases should correct this problem? If so, I shall be patient -- and wait ; Thank you, for your contributions to this problem ... -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: missing result ... in ... response ???
* On 2006:05:25:08:25:07-0500 I, Michael D Schleif [EMAIL PROTECTED], scribed: Something has changed in amanda. I have been running amanda on this lan for several years. For the most part, DLE's have been constant for at least six months. I have six linux servers, all running debian. Regarding amanda-server, my records show that I upgraded amanda to version: 2.4.5 on 16JUN05 Everything was backing up, and restoring, to my satisfaction, until last week. At that time, two servers (brono jord) were terribly old, regarding kernel and debian os. So, I upgraded via aptitude, which also upgraded amanda-client to version: 2.5.0 Since that time, many -- but, NOT all -- DLE's on brono and jord are FAIL'ing, e.g.: brono /var lev 0 FAILED [missing result for /var in brono response] jord /var lev 0 FAILED [missing result for /var in jord response] Yes, both of these servers have many DLE's; but, as stated above, this HAS been working without incident at the older version. Numbers of DLE's: brono 137 jord 219 snip / Bdale Garbee published to debian repository version 2.5.0p2. I have tried this on brono and jord, and this does NOT resolve the problem. I now have this on ALL of my boxen, except brono and jord, which I have downgraded to 2.4.4p3-3. Last night was my first completely successful backup in more than one week! I have received several private emails explaining the situation. I do understand those issues. However, amanda DOES succeed in my situation in versions _prior_ to v2.5.x -- and it FAILS in ALL v2.5.x ; This I do NOT understand. What am I missing? How will I know when a new version corrects this problem? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
missing result ... in ... response ???
Something has changed in amanda. I have been running amanda on this lan for several years. For the most part, DLE's have been constant for at least six months. I have six linux servers, all running debian. Regarding amanda-server, my records show that I upgraded amanda to version: 2.4.5 on 16JUN05 Everything was backing up, and restoring, to my satisfaction, until last week. At that time, two servers (brono jord) were terribly old, regarding kernel and debian os. So, I upgraded via aptitude, which also upgraded amanda-client to version: 2.5.0 Since that time, many -- but, NOT all -- DLE's on brono and jord are FAIL'ing, e.g.: brono /var lev 0 FAILED [missing result for /var in brono response] jord /var lev 0 FAILED [missing result for /var in jord response] Yes, both of these servers have many DLE's; but, as stated above, this HAS been working without incident at the older version. Numbers of DLE's: brono 137 jord 219 At first, I thought that this maybe conflict between amanda-server and amanda-client versions; so, I upgraded amanda-server: 2.5.0 on 23MAY06 NO difference. So, I searched these archives, and I googled. All I found was this URL: http://wiki.zmanda.com/index.php/Amdump:_results_missing amanda.conf has never had `etimeout' configured. Yesterday, I set it: etimeout 600 NO difference. Remember, this exact same configuration has been working WITHOUT incident at older version for eleven months! This is NOT a firewall issue, since this is only for my internal lan. Regarding maximum udp datagram size: net.inet.udp.maxdgram=63535 Apparently, sysctl on linux/debian does NOT support this. I have pinged debian-user on this issue; but, there has been NO response. I do NOT know what the current, default size is; nor do I know how to change it. I prefer NOT to combine DLE's; which will pose other challenges, not the least of which is DLE larger than tape. These DLE's are very dynamic. I cannot predict when a particular DLE will contain enormous data; and the nature of this dynamic data is already compressed ... What am I missing? This used to work; then, it b0rk; and the only change was a newer amanda version. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: missing result ... in ... response ???
* Jean-Louis Martineau [EMAIL PROTECTED] [2006:05:25:10:16:56-0400] scribed: Michael, If the problem is that you have too many DLE for a udp packet, try the attached patch which will double the size of the packet. Thank you, for your participation in this matter. Yes, I can get this source, and compile it myself. However, I have two issues with that solution: [1] Did this _change_ between v2.4.5 and v2.5.x? If so, why? If so, at which version? Perhaps, I can down-grade? [2] One reason for using debian is, package management is so easy. Managing one, or dozens, or hundreds of personally compiled programs is a mess that I prefer to avoid. what do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: DDS-3 tapetype ???
OK, here is my solution that allows full tape length for my backups.
Notice that I am using amtapetype only as an effective way to illustrate
both my problem and the solution.
This demonstrates using the OS and mt to turn tape drive hardware
compression ON:
* Michael D Schleif [EMAIL PROTECTED] [2005:06:17:10:04:59-0500] scribed:
snip /
# sudo /bin/mt -f /dev/nst0 compression 1
# sudo /bin/mt -f /dev/nst0 defcompression 1
# sudo -u backup amtapetype -c -f /dev/nst0 -o
Writing 1024 Mbyte compresseable data: 384 sec
Writing 1024 Mbyte uncompresseable data: 1318 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 1024 Mbyte: 2636 sec = 0 h 43 min
This demonstrates using the OS and mt to turn tape drive hardware
compression OFF:
# sudo /bin/mt -f /dev/nst0 compression 0
# sudo /bin/mt -f /dev/nst0 defcompression -1
* Michael D Schleif [EMAIL PROTECTED] [2005:06:16:23:59:28-0500] scribed:
snip /
# time sudo -u backup amtapetype -e 12g -f /dev/nst0 -o
Writing 32 Mbyte compresseable data: 37 sec
Writing 32 Mbyte uncompresseable data: 35 sec
Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min
wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write)
wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write)
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 9522 mbytes
filemark 0 kbytes
speed 908 kps
}
real364m39.451s
user0m2.724s
sys 0m28.719s
Next, the Compaq/Sony SDT-9000 a physical jumper labeled `disable dc'.
To this point, this jumper was OPEN. Now I CLOSED this jumper.
Interestingly, now when I used the OS and mt to set both compression and
defcompression to 1, the following test _never_ returns an initial
estimate:
# sudo -u backup amtapetype -c -f /dev/nst0 -o
Finally, with the jumper CLOSED, compression 0 and defcompression -1, I
get the following:
# time sudo -u backup amtapetype -e 12g -f /dev/nst0 -o
Writing 128 Mbyte compresseable data: 114 sec
Writing 128 Mbyte uncompresseable data: 114 sec
Estimated time to write 2 * 12288 Mbyte: 21888 sec = 6 h 4 min
wrote 365676 32Kb blocks in 93 files in 11010 seconds (short write)
wrote 365676 32Kb blocks in 186 files in 10484 seconds (short write)
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 11427 mbytes
filemark 0 kbytes
speed 1089 kps
}
real373m59.100s
user0m2.907s
sys 0m30.466s
Most importantly, last night's backup used nearly the whole 12 GB of tape!
Thank you, all of you, for your contributions to this challenge.
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
Re: DDS-3 tapetype ???
* Paul Bijnens [EMAIL PROTECTED] [2005:06:17:09:51:48+0200] scribed:
Michael D Schleif wrote:
Since the tape drive change, I have wondered why I didn't seem to be
getting all the data on some tapes. Clearly, with Amanda, some days it
just doesn't want to send a full 12GB to tape; but, mostly, I have been
seeing 9GB going to tape, and balance sitting in holdingdisk.
Today, I did this:
# time sudo -u backup amtapetype -e 12g -f /dev/nst0 -o
Writing 32 Mbyte compresseable data: 37 sec
Writing 32 Mbyte uncompresseable data: 35 sec
I'm pretty sure that your hardware compression is indeed off.
Otherwise you would have a very large speed difference in writing
uncompressed or compressed data, that is tested here. It would
be twice or three times as fast, instead of only 2 seconds difference.
Yes, indeed. I also tried this:
# sudo /bin/mt -f /dev/nst0 compression 1
# sudo /bin/mt -f /dev/nst0 defcompression 1
# sudo -u backup amtapetype -c -f /dev/nst0 -o
Writing 1024 Mbyte compresseable data: 384 sec
Writing 1024 Mbyte uncompresseable data: 1318 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 1024 Mbyte: 2636 sec = 0 h 43 min
Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min
wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write)
wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write)
These two lines are actually a little strange. I would have expected
that the second pass wrote a little bit less then the first pass (and
the difference is the space taken up by the additional filemarks).
But you seem to write more in the second pass. Even 400 Mbyte.
In previous version of amtapetype, this would be reported as a negative
filemark size of -4603 Mbyte (the granularity of measuring is 32K).
In lieu of else to chase, how can this happen? Is this strangeness a
bad thing? How can I find the root cause?
What actually happened is that in the first pass, there was a hard write
error, interpreted as an end-of-tape.
This is a symptom of an almost bad tape or tapedrive or dusty heads.
Some OS's report an excessive soft-error rate in the kernel messages.
Do you find anything like that in /var/log/messages?
No, there are no errors under /var/log/ for the tape drive. The tape I
am using for this was brand new, unsealed yesterday, solely for this
test. It is a hp dds-3 c5708a.
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
I'm pretty sure that your hardware compression is indeed off.
Otherwise you would have a very large speed difference in writing
uncompressed or compressed data, that is tested here.
Yes, in recent versions of amtapetype, it actually puts it in the
comment, as above.
length 9522 mbytes
filemark 0 kbytes
speed 908 kps
}
I would be more willing to consider hardware problems on my side, if it
weren't for several extenuating circumstances:
[1] Amanda FAQ-O-Matic shows other people ending with same results; but,
I have not found documented resolution.
[2] All of my tapes in circulation have been reporting short lengths in
the `Tape Size (meg)' report field. Prior to replacing the tape
drive, these same tapes were better filled, according to these
reports.
[3] I clean the tape drive once (1x) per week. I do not notice any
unusual lights/LED's while the tape drive is working.
[4] I have successfully restored from these tapes, and using this same
tape drive, on several occasions.
Just for clarification, the brand on the tape drive is Compaq; but, the
only SDT-9000 I find on Google is the Sony brand; therefore, I assume
that Compaq is private branding the Sony drives.
What else can I do?
What do you think?
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
DDS-3 tapetype ???
Earlier this year, my HP DAT tape drive had problems, and I replaced it
with a Compaq/Sony SDT-9000. Mostly, I am still using the same DDS-3
tapes that I was using, and retired some and added some. My old records
show that I was getting nearly the full 12GB uncompressed tape length.
Since the tape drive change, I have wondered why I didn't seem to be
getting all the data on some tapes. Clearly, with Amanda, some days it
just doesn't want to send a full 12GB to tape; but, mostly, I have been
seeing 9GB going to tape, and balance sitting in holdingdisk.
Today, I did this:
# time sudo -u backup amtapetype -e 12g -f /dev/nst0 -o
Writing 32 Mbyte compresseable data: 37 sec
Writing 32 Mbyte uncompresseable data: 35 sec
Estimated time to write 2 * 12288 Mbyte: 26880 sec = 7 h 28 min
wrote 298832 32Kb blocks in 76 files in 10632 seconds (short write)
wrote 310628 32Kb blocks in 158 files in 10840 seconds (short write)
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 9522 mbytes
filemark 0 kbytes
speed 908 kps
}
real364m39.451s
user0m2.724s
sys 0m28.719s
What is going on here?
How can I get a full 12GB tape length?
What do you think?
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
AS/400 backup ???
Anybody using Amanda to backup an AS/400? Pointers cheerfully accepted ; TIA -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Dump Time Run Time ???
I am certain that this is a misunderstanding on my part ;
How can Dump Time be *GREATER THAN* Run Time?
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:17
Run Time (hrs:min) 9:40
Dump Time (hrs:min) 12:12 12:10 0:02
Clearly, this backup did *NOT* take anywhere near twelve (12) hours.
So, what is that Dump Time value?
What do you think?
P.S., Notice the Estimate Time (re: Speed up 400GB backup? thread).
This successful backup is for 65GB, across (17) DLE's, including a
Netware server over ncpfs, and a couple of windoze over samba.
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
Re: disklist and whitespaces
* Andrea Borgia [EMAIL PROTECTED] [2004:07:15:18:48:50+0200] scribed: Hello. On one host I would like to backup the Windows Documents and Settings directory from Linux, but it appears Amanda is bitching about those embedded whitespaces. I've tried both escaping them and quoting the whole path (as above), but still no luck. Has anyone dealt with a similar problem before? Apart from simply ignoring such paths, how should I add them to the disklist? Assuming that you are backing up over Samba, what I do is share Documents and Settings as something else (e.g., docs), which alleviates this problem. hth -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
GNUTAR, mount points symbolic links ???
Does Amanda/GNUTAR _follow_ all mount points and symbolic links in a DLE? Everytime that I setup Amanda clients, I get confused on these issues. If this is covered in the FAQ-O-Matic, then I do not see it. If it has been covered on the mailing list countless times, then my searches are too lame. Hopefully, this post, including this subject line, will make this easier to find for those who come after ; If I am right, by default, Amanda/GNUTAR _does_ follow follow mount points contained within a DLE, but does _not_ follow symbolic links. This makes a difference regarding deploying exclude files. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Best Practices: small number of tapes ???
OK, we have a Quantum SuperDLT1 tape drive, and an Overland LXB autoloader, with ten (10) slot magazine and barcode reader. One slot is the cleaning tape, which is controlled by the autoloader, and not by the Amanda changer. Backups are to be performed seven (7) days per week. Amanda is backing up as expected, and tapes are being selected and loaded without a hitch. This is a recent setup, and DLE's are being configured and added every couple of days. So far, everything can fit on one tape, even assuming level 0 on each DLE. As this environment grows, that will not be the case. Normally, Amanda's logic loves a large number of tapes. My office LAN, manually changed, uses eighteen (18) DDS3 tapes. I have followed this setup carefully for more than one year, and even as I add DLE's, Amanda manages to get everything necessary on one tape per backup. All is good. With this current setup, nine (9) usable tapes, I wonder how best to configure Amanda? Yes, we can manually swap out magazines as necessary; but, we prefer that this site run as automagically as possible. To wit, one magazine and nine tapes -- period. How do you setup similar environments? What happens if a tape is, of a sudden, bad when you need to restore? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Best Practices: small number of tapes ???
* Gene Heskett [EMAIL PROTECTED] [2004:07:10:17:45:42-0400] scribed: On Saturday 10 July 2004 11:46, Michael D Schleif wrote: snip / With this current setup, nine (9) usable tapes, I wonder how best to configure Amanda? Yes, we can manually swap out magazines as necessary; but, we prefer that this site run as automagically as possible. To wit, one magazine and nine tapes -- period. How do you setup similar environments? What happens if a tape is, of a sudden, bad when you need to restore? What do you think? If it was me, I'd probably get another magazine, put 7 tapes and a cleaner in each, and have cron send you a reminder email to change the magazine before you do anything else monday mornings. That would take a dumpcycle=7, runspercycle=7, tapecycle=14. Or goto dumpcycle=4,runspercycle=4,and tapecycle=9 and run it every night and wear those tapes out in a hurry. But I'm not you, and atm don't even have amanda running, I've gotta see if I can make it use dvd-+-rw's one of these days. My last DDS2 changer's head died a week or so back. Yes, I know that this is the ideal solution. However, this is an office with naive computer users, and a bunch of servers. Experience has taught me not to rely too heavily on non-technical people to change tapes ; It is more important that we get a good backup _every_ night, than to have somebody forget to change the magazine, and go without backups for several days ; Somebody must have already dealt with this scenario, and have a time worn solution. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
crossed signals ???
Can somebody please explain these errors: [compress got signal 11, /usr/bin/smbclient got signal 13] [compress got signal 11, /bin/tar got signal 13] [index got signal 11, /usr/bin/smbclient got signal 13] One of my Debian clients, running kernel 2.6.2, has recently developed these maladies. Fortunately, most of its DLE's backup successfully, and these maladies are intermittent. Nevertheless, when a DLE presents one of these errors, all subsequent DLE's also FAIL ; What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
superdlt1: out of tape ???
We are having one bear of a time getting Amanda to work properly in this
environment.
# uname -a
Linux pluto 2.6.2-1-686-smp #1 SMP Thu Feb 19 23:32:17 EST 2004 i686 GNU/Linux
(brought to you by Amanda version 2.4.4p2)
define tapetype SuperDLT1 {
comment QUANTUM SuperDLT1
length 11 mbytes
filemark 0 kbytes
speed 9100 kps
}
These dumps were to tape PSSI.001.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: PSSI.002.
FAILURE AND STRANGE DUMP SUMMARY:
pluto /home/irv/DATA lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:15
Run Time (hrs:min) 1:03
Dump Time (hrs:min)0:32 0:25 0:07
Output Size (meg)3707.9 3687.9 19.9
Original Size (meg) 3707.9 3687.9 20.0
Avg Compressed Size (%) 3.3-- 3.3 (level:#disks ...)
Filesystems Dumped5 1 4 (1:4)
Avg Dump Rate (k/s) 1978.8 2527.8 48.0
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg)19.90.0 19.9
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 4 0 4 (1:4)
Avg Tp Write Rate (k/s) 4250.2-- 4250.2
USAGE BY TAPE:
Label Time Size %Nb
PSSI.001 0:00 19.90.0 4
^L
NOTES:
planner: tapecycle (7) = runspercycle (28)
planner: Full dump of pluto:/home/irv/DATA promoted from 28 days ahead.
taper: tape PSSI.001 kb 423136 fm 5 writing file: Input/output error
driver: going into degraded mode because of tape error.
^L
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SSKB/s
MMM:SSKB/s
---
--
pluto/home/irv/DATA 0 3776460 3776460 -- 24:54 2527.8
FAILED --
pluto/home/irv/SYS11021010210 --1:5886.3
0:01 7440.1
pluto/home/irv/_ADMIN 1 302 6.7 0:01 1.9
0:01 2.0
pluto/home/jen/SYS11017010170 --5:0533.3
0:01 7109.4
pluto/home/jen/_ADMIN 1 302 6.7 0:01 1.5
0:01 2.0
We have several Netware volumes mounted to this box via ncp, which are
then to be backed up to this Overland SuperDLT1 system.
There are other problems with amverify, and when we try to use more
DLE's; but, I'm hoping to solve this situation first, then move on to
the others.
What do you think?
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
backup DMZ host ???
My client has a proxy-arp DMZ, on which resides a host that I want to backup to a NAT'ed, private network Amanda server. I keep getting this error: # sudo -u backup amcheck DailySet1 -cltw Amanda Tape Server Host Check . . . ERROR: don.platinumaire.net: [host bluetrout.PlatinumAire.net: port 61906 not secure] Notice, don is the DMZ host, and bluetrout is the router. What am I missing? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: backup DMZ host ???
Stefan = O, I forgot about /tmp/amanda/ on the client ; From the client (don): amandad: time 0.004: sending REP packet: Amanda 2.4 REP HANDLE 000-E08F0608 SEQ 1083000883 ERROR [host bluetrout.PlatinumAire.net: port 62170 not secure] * Stefan G. Weichinger [EMAIL PROTECTED] [2004:04:26:19:53:39+0200] scribed: Hi, Michael, on Montag, 26. April 2004 at 18:27 you wrote to amanda-users: MDS ERROR: don.platinumaire.net: [host MDS bluetrout.PlatinumAire.net: port 61906 not secure] MDS Notice, don is the DMZ host, and bluetrout is the router. MDS What am I missing? Is that port open? What is listening there? Can you close it? Which port(s)? Which side, client or server? And did you compile BOTH client AND server with the port-options? Yes, both server and client are compiled identically with regard to ports. FWIW, I am on Debian, and we are using DEB's showing following version: 2.4.4p2-2 -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: kernels v2.6.x vs. /dev/nst0 ???
* Joshua Baker-LePain [EMAIL PROTECTED] [2004:03:08:08:18:07-0500] scribed: On Sun, 7 Mar 2004 at 11:10pm, Michael D Schleif wrote Amanda 2.4.4p1 Debian Linux I finally took the plunge yesterday, and upgraded my last system to kernel 2.6.3. Unfortunately, this is my amanda backup server, and under this kernel it no longer communicates with /dev/nst0: # sudo mt -f /dev/nst0 offline mt: No such device. Cannot open '/dev/nst0'. In addition to making sure st is available, doesn't 2.6 also have a device mapper (like devfs, but not) available? Did you compile that in, which would have the result of putting /dev/nst0 somewhere else (like /dev/tape/0 or something like that)? Yes, that's what I'm guessing. I had to add two (2) modules to get my mouse working under X11. So far, I haven't found reference to anything similar for st . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: kernels v2.6.x vs. /dev/nst0 ???
* Michael D Schleif [EMAIL PROTECTED] [2004:03:07:23:10:40-0600] scribed: snip / Unfortunately, this is my amanda backup server, and under this kernel it no longer communicates with /dev/nst0: # sudo mt -f /dev/nst0 offline mt: No such device. Cannot open '/dev/nst0'. Everything else appears to work as expected. I didn't notice this tape problem until this morning, I saw the backup was stuck on holdingdisk. Running following results in `0' tape devices found: # sudo /etc/init.d/mt-st modload Regardless of kernel, I see this: # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 05 Lun: 00 Vendor: HP Model: C1537A Rev: L812 Type: Sequential-AccessANSI SCSI revision: 02 . . . Now, after reboot back into 2.4.25, /dev/nst0 is working fine, and I am flushing last night's backup to tape as I compose this. snip / * Stefan G. Weichinger [EMAIL PROTECTED] [2004:03:08:10:12:46+0100] scribed: Hi, Michael, on Montag, 08. März 2004 at 06:10 you wrote to amanda-users: MDS Amanda 2.4.4p1 MDS Debian Linux MDS I finally took the plunge yesterday, and upgraded my last system to MDS kernel 2.6.3. MDS What do you think? Just for the records: I compiled and ran various versions and snapshots of AMANDA on all Linux-kernels since 2.5.79 on my testbox. No problems. Right now I have 2.6.4-rc2 up, with AMANDA 2.4.5b1 on it, running fine. As Frank said, it is likely that you miss a module. How did you configure 2.6.3? A good start would be to take the config of your 2.4.25, make oldconfig and start testing with this. I am using the stock Debian kernel: kernel-image-2.6.3-1-686 From config-2.6.3-1-686: # # SCSI device support # CONFIG_SCSI=m CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=m CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=m # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=m # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # CONFIG_SCSI_MULTI_LUN=y # CONFIG_SCSI_REPORT_LUNS is not set CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y From config-2.4.25-1-686: # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=m CONFIG_SD_EXTRA_DEVS=40 CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=m # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_SR_EXTRA_DEVS=2 CONFIG_CHR_DEV_SCH=m CONFIG_CHR_DEV_SG=m # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_DEBUG_QUEUES is not set CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y What am I missing? After that you can still try to add/remove features from you kernel. Can you access your 2.6.3-tape-device via mt or create archives on it with tar? That's the point, I cannot (see above). -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: kernels v2.6.x vs. /dev/nst0 ???
* Stefan G. Weichinger [EMAIL PROTECTED] [2004:03:08:16:03:45+0100] scribed: Hi, Michael, on Montag, 08. März 2004 at 15:48 you wrote to amanda-users: MDS I am using the stock Debian kernel: MDSkernel-image-2.6.3-1-686 MDS From config-2.6.3-1-686: MDS# MDS# SCSI device support MDS# MDSCONFIG_SCSI=m MDSCONFIG_SCSI_PROC_FS=y MDS# MDS# SCSI support type (disk, tape, CD-ROM) MDS# MDSCONFIG_BLK_DEV_SD=m MDSCONFIG_CHR_DEV_ST=m ... MDS What am I missing? Maybe you don't have the right modutils installed. The format of modules has changed with 2.6, so you need other tools for using and handling them. Are you able to do a modprobe scsi in your 2.6-environment? Do the commands modprobe, lsmod, rmmod work there? For the record, upgrading module-init-tools from 3.0-pre9-1 to 3.0-pre10-1 did the trick for me! I do not know why this worked, because the changelog indicates only some upstream release issue. Also, as a loadable module (regardless kernel 2.4.25 or 2.6.3), `st' is _not_ loaded (e.g., lsmod) until userland tries to use it. In my case, that is the `mt-st' package, which I have not changed in many weeks. Bottomline, I upgraded module-init-tools and rebooted, and now userland has no problems communicating with /dev/nst0. Thank you for your help. -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
kernels v2.6.x vs. /dev/nst0 ???
Amanda 2.4.4p1 Debian Linux I finally took the plunge yesterday, and upgraded my last system to kernel 2.6.3. Unfortunately, this is my amanda backup server, and under this kernel it no longer communicates with /dev/nst0: # sudo mt -f /dev/nst0 offline mt: No such device. Cannot open '/dev/nst0'. Everything else appears to work as expected. I didn't notice this tape problem until this morning, I saw the backup was stuck on holdingdisk. Running following results in `0' tape devices found: # sudo /etc/init.d/mt-st modload Regardless of kernel, I see this: # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 05 Lun: 00 Vendor: HP Model: C1537A Rev: L812 Type: Sequential-AccessANSI SCSI revision: 02 . . . Now, after reboot back into 2.4.25, /dev/nst0 is working fine, and I am flushing last night's backup to tape as I compose this. I have searched the archives and Google; but, the string `st' is very common, and I probably have not found the optimal search string ; What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Advice for setup large environment?
I have been successfully using Amanda for nearly a year on several small LAN's. Now, I want to setup Amanda in a larger network in a phased approach. First, notice that I will be using backup hardware such as I have setup and configured for Arcserve and BackupExec; but, not yet with Amanda. [1] Hardware SuperDLT 1 tape drive Overland Loader Xpress autoloader [2] Tapes and magazines Magazines hold ten (10) tapes One (1) cleaning tape per magazine Three (3) available magazines [3] Startup configuration Initially, one (1) magazine and seven (7) tapes [4] Future larger configuration Rotate all three (3) fully loaded magazines Amanda can put daily backups on one (1) tape Amanda must use all nine (9) tapes in a magazine *prior* to expecting another magazine I am comfortable with installing Amanda in this environment, as well as configurations such as holdingdisk, disklist, dumptypes, c. I am soliciting advice regarding areas such as these: [A] dumpcycle runspercycle runtapes tapecycle c. [B] How do I setup the autoloader? Yes, I know that this is a FAQ, and I will be RTFM this week. Are there any specific things that I ought to know/read, based on real life experiences of list members in similar environments? [C] Once we prove this in the pilot, then we will want to use a barcode reader, which may not be available during pilot. [D] How do I setup regular cleaning tape usage via Amanda? [E] I am concerned about tape sequence. We are starting with seven (7) tapes; but, will eventually move to twenty-seven (27). If the order/sequence of tapes is not perfect, then Amanda will expect tapes in another magazine prior to using all seven in the current magazine. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Can't open exclude file ???
This does *not* appear to be Gene's problem of several days ago.
Yesterday, I reconfigured some disk, and reconfigured amanda to work
with the disk changes.
For nearly one year, I have used the following as a top level dumptype,
from which all others inherit:
define dumptype global {
comment dat tapedrive, gnu tar
compress none
exclude list optional .amanda.excludes
holdingdisk yes
index yes
priority medium
program GNUTAR
record yes
}
Notice the `exclude list optional' line.
So, last night, I added the second line to the following:
bragi.private.network / server-compress
bragi.private.network /home/mds/mail important-fast-compress
bragi.private.network /home/mds/tmp medium-fast-compress
bragi.private.network /usr important-fast-compress
Now, since this addition, I get this:
# sudo -u backup amcheck DailySet1 -cltw
Amanda Tape Server Host Check
-
Holding disk /space: 3704388 KB disk space available, using 3704388 KB
Tape backup.015 is writable
Tape backup.015 label ok
Server check took 39.313 seconds
Amanda Backup Client Hosts Check
ERROR: bragi.private.network: [Can't open exclude file
'/usr/local/home/mds/mail/.amanda.excludes': Permission denied]
Client check: 2 hosts checked in 7.134 seconds, 1 problem found
(brought to you by Amanda 2.4.4p1)
Notice the _working_ exclude under /usr:
# ls -l /usr/local/home/mds/mail/.amanda.excludes
-rw---1 backup backup 59 Jan 28 01:00
/usr/local/home/mds/mail/.amanda.excludes
# ls -l /usr/.amanda.excludes
-rw---1 backup backup 23 Aug 4 09:33 /usr/.amanda.excludes
When I comment OUT the `exclude list optional' line from conf, then I
get *NO* amcheck errors -- which is what I did for last night's backup.
What is the problem here?
What is the solution to that problem?
What do you think?
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
Re: Can't open exclude file ???
* Jon LaBadie [EMAIL PROTECTED] [2004:01:28:10:28:28-0500] scribed: On Wed, Jan 28, 2004 at 09:07:34AM -0600, Michael D Schleif wrote: snip / Now, since this addition, I get this: # sudo -u backup amcheck DailySet1 -cltw Amanda Tape Server Host Check - Holding disk /space: 3704388 KB disk space available, using 3704388 KB Tape backup.015 is writable Tape backup.015 label ok Server check took 39.313 seconds Amanda Backup Client Hosts Check ERROR: bragi.private.network: [Can't open exclude file '/usr/local/home/mds/mail/.amanda.excludes': Permission denied] Client check: 2 hosts checked in 7.134 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) snip / Check the permissions on the mail directory, or possibly - but unlikely, the directories above it. IIRC, amcheck does not run with the same root permissions as amdump. Thus it may not be able to get to the excluce file during an amcheck. Ironically, I do _not_ need any exclude file for this DLE. Initially, I did not have any exclude file, and amcheck issued the _same_ error. Then, I touched an empty exclude file, resulting in the same error. For my original post, I included two temporary directories in the exclude file. Regarding perms: # ls -adl /usr drwxr-xr-x 16 root root 4096 Oct 6 14:15 /usr # ls -adl /usr/local/home drwxrwsr-x7 root staff4096 Jan 16 21:17 /usr/local/home # ls -adl /usr/local/home/mds drwxr-xr-x 44 mds mds 8192 Jan 28 09:07 /usr/local/home/mds # ls -adl /usr/local/home/mds/mail drwx-- 19 mds mds 4096 Jan 28 01:00 /usr/local/home/mds/mail Else? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Can't open exclude file ???
* Jon LaBadie [EMAIL PROTECTED] [2004:01:28:11:08:19-0500] scribed: On Wed, Jan 28, 2004 at 09:52:41AM -0600, Michael D Schleif wrote: snip / Ironically, I do _not_ need any exclude file for this DLE. Initially, I did not have any exclude file, and amcheck issued the _same_ error. Then, I touched an empty exclude file, resulting in the same error. For my original post, I included two temporary directories in the exclude file. Regarding perms: # ls -adl /usr drwxr-xr-x 16 root root 4096 Oct 6 14:15 /usr # ls -adl /usr/local/home drwxrwsr-x7 root staff4096 Jan 16 21:17 /usr/local/home # ls -adl /usr/local/home/mds drwxr-xr-x 44 mds mds 8192 Jan 28 09:07 /usr/local/home/mds # ls -adl /usr/local/home/mds/mail drwx-- 19 mds mds 4096 Jan 28 01:00 /usr/local/home/mds/mail ^^ When amcheck looks for the exclude file, unless it is running with root privleges or as mds, it will not be able to visit this directory. During the amcheck run your host is both server and client. When amcheck goes out to the client, it loses its root privleges and runs as the amanda user. For this one you may need to put the exclude file somewhere else the amanda user can visit and specify an absolute directory path to the file. OK, now it makes sense to me -- mostly. I have reviewed my permission requirements, and I can live with this: # ls -adl /usr/local/home/mds/mail drwxr-xr-x 19 mds mds 4096 Jan 28 10:29 /usr/local/home/mds/mail This allows amcheck to run _without_ errors, even _without_ /usr/local/home/mds/mail/.amanda.excludes , which is what I wanted. Nonetheless, I remain confused, since conf uses: exclude list optional .amanda.excludes So, even though it is `optional', amcheck *must* have permissions adequate to see whether or not the `optional' file exists? Would that condition impact the actual backup itself? Or, since it runs as superuser, it would have access to the exclude file, and everything would be OK? Am I getting closer to understanding this? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
howto determine tape position ???
At the end of an amanda dump, what is the optimal way to determine the location/position on that tape where the dump completed? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: howto determine tape position ???
* Jon LaBadie [EMAIL PROTECTED] [2004:01:13:12:30:56-0500] scribed: On Tue, Jan 13, 2004 at 10:17:18AM -0600, Michael D Schleif wrote: At the end of an amanda dump, what is the optimal way to determine the location/position on that tape where the dump completed? Not certain what your objective is, so I'm not certain in what units you might need the information. I am trying to track tape usage statistics over time. Do these do anything for you: my mt status command reports where the tape is positioned by tape file number and block number $ mt status HP DDS-3 4mm DAT loader tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 13 block no= 0 your amanda report shows the percent of the tape used and the number of bytes and files successfully written under the tape usage section USAGE BY TAPE: LabelTime Size %Nb DS1-01 0:432536.3 21.725 What does `Nb' mean? Is that the number of DLE's on tape? also in the amanda report is taper's report (under Notes:) of the ACTUAL number of bytes and files written (some may have failed due to an error at the end) NOTES: ... taper: tape DS1-01 kb 2598496 fm 25 [OK] In your example, what does `fm 25' mean? Perhaps, I can use numbers already calculated by amanda, rather than calculating what I want from mt. Thank you. -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Who is radicalmedia.com ???
Jon LaBadie [EMAIL PROTECTED] [2003:09:05:12:19:59-0400] scribed: On Fri, Sep 05, 2003 at 09:58:50AM -0500, Michael D Schleif wrote: Michael D Schleif [EMAIL PROTECTED] [2003:09:01:22:12:01-0500] scribed: And, why are they re-sending post-spamassassin'd spam, that they received from amanda mailing list, *BACK* through amanda mailing list? Who can stop this? A good choice would be the list member who is doing the resends, or his email administrator. snip / I do not know how you know who is that list member? I hate to chastise the wrong person. Nevertheless, look at this URL: http://www.helices.org/tmP/radicalmedia.com These are among the last TEN (10) instances of this lunacy !?!? Please, can somebody locate the appropriate person and *STOP* this lunacy? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: Who is radicalmedia.com ???
Michael D Schleif [EMAIL PROTECTED] [2003:09:01:22:12:01-0500] scribed: And, why are they re-sending post-spamassassin'd spam, that they received from amanda mailing list, *BACK* through amanda mailing list? Who can stop this? Please . . . Here is an example header: Received: from radicalmedia.com (radicalmedia.com [204.254.246.2]) by sapphire.omniscient.com (8.12.9/8.12.9) with ESMTP id h859XgFV007985 for [EMAIL PROTECTED]; Fri, 5 Sep 2003 05:33:42 -0400 (EDT) Received: by radicalmedia.com (CommuniGate Pro PIPE 4.1.1) with PIPE id 148545; Fri, 05 Sep 2003 05:33:42 -0400 Received: from localhost [127.0.0.1] by radicalmedia.com with SpamAssassin (2.55 1.174.2.19-2003-05-19-exp); Fri, 05 Sep 2003 05:33:40 -0400 From: Serap Çigdemgil [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: hi Date: Fri, 5 Sep 2003 12:19:24 +0300 Message-Id: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=--=_3F585874.2FD31CBE Sender: [EMAIL PROTECTED] X-UIDL: jYI!4AM!!g+#!hYf! X-Spam-Status: No, hits=1.0 required=5.0 tests=SEMIFORGED_HOTMAIL_RCVD,X_AUTH_WARNING version=2.55 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Notice that I received two (2) copies of this email: one (1) original, and one (1) sent back through [EMAIL PROTECTED] *AFTER* radicalmedia.com _added_ their own spamassassin headers. The real problem that I have with this is twofold: [1] There is absolutely *NO* good reason for anybody to re-send spam and virus/worms to this mailing list! [2] By mangling the original message, radicalmedia.com makes it more difficult for my own spam and virus processes to properly handle these kinds of message. So, I repeat, please, *STOP* this inconsiderate behaviour! -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Who is radicalmedia.com ???
And, why are they re-sending post-spamassassin'd spam, that they received from amanda mailing list, *BACK* through amanda mailing list? Who can stop this? Please . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: Not again !!!
Also sprach Jon LaBadie (Wed 06 Aug 02003 at 04:59:41PM -0400): On Wed, Aug 06, 2003 at 02:39:17PM -0500, Michael D. Schleif wrote: Yes, agreed; but, are the plethora of insipid and specious virus-found alarms really necessary (read: on-topic) on this -- or any -- mailing list? Yes, absolutely. Otherwise I would not know a virus had been posted :)) O, yeah, I dint think o dat . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: su amanda doesn't have permissions
Also sprach S. Keel (Fri 08 Aug 02003 at 03:09:49PM -0700): Hopefully someone here can help...I've been working through the Frankenlinux setup instructions along with the Using Amanda Chapter at Backupcentral to setup my site, but have run into a problem when I try to run... su amanda -c amlabel daily DailySet1-001 ...as root bash reports that it cannot find 'amlabel' 'amlabel' is installed into /usr/local/sbin, so I went ahead and added that path to my amanda user's $PATH environment variable, but it still doesn't work. I'm hesitant to make changes to ENV_PATH and ENV_SUPATH in /etc/login.defs becuase I don't want every user to have elevated privileges. Does anyone have a suggestion. Preferably: sudo -u backup amlabel daily DailySet1-001 Alternatively (untested): su - amanda -c amlabel daily DailySet1-001 -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: Disaster recovery.
Also sprach Gene Heskett (Fri 08 Aug 02003 at 02:16:17PM -0400): On Friday 08 August 2003 14:00, Ean Kingston wrote: I've been starting to work on a DRP plan here and I've run into a bit of a catch-22. If the amanda index (and tape in my case) server is lost and all I have left is the tapes. How do I rebuild new index files for my tapes so that I can restore? I can't just restore the last set of index files from the most recent backup because they would reflect the state of the tapes from one day earlier (wouldn't they?). I can't find a tool that I can feed the collection of tapes so that it will rebuild the index files. Is there such a thing. Not that I'm aware of, however other amanda experts may well point you to the correct answer. That said, that problem bothered me too, so now my tapesize has been reduced by about 100megs to make room, and I have a script set that runs after amdump has been completed. It packs up all the now unlocked stuffs from the configs and the indexes and appends them to the end of the tape, thereby giving me the current image of that stuff as it exists after the dump run that made this tape is complete. I've been threatening to post them, but they are as yet pretty specific to my install, needing a lot of dressing up to make them anywhere near universal. Currently working with a changer and a DDS2 tape drive in it. If you think they might be helpfull though, ask. I may find time to convert what you have to more generic application, should you care to share . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: Not again !!!
Also sprach Rebecca Pakish Crum (Wed 06 Aug 02003 at 02:23:30PM -0500): snip / It amazes me how often these two running arguments are repeatedly debated...using localhost and spam to the amanda list. For the love of pete...how many sys admins does it take to beat the dead horse? (I suppose I am now guilty as well by even responding to the tirades) Maybe there needs to be something addressed to the newbie's when they register with amanda.org as a part of the welcome email that says You are responsible for your own network...the list is open to everyone and everything, please don't complain about spam, viruses, etc. I find those who are bothered to be unprepared. Get a spam server...deal with it, move on. Or maybe those complaining would like to contribute and maintain a spam/virus server for the list. This is the 4th or 5th time this year this subject has gone on for far too long. Amanda is free, the knowledge everyone gains and contributes her is free, if the price is to be 'bothered' with extra emails, then pay for some other backup utility and you won't be bothered again. Yes, agreed; but, are the plethora of insipid and specious virus-found alarms really necessary (read: on-topic) on this -- or any -- mailing list? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
tape usage ???
Does amanda keep track of how many times a tape has been used? If not, how difficult would it be to increment a counter in the amanda tape header? Clearly, at 32kB, there is plenty of room in the header for this simple matter . . . What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
which tape is which ???
I have been using amanda for several weeks. Initially, I tested various configurations; but, now I am supposed to be ``in production'' ; Somehow, I find myself with two (2) identically labeled tapes: backup.005 ; amcheck finds both to be valid. tapelist shows one (1) entry for backup.005. How can I find out which of these is really in the current backup cycle? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: which tape is which ???
Also sprach Kurt Yoder (Tue 15 Jul 02003 at 11:10:34AM -0400): I believe both of them will be accepted by amanda when it's looking for backup.005. So just pick the most recently-written one to use as the real backup.005. Then erase the other one using mt or dd, and treat it as a blank tape. Michael D. Schleif said: I have been using amanda for several weeks. Initially, I tested various configurations; but, now I am supposed to be ``in production'' ; Somehow, I find myself with two (2) identically labeled tapes: backup.005 ; amcheck finds both to be valid. tapelist shows one (1) entry for backup.005. How can I find out which of these is really in the current backup cycle? That's my problem: if I knew which of these tapes is the ``most recently-written one'', then I would know which is in the current cycle ; So, how do I determine that? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: which tape is which ???
Also sprach Kurt Yoder (Tue 15 Jul 02003 at 11:31:21AM -0400): Michael D. Schleif said: snipped That's my problem: if I knew which of these tapes is the ``most recently-written one'', then I would know which is in the current cycle ; So, how do I determine that? Ah. Put one in and do dd if=tape device of=test_header bs=32k. This will grab the amanda tape header and put it in the file test_header. In this file you will then see the date of the dump on this tape. Perhaps, that should be: dd if=/dev/nst0 of=~/test_hdr bs=32k count=1 Thank you. -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: to compress or not to compress ???
Also sprach Paul Bijnens (Fri 04 Jul 02003 at 10:51:47AM +0200): snip / In docs/RESTORE, you can find all the commands you need to use an amanda tape without amanda software. That is an excellent document! I'm sorry that I bothered the list before finding and reading it . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
to compress or not to compress ???
Yes, I am learning -- at the expense of many questions ; First, a brief overview: I have five (5) Linux servers, totaling ~50 Gb used diskspace, divided roughly even across all five. I have several DAT tape drives, the largest of which is an HP DDS-3. I have twelve (12) DDS-3 tapes, and twenty (20) DDS-2 tapes, as well as several cleaning tapes. So far, I have configured: dumpcycle 7 runspercycle 7 runtapes 1 I am studying _Using Amanda_ here: http://www.backupcentral.com/amanda.html I am confused about two (2) things: [1] Should I use hardware compression? There seem to be several schools of thought here. I want to know how Amanda works with hardware compression? What are the advantages of using software compression? What are the disadvantages of using *both* hardware and software compression? [2] What are the optimal dumptypes for my situation? Yes, I have already struggled with and overcome dump vs. GNUTAR. My first mistake was using comp-root and comp-user on localhost. Yes, I understand that Amanda can facilitate planning and scheduling full vs. incremental backups. However, I am concerned about developing a simple recovery strategy. I am currently having problems with amrecover; but, I think that is due to short vs. FQDN usage -- so, I'll save that for another time. I am running exclusively Debian woody on all systems. I believe that I have a good working filesystem design. I am on a fast network. Yes, I come from a traditional system administrator's backup mindset, and I do not want that to undermine Amanda's design. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: to compress or not to compress ???
Also sprach Gene Heskett (Thu 03 Jul 02003 at 02:51:39PM -0400): On Thursday 03 July 2003 11:42, Michael D. Schleif wrote: Yes, I am learning -- at the expense of many questions ; First, a brief overview: I have five (5) Linux servers, totaling ~50 Gb used diskspace, divided roughly even across all five. I have several DAT tape drives, the largest of which is an HP DDS-3. I have twelve (12) DDS-3 tapes, and twenty (20) DDS-2 tapes, as well as several cleaning tapes. So far, I have configured: dumpcycle 7 runspercycle 7 runtapes 1 You left out tapecycle, which is the number of tapes in the rotation pool, in this case it should be not less than 15. Wouldn't that be eight (8)? runspercycle * runtapes + 1 snip / One thing to be aware of is that a tape, once written in the compressed mode, remembers that, and will overwrite your choices unless you go to a rather detailed method of removing the compressed flags. How do I do this? These tape drives have all used compression, and many of these tapes have been used once or twice. So, it looks like I will *not* use hardware compression, and I want to reap all of the benefits of that strategy. Also, what is the best way to turn off compression? # sudo mt-gnu -f /dev/nst0 datcompression Compression on. Compression capable. Decompression capable. # sudo mt-gnu -f /dev/nst0 datcompression 0 Compression off. Compression capable. Decompression capable. # sudo mt-gnu -f /dev/nst0 datcompression Compression off. Compression capable. Decompression capable. Will this persist across power cycles? Will previously hardware compressed tapes turn hardware compression back on? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: to compress or not to compress ???
Also sprach George Kelbley (Thu 03 Jul 02003 at 02:41:12PM -0600): restoring w/o amrestore can be done with dd, gzip, tar, and so on, way messy compared to amrecover (or amrestore) but its possible. That's one of the plus's to amanda. Kurt Yoder wrote: Assuming you're running Linux, all you need is some form of Linux rescue disk. I've got a bunch of Debian installer cd's lying around and have used them for similar purposes before. Probably most Linux installer cd's can be used like this, and I'm quite certain something like Knoppix would include all the utilities anyone would need. Who knows, might even work to restore tapes made with non-Linux amanda servers. BTW, if restoring without an amanda server, doesn't one also need amrestore? The other day I tried restoring an amanda image, and had to run it through amrestore before I could untar it. Eric Siegerman said: On Thu, Jul 03, 2003 at 12:17:16PM -0400, Ean Kingston wrote: Also, with hardware compression, I know I can restore the tape without having to worry about finding the right libraries and programs to do the restore. True. But one can work around that by backing up / uncompressed, and making sure it contains a (possibly statically linked) copy of gzip. Hmmm, something to add to my to-do list :-( Am I right that amrecover is useless *without* an index? Also, using only amrestore, is it possible to get at individual files/directories, or is it only a matter of restoring the entire dump/tarball? I am curious as to a procedure of manually -- without amanda -- viewing and restoring from amanda-written tapes . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: server will not backup itself ?!?!
Also sprach Paul Bijnens (Wed 02 Jul 02003 at 09:38:37AM +0200): Michael D. Schleif wrote: # grep amanda /etc/inetd.conf amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped ... # kill -HUP 351 # ps aux | grep inetd root 351 0.0 0.0 1256 544 ?S01:30 0:00 /usr/sbin/inetd One more thing to check: Is the inetd config really working? netstat -na | grep 10080 # netstat -na | grep 1008 tcp0 0 0.0.0.0:10082 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:10083 0.0.0.0:* LISTEN udp0 0 0.0.0.0:10080 0.0.0.0:* -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: server will not backup itself ?!?!
Also sprach Jay Lessert (Wed 02 Jul 02003 at 08:38:45AM -0700):
On Tue, Jul 01, 2003 at 09:59:16PM -0500, Michael D. Schleif wrote:
# bragi.private.network sda1 comp-root
# bragi.private.network sda4 comp-user
192.168.123.150 sda1 comp-root
192.168.123.150 sda4 comp-user
# localhost sda1 comp-root
# localhost sda4 comp-user
Report the problem using a single configuration that you believe
should work. In this case, I'm not sure what what would be.
So, please, help me by telling me which configuration that you want to
see documented, and what output you want to see from that configuration.
I will gladly supply the data, if you can help me resolve this problem.
So lets go with bragi.private.network in disklist. That should be
correct, unless you have bragi in /etc/hosts (it doesn't look
like you do).
Since both dns and hosts know this system as Bragi.private.network, that
is the name that is now in both disklist and amandahosts.
# ping bragi
PING Bragi.private.network (192.168.123.150): 56 data bytes
^
Is the Bragi (not bragi) real, or some sort of typo?
OK, bragi is Bragi in dns; but, name resolution, by rfc, is case
insensitive.
That's very nice, but I'm trying to help solve your problem. I'm not
sure, but it looks to me like bsd_security_ok() is just doing a
gethostbyaddr(), and then strcasecmp()'ing against
.amandahosts; unless gethostbyaddr() is smashing case, that
looks case-sensitive.
You should see some sort of amandahostsauth failed message somewhere
in the log or the debug files if this is going on. Looks like you can
re-compile with SHOW_SECURITY_DETAIL defined to get more detail
in the debug logs.
If you've got bragi.private.network in /etc/hosts, and if you've
got the usual nsswitch.conf hosts setting, the DNS won't matter.
# sudo -u backup amcheck -c DailySet1
Amanda Backup Client Hosts Check
WARNING: Bragi.private.network: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.025 seconds, 1 problem found
(brought to you by Amanda 2.4.4)
[EMAIL PROTECTED]:/var/log/amanda/DailySet1
# ls -l /tmp/amanda/* /var/log/amanda/DailySet1/*
-rw---1 backup backup182 Jul 2 11:51
/tmp/amanda/amcheck.20030702115039.debug
-rw---1 backup backup176 Jul 2 11:55
/tmp/amanda/amtrmidx.20030702115535.debug
-rw---1 backup backup197 Jul 2 11:55
/tmp/amanda/amtrmlog.20030702115535.debug
-rw---1 backup backup 5804 Jul 2 11:55
/var/log/amanda/DailySet1/amdump.1
-rw---1 backup backup562 Jul 2 11:55
/var/log/amanda/DailySet1/log.20030702.0
[EMAIL PROTECTED]:/var/log/amanda/DailySet1
# cat ./log.20030702.0
DISK planner Bragi.private.network sda1
DISK planner Bragi.private.network sda4
START planner date 20030702
INFO planner Adding new disk Bragi.private.network:sda1.
INFO planner Adding new disk Bragi.private.network:sda4.
START driver date 20030702
START taper datestamp 20030702 label backup.004 tape 0
ERROR planner Request to Bragi.private.network timed out.
FINISH planner date 20030702
WARNING driver WARNING: got empty schedule from planner
STATS driver startup time 29.987
INFO taper tape backup.004 kb 0 fm 0 [OK]
FINISH driver date 20030702 time 33.271
[EMAIL PROTECTED]:/var/log/amanda/DailySet1
# cat /tmp/amanda/am*
amcheck: debug 1 pid 19760 ruid 34 euid 0: start at Wed Jul 2 11:50:39 2003
amcheck: dgram_bind: socket bound to 0.0.0.0.655
amcheck: pid 19760 finish time Wed Jul 2 11:51:09 2003
amtrmidx: debug 1 pid 19891 ruid 34 euid 34: start at Wed Jul 2 11:55:35 2003
/usr/lib/amanda/amtrmidx: version 2.4.4
amtrmidx: pid 19891 finish time Wed Jul 2 11:55:35 2003
amtrmlog: debug 1 pid 19890 ruid 34 euid 34: start at Wed Jul 2 11:55:35 2003
/usr/lib/amanda/amtrmlog: version 2.4.4
Keeping 16 log files
amtrmlog: pid 19890 finish time Wed Jul 2 11:55:35 2003
[EMAIL PROTECTED]:/var/log/amanda/DailySet1
# grep -i fail /tmp/amanda/* /var/log/amanda/DailySet1/*
/var/log/amanda/DailySet1/amdump.1:FAILED QUEUE: empty
P.S., Is there some reason that you do not want your participation in
this thread posted to the mailing list?
Because everything I'm saying has been said on the list many times
before. No need to clutter the archives.
Do you mind if I cc the list on our dialog?
I do appreciate the level of detail to which you go with this, and I
have not -- yet -- found this level of detail in the archives.
Thank you.
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
pgp0.pgp
Description: PGP signature
Re: server will not backup itself ?!?!
Also sprach Paul Bijnens (Wed 02 Jul 02003 at 07:35:07PM +0200):
Michael D. Schleif wrote:
# sudo -u backup amcheck -c DailySet1
Amanda Backup Client Hosts Check
WARNING: Bragi.private.network: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.025 seconds, 1 problem found
(brought to you by Amanda 2.4.4)
[EMAIL PROTECTED]:/var/log/amanda/DailySet1
# ls -l /tmp/amanda/* /var/log/amanda/DailySet1/*
-rw---1 backup backup182 Jul 2 11:51
/tmp/amanda/amcheck.20030702115039.debug
-rw---1 backup backup176 Jul 2 11:55
/tmp/amanda/amtrmidx.20030702115535.debug
-rw---1 backup backup197 Jul 2 11:55
/tmp/amanda/amtrmlog.20030702115535.debug
-rw---1 backup backup 5804 Jul 2 11:55
/var/log/amanda/DailySet1/amdump.1
-rw---1 backup backup562 Jul 2 11:55
/var/log/amanda/DailySet1/log.20030702.0
There should be a file /tmp/amanda/amandad.*.debug too.
That's the file that the client side creates with the debug info.
Its absence means that amandad (listening on port 10080 udp) is not
even started by (x)inetd. You should take a very very close look
at that line in the inetd config.
Have a look in /var/{log,adm}/messages too.
Maybe (temporarily) remove the tcpd wrapper, if you use it.
Disable any firewall (check ipchains AND iptables!).
If you have nc installed (because you need udp and not tcp)?
try sending a bogus command to the amandad daemon:
# echo | nc -u bragi 10080
Amanda 2.4 NAK HANDLE SEQ 0
ERROR expected Amanda, got
^C --- interrupt with Control-C
punt!
#
You can even try to start amandad up manually (but you want be
able to communicate with it), and trace it:
# strace /usr/local/libexec/amandad
...(many lines output removed)...
select(1, [0], NULL, NULL, {30, 0}
^C
Eureka!
Some time ago, I had done quite a bit of hardening of this system,
bragi. Even though I had looked in the system logs for amanda errors, I
did not make this correlation:
Jul 2 12:52:59 Bragi inetd[21590]: execv /usr/sbin/tcpd: Permission denied
Jul 2 12:52:59 Bragi inetd[351]: /usr/sbin/tcpd: exit status 0x1
/usr/sbin/tcpd had mode -rwxr-x--- (0750), and it requires -rwxr-xr-x
(0750), since backup does not belong to group root.
I have other problems; but, at least amcheck is satisfied and I have
several times gotten amanda to start backing up.
Thank you.
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
pgp0.pgp
Description: PGP signature
EXT2 directory corrupted while converting directory #195556 ???
Now that I have amanda doing something useful, I have run into another problem. The first full backup that I did was successful, including backing up /dev/sda1. Subsequently, in order to test various functionality of amanda, I did this: # sudo -u backup amadmin DailySet1 force Bragi.private.network amadmin: Bragi.private.network:sda1 is set to a forced level 0 at next run. Then, I reset the time for the cronjob and continually get the subject error on /dev/sda1: sendbackup: start [Bragi.private.network:sda1 level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | DUMP: Date of this level 0 dump: Wed Jul 2 15:00:04 2003 | DUMP: Dumping /dev/sda1 (/) to standard output | DUMP: Added inode 7 to exclude list (resize inode) | DUMP: Label: none | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 556620 tape blocks. | DUMP: Volume 1 started with block 1 at: Wed Jul 2 15:00:05 2003 | DUMP: dumping (Pass III) [directories] ? /dev/sda1: EXT2 directory corrupted while converting directory #195556 ? | DUMP: Broken pipe I do not find anything of this sort in the amanda archives. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: EXT2 directory corrupted while converting directory #195556 ???
Also sprach Paul Bijnens (Wed 02 Jul 02003 at 11:23:10PM +0200): Michael D. Schleif wrote: ... | DUMP: dumping (Pass III) [directories] ? /dev/sda1: EXT2 directory corrupted while converting directory #195556 ? | DUMP: Broken pipe I do not find anything of this sort in the amanda archives. Well, I do... http://groups.yahoo.com/group/amanda-users/message/44279 http://groups.yahoo.com/group/amanda-users/message/42244 A filesystem check helps too sometimes. Dump for ext2 always had a bad reputation. There was no maintainer for dump for some time. Are you sure you have the latest version from http://dump.sourceforge.net/ . It is supposed to work better. I left dump a long time ago, and use tar now (I have a mixed Solaris / Linux / MS environment - gnutar makes interoperability of restores easy). So, GNUTAR it is, then ; -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
howto decide full vs. incremental ???
Thank you, all of you, for your help -- I have a working amanda! Now, I am trying to understand amanda's built-in backup strategy. How can I know when `disk' will be backed up full or incremental? I do not have a changer, and I have more data across all disks than single tape capacity. Therefore, I want to stagger full backups, such that on any given tape, only one (1) system is full backup and all others are incremental backups. I have scoured amanda(8), and learned alot; but, I do not find this information there. Please, kindly point me to the right point in TFM, and I can read . . . What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
server will not backup itself ?!?!
Hi! I installed amanda on a Debian Woody system, and everything appears to be configured properly. amcheck -lstw runs without incident. However, I am victim to what appears to be the most common problem: selfcheck request timed out. Host down? I have scoured the Faq-O-Matic, and I list below the results of all the suggested fixes. What do you think? ### ### # sudo -u backup amcheck -lstw DailySet1 Amanda Tape Server Host Check - Holding disk /space: 1294188 KB disk space available, that's plenty Tape backup.003 is writable Tape backup.003 label ok NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run Server check took 0.077 seconds (brought to you by Amanda 2.4.2p2) ### ### # sudo -u backup amcheck -c DailySet1 Amanda Backup Client Hosts Check WARNING: 192.168.123.150: selfcheck request timed out. Host down? Client check: 1 host checked in 30.024 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) ### ### # find /tmp/amanda /tmp/amanda /tmp/amanda/amcheck.20030701093517.debug /tmp/amanda/amcheck.20030701093730.debug /tmp/amanda/amcheck.20030701093853.debug /tmp/amanda/amcheck.20030701094157.debug /tmp/amanda/amcheck.20030701094626.debug /tmp/amanda/amandad.20030701095200.debug /tmp/amanda/amcheck.20030701095919.debug /tmp/amanda/amcheck.20030701100359.debug ### ### # grep amanda /etc/services amanda 10080/udp # amanda backup services kamanda 10081/tcp # amanda backup services (Kerberos) kamanda 10081/udp # amanda backup services (Kerberos) amandaidx 10082/tcp # amanda backup services amidxtape 10083/tcp # amanda backup services ### ### # grep amanda /etc/inetd.conf amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped ### ### # kill -HUP 351 # ps aux | grep inetd root 351 0.0 0.0 1256 544 ?S01:30 0:00 /usr/sbin/inetd ### ### # su - backup [EMAIL PROTECTED]:~$ /usr/lib/amanda/amandad [EMAIL PROTECTED]:~$ exit logout ### ### # cat /etc/amandahosts # localhost backup 192.168.123.150 backup # bragi.private.network backup ### ### # grep -v '^\([# ]\|$\)' /etc/amanda/DailySet1/disklist 192.168.123.150 sda1 comp-root 192.168.123.150 sda4 comp-user ### ### -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --
Re: server will not backup itself ?!?!
Also sprach Jay Lessert (Tue 01 Jul 02003 at 05:09:21PM -0700): On Tue, Jul 01, 2003 at 06:36:34PM -0500, Michael D. Schleif wrote: What do you think? ### ### # grep -v '^\([# ]\|$\)' /etc/amanda/DailySet1/disklist 192.168.123.150 sda1 comp-root 192.168.123.150 sda4 comp-user I think if *you* don't know the hostname, how to you expect amanda to figure it out? :-) Reverse lookups have to work, e.g., from the entries in .amandahosts. Don't use localhost, either, please. I have erred on the side of terseness in my original post ; Of course, I have tried every combination of hostname and address in disklist, and also made certain that that name there is the _same_ as that used in amandahosts: # bragi.private.network sda1 comp-root # bragi.private.network sda4 comp-user 192.168.123.150 sda1 comp-root 192.168.123.150 sda4 comp-user # localhost sda1 comp-root # localhost sda4 comp-user Furthermore, from this host, both amanda server client, I have _no_ name resolution issues: # host bragi bragi.private.network has address 192.168.123.150 # ping bragi PING Bragi.private.network (192.168.123.150): 56 data bytes 64 bytes from 192.168.123.150: icmp_seq=0 ttl=255 time=0.1 ms 64 bytes from 192.168.123.150: icmp_seq=1 ttl=255 time=0.0 ms 64 bytes from 192.168.123.150: icmp_seq=2 ttl=255 time=0.0 ms --- Bragi.private.network ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.0/0.0/0.1 ms Everywhere, I see the strong warnings against using localhost. With Debian, localhost is the default used in disklist. Why this adversity for localhost? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: server will not backup itself ?!?!
Also sprach Kurt Yoder (Tue 01 Jul 02003 at 08:46:41PM -0400): Did you look through the amcheck debug files that you saw in /tmp/amanda? Yes, since posting, I found an archived post suggesting this, in which I find new information. However, I cannot understand its meaning: # cat /tmp/amanda/amandad.20030701171859.debug amandad: debug 1 pid 25109 ruid 34 euid 34 start time Tue Jul 1 17:18:59 2003 /usr/lib/amanda/amandad: version 2.4.2p2 /usr/lib/amanda/amandad: build: VERSION=Amanda-2.4.2p2 /usr/lib/amanda/amandad:BUILT_DATE=Tue Apr 2 21:24:21 UTC 2002 /usr/lib/amanda/amandad:BUILT_MACH=Linux cyberhq 2.4.18pre2 #1 SMP Tue Jan 8 18:13:43 PST 2002 i686 unknown /usr/lib/amanda/amandad:CC=gcc /usr/lib/amanda/amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin /usr/lib/amanda/amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man /usr/lib/amanda/amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda /usr/lib/amanda/amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ /usr/lib/amanda/amandad:RDEV_PREFIX=/dev/r DUMP=/sbin/dump /usr/lib/amanda/amandad:RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient /usr/lib/amanda/amandad:GNUTAR=/bin/tar COMPRESS_PATH=/bin/gzip /usr/lib/amanda/amandad:UNCOMPRESS_PATH=/bin/gzip MAILER=/usr/bin/Mail /usr/lib/amanda/amandad: listed_incr_dir=/var/lib/amanda/gnutar-lists /usr/lib/amanda/amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 /usr/lib/amanda/amandad:DEFAULT_TAPE_SERVER=localhost /usr/lib/amanda/amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM /usr/lib/amanda/amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE /usr/lib/amanda/amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS /usr/lib/amanda/amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP /usr/lib/amanda/amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast /usr/lib/amanda/amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout error receiving message: timeout amandad: pid 25109 finish time Tue Jul 1 17:19:29 2003 Can you manually connect to the services in question? (eg telnet localhost 10082, etc)? Yes, and no . . . # telnet localhost 10080 Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused # telnet localhost 10082 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. # telnet localhost 10083 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. Your /etc/amandahosts has localhost commented out. If you're connecting to localhost this could be a problem. Also, my amandahosts is in /var/backup/.amandahosts, and I'm also running Debian. Unless /etc/amandahosts is a symlink to /var/backup/.amandahosts, you might try adding your entries there. # ls -al /var/backups/.amandahosts lrwxrwxrwx1 backup backup 16 Jun 30 23:56 /var/backups/.amandahosts - /etc/amandahosts As I added in a previous exchange, much of the archives and Faq-O-Matic strongly opposes use of localhost -- a point that interests me; but, has little bearing on my particular solution ; What do you think? On Tuesday, July 1, 2003, at 07:36 PM, Michael D. Schleif wrote: Hi! I installed amanda on a Debian Woody system, and everything appears to be configured properly. amcheck -lstw runs without incident. However, I am victim to what appears to be the most common problem: selfcheck request timed out. Host down? I have scoured the Faq-O-Matic, and I list below the results of all the suggested fixes. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: server will not backup itself ?!?!
Also sprach Joshua Baker-LePain (Tue 01 Jul 02003 at 10:29:38PM -0400):
On Tue, 1 Jul 2003 at 6:36pm, Michael D. Schleif wrote
# grep amanda /etc/inetd.conf
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad
amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
What's in /etc/hosts.{allow,deny}. You've TCP wrapped amandad, are you
letting localhost connect?
# cat /etc/hosts.{allow,deny}
# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example:ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name portmap for the
# daemon name. Remember that you can only use the keyword ALL and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/netbase/portmapper.txt.gz for further information.
#
ALL: LOCAL
statd: .private.network
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example:ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name portmap for the
# daemon name. Remember that you can only use the keyword ALL and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/netbase/portmapper.txt.gz for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.
ALL: PARANOID
Also, is ip{chains,tables} in the way?
# iptables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Bragi is inside a private network, which is firewalled to the Internet;
but, as you can see, no firewalling is done inside this network.
What do you think?
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
pgp0.pgp
Description: PGP signature
Re: server will not backup itself ?!?!
Also sprach Jay Lessert (Tue 01 Jul 02003 at 07:45:50PM -0700): On Tue, Jul 01, 2003 at 09:08:33PM -0500, Michael D. Schleif wrote: Of course, I have tried every combination of hostname and address in disklist, and also made certain that that name there is the _same_ as that used in amandahosts: # bragi.private.network sda1 comp-root # bragi.private.network sda4 comp-user 192.168.123.150 sda1 comp-root 192.168.123.150 sda4 comp-user # localhost sda1 comp-root # localhost sda4 comp-user Report the problem using a single configuration that you believe should work. In this case, I'm not sure what what would be. OK, I understand your perplexity; however, I started with the default localhost, moved to simply bragi, then bragi.private.network, and finally to it ip address -- *ALL* exhibited identical behaviour, as far as I can see. So, please, help me by telling me which configuration that you want to see documented, and what output you want to see from that configuration. I will gladly supply the data, if you can help me resolve this problem. Do you really have a DNS server that resolves .network as a TLD? Yes, I run tinydns on this private network. # ping bragi PING Bragi.private.network (192.168.123.150): 56 data bytes ^ Is the Bragi (not bragi) real, or some sort of typo? OK, bragi is Bragi in dns; but, name resolution, by rfc, is case insensitive. Everywhere, I see the strong warnings against using localhost. With Debian, localhost is the default used in disklist. Why this adversity for localhost? It is a bad idea IMO, 1) because the reverse lookup will often fail, 2) because localhost in the amanda records is not very self-documenting. There are lots of things in default setups that are bad. Yes, of course. Nevertheless, some newbies want to know the reason why . . . P.S., Is there some reason that you do not want your participation in this thread posted to the mailing list? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
