Hi,
we are using amanda 2.4.1p1 on a Suse Linuxas tapeserver for half a year
now.
It worked quite fine, dispite some problems which I mostly solved
without to
much efforts. Recently I added other pc disks to our disklist (using
samba)
which resulted in those strange result:
FAILURE
On Fri, 2 Feb 2001, Michael Russell wrote:
I'm using 2.4.2 and have noticed that the mailed output has some problems
with some of the big disks' columns of info running together. The column
for the tape speed is too small too, since the advent of faster tape
drives:
You can adjust
The beginning of my configuration file looks like:
# /etc/amanda/Config1/amanda.conf
org "Config1" # your organization name for reports
mailto "[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]" # list
of message recipients
dumpuser "backup" # the user to run dumps
under
* Victor R. Cain [EMAIL PROTECTED] (Fri, Feb 02, 2001 at 10:36:20AM -0500)
The beginning of my configuration file looks like:
# /etc/amanda/Config1/amanda.conf
org "Config1" # your organization name for reports
mailto "[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]" # list
Gerhard den Hollander wrote:
* Victor R. Cain [EMAIL PROTECTED] (Fri, Feb 02, 2001 at 10:36:20AM -0500)
The beginning of my configuration file looks like:
# /etc/amanda/Config1/amanda.conf
org "Config1" # your organization name for reports
mailto "[EMAIL PROTECTED] [EMAIL
Jason -
Yes -
[amanda@ford amanda]$ amtape daily slot 13
amtape: could not load slot 0: illegal request
But with the change in code this now works.
Much thanks for pointing this out.
--doug
At 08:04 AM 2/2/2001 -0500, you wrote:
On Fri, 02 Feb 2001, Doug Munsinger wrote:
I'm testing
Also, while I have your attention, is this sort of message expected
in the NOTES section for each run? ...
taper: tape mti-bk04 kb 45482304 fm 23 [OK]
It's normal and tells you how much taper wrote (~45 GBytes in this case).
This is particularly useful when it bangs into end of tape because
mailto "[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]" ...
Amcheck reports no errors, and the runs appear to be happening,
but I'm getting no e-mail reports. Is there something wrong
with my "mailto" line?
Gerhard was mistaken with his suggestion. The "mailto" parameter must
be a
"name@IP Address" is not a valid address to send email to. You must
use either "name@hostname" or "name@[IP address]". This is in an RFC
somewhere. I'd use name@hostname if I could; I'd not trust the mail
software to handle name@[IP address] correctly since it's used so
seldom.
I've been having trouble backing up one client, where I changed the
dumptype to use tar on one of its filesystems (and I'm using tar 1.13.17 on
the client). All other clients use dump, and while I left the etimeout
setting to the default of 600, the backup ran fine except for the client
Any ideas, thoughts, suggestions, admonishments?
What's in /tmp/amanda/sendsize*debug on the client?
If you don't see anything running for your Amanda user on the server,
then it must have died since you can run amstatus (i.e. the amdump
file has not been renamed to amdump.1, unless you
Hi,
a short suggestion:
put this in your amanda.conf:
mailto "backup"
and in your /etc aliases put this:
backup: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
and you get what you want..
at least, thats the way we do it.
Christoph
"Victor R. Cain" schrieb:
Gerhard den
Hi Suman,
Did you check on the client to see what's in the debug files of the
/tmp/amanda directory?
Check the permissions on /usr/local/libexec/runtar--it must be owned by
root and SUID like this:
-rwsr-x---1 root amanda 78334 Nov 13 15:32
/usr/local/libexec/runtar
I had a
got result for host mogadon disk /etc: 0 - -1K, -1 - -1K, -1 - -1K
What's in /tmp/amanda/sendsize*debug on mogadon?
smallA
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Thank you all for your prompt reply. Here comes the output of
/tmp/amanda/sendsize*debug -
/usr/local/libexec/sendsize: version 2.4.1p1
calculating for amname '/etc', dirname '/etc'
sendsize: getting size via dump for /etc level 0
sendsize: running "/sbin/dump 0sf 1048576 - /etc"
running
Title: non-rewinding?
Hi all,
I finally got my changer working with the stctl driver SCSI II (Exabyte 10H with EXB 8500 series drive/tapes). Running on Solaris 7 (sparc). My changer finally sees all the tapes in it and now I have moved on to the point where I begin to 'amlabel' each of
Date: Fri, 2 Feb 2001 11:51:37 -0800 (PST)
From: smallA [EMAIL PROTECTED]
/usr/local/libexec/sendsize: version 2.4.1p1
calculating for amname '/etc', dirname '/etc'
sendsize: getting size via dump for /etc level 0
sendsize: running "/sbin/dump 0sf 1048576 - /etc"
running
and in your /etc aliases put this:
backup: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
and you get what you want..
at least, thats the way we do it.
Christoph
don't forget to run 'newaliases'
-Ben
... It tells me to check my
amanda.conf file to verify that the drive is "non-rewinding".
And did you?
Amanda **must** have a non-rewinding device. For Solaris, that means
you need the name with an 'n' in it, e.g. /dev/rmt/0mn (as compared with
just 0m).
... is there a way to work around it
Ok, I'm a few steps closer to adding barcode support to a modified chg-zd-mtx
script. I have a two questions for some people in the know.
chg-scsi has the following params:
./chg-scsi-slot param
./chg-scsi-info
./chg-scsi-reset
./chg-scsi-eject
I read in the archives that this error is usually caused by bad
tapes, or write protect etc. I know that the tape is in good condition,
because I tar'd to it before labeling.
This particular problem would not be caused by a bad tape.
On the client, the sendbackup.debug file says
I was asked for some additional information regarding the configuration of
the system
System configuration:
Sun E450
Solaris 7
StorEdge L280 tape drive
Amanda 2.4.2
As I said in my previous message, we have been using the L280 with NetBackup
for several months, but have decided that it isn't
System configuration:
Sun E450
Solaris 7
...
I downloaded the drivers that were provided by John the beginning of this
month and installed the 32 bit version in /usr/kernel/drv
Umm, isn't an E450 an Ultra? Are you running a 32 bit or 64 bit kernel?
If 64 bit, you need to use the 64 bit sst.
I
23 matches
Mail list logo
