Does bin have read access on the raw devices /dev/rdsk (or /dev/vx/)??
Toomas Aas wrote:
Hi David!
On 8 Apr 02 at 10:57 you wrote:
I've just upgraded from 2.4.2p2 to 2.4.3b3, at the same time I've changed my
amanda user from root to bin. I notice when I get the report at the end of a
To confirm bin does have read access I did a
dd if=/dev/rdsk/c0t0d0s0 of=/tmp/foobar bs=512 count=1
as bin and it did not complain as it would if bin did not have read
access.
On 8 Apr 2002, at 9:08, Don Potter wrote:
Does bin have read access on the raw devices /dev/rdsk (or
For example:
/export/home/staff
has 11.8GB but is only backing up 235MB. Now when I do a du -sk
/export/home/staff as user bin it reports (Guess what) 235MB.
Please post what df -k /export/home/staff says. I'm guessing it's not
a real file system but a subdirectory (or some goofy
David Flood [mailto:[EMAIL PROTECTED]] wrote:
I've just upgraded from 2.4.2p2 to 2.4.3b3, at the same time
I've changed my
amanda user from root to bin. I notice when I get the report
at the end of a
level 0 backup. It has backed up nowhere near all the data
that exists.
For
No -- this is the group that the files/amanda user belong to. The idea is that
disk devices (and files such as /etc/dumpdates) are owned by root, but the group
disk (on my linux box), or operator (on my freebsd one), or sys (I think,
on the solaris machines) has read and write access. This
David
make sure that the 'bin' user has access to the /dev/dsk/c0t0d0s0 (or
whatever). It will probably need to be a member of sys on a solaris
box, check the file group membership of the actual device.
--
Martin
David Flood wrote:
I've just upgraded from 2.4.2p2 to 2.4.3b3, at the same
Hello all.
I am currently using Amanda version 2.4.2p2 without any problems. Are
there any compelling reasons that I should upgrade to 2.4.3b3 since
everything is working now?
Thanks!
Anthony
I did this already in reply to either Toomas or Don's reply but I think I only sent it to them instead of the list - Doh.
Here goes:
I'll use c0t0d0s0 in this example but all slices on all disk are the same in terms of ownership and permissions.
ls -la /dev/dsk/c0t0d0s0
lrwxrwxrwx 1 root
It appears that the offline_before_unload switch/feature does not work
in this script! Am i :-/
/gat
John R. Jackson wrote:
I think the following patch fixes that version. Also, there is a new
copy of the whole thing at:
ftp://gandalf.cc.purdue.edu/pub/amanda/chg-zd-mtx.sh.in-243
It appears that the offline_before_unload switch/feature does not work
in this script! ...
Insufficient details, so you get a million questions in response:
Did you drop this file in place of your existing chg-zd-mtx.sh.in file
(saving the original in case there is a problem)?
Did you rerun
This is far short of a million, even if its binary, questions!
actually plugged it in, and linked it to ...sh.in
rebuilt it ( make, not configure ) , but no install. Just cp'd the
chg-zd-mtx to /usr/local/libexec. I know its there bec the old version
is ~17k, and newer one is ~37k
it does not
I have not run a restore to check but last time when the symptoms
were identical it was mostly directory structure taht was backed up
and any files bin had access to.
To try and explain that a bit more let say I had a user named bob:
/export/home/staff/bob
the backup tape would contain the
On 7 Apr 2002 at 8:41am, Anthony Valentine wrote
I am currently using Amanda version 2.4.2p2 without any problems. Are
there any compelling reasons that I should upgrade to 2.4.3b3 since
everything is working now?
Given that 'b' means beta... probably not. ;)
Even when 2.4.3 proper comes
Interesting, the log file shows that offline_before_unload is set to 0
:-{
Storage Element 5:Full
Storage Element 6:Empty
Storage Element 7:Full
12:18:14 SLOTLIST - firstslot set to 1
12:18:14 SLOTLIST - lastslot set to 7
12:18:14 SLOTLIST - 1 2 3 4 5 6 7
12:18:15 Config info:
I've created a file called duampatch with vi, copied the patch from the
web page http://www.amanda.org/patches/2.4.2p2/advfs.diff, and pasted
it into the file. When I issue:
patch -p1 duampatch
from the top level of the amamanda-2.4.2 tree, it just says, Hmm... I
can't seem to find a
OK thanks John that's explained a lot but how would you explain
(messed up index file or no) how it worked with bin as the user
under 2.4.1p1? Was there something changed between 2.4.1p1
and 2.4.2p2 that would affect this?
I don't want to appear to be nagging on but backups is one of the
This is far short of a million, even if its binary, questions!
It was base 1.30766 :-).
actually plugged it in, and linked it to ...sh.in
rebuilt it ( make, not configure ) , but no install. Just cp'd the
chg-zd-mtx to /usr/local/libexec. ...
You have to run ./configure to convert
There are still some bug-a-boo's.
non-amanda tape in slot 5, and loaded in tape drive.
no tape in slot 6. There is an amanda tape in slot 7
issue an amcheck confname
get
--
[Amanda@kodak Amanda]$ amtape confname slot 5
amtape:
... how would you explain
(messed up index file or no) how it worked with bin as the user
under 2.4.1p1? ...
I don't think it was. I don't see any way it could have been working
unless you were running it as root.
Well, actually, you might have been able to configure Amanda using
Problem solved, as determined by one dump having the client disks indexed so far.
The issue appeared to be that the client had two IP addresses (because
of a solution to another, temporary problem). Getting back to one IP
address returned the indexing.
Thanks for all the help, and I'll still
I've created a file called duampatch with vi, copied the patch from the
web page http://www.amanda.org/patches/2.4.2p2/advfs.diff, and pasted
it into the file. ...
Bad idea. Never try to copy/paste patches. There is practically
zero chance it won't get messed up along the way (tabs =
Hello all,
I'm a brand new if about amanda and mtx so please don't laugh too hard at
me. I'm trying to use our old, retired HP C1553A (it was running under Novell
with Arcserve as a backup software for a few years without any major
problems) under Linux and Amanda. I have my homework done
Started debugging the script ...
Which version?
seems like its reading the file
changer.conf.conf ( non-existent file ) and reading the options from
there, rather than from just changer.conf.
It takes changerfile from amanda.conf (amgetconf config changerfile)
and tacks on .conf to make the
Greg Wardawy [mailto:[EMAIL PROTECTED]] wrote:
Amanda Backup Client Hosts Check
ERROR: localhost: [access as amanda not allowed from amanda@linver]
amandahostsauth failed
Client check: 1 host checked in 0.020 seconds, 1 problem found
Hmmm... I can't help
I'm a brand new if about amanda and mtx so please don't laugh too hard at
me. ...
We never laugh at new users!!! :-)
Welcome!
in the mtx-changer.conf file I have:
...
statefile /var/lib/amanda/DailySet1/curinfo/localhost/_etc/state
slot 1 /dev/sga
slot 2 /dev/sga
...
Where did you get the
I've got a server farm of about 30 machines, most on various RedHat
distributions, a few AIX.
I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT tapes.
I have 10 physical backup tapes available for each drive.
The tape drives are attached to 3 linux computers, Columbia, Frith Coffee,
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote:
I've got a server farm of about 30 machines, most on various RedHat
distributions, a few AIX.
I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT tapes.
I have 10 physical backup tapes available for each drive.
The tape drives are attached to
On Mon, 8 Apr 2002, Doug Silver wrote:
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote:
I've got a server farm of about 30 machines, most on various RedHat
distributions, a few AIX.
I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT tapes.
I have 10 physical backup tapes available
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote:
On Mon, 8 Apr 2002, Doug Silver wrote:
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote:
I've got a server farm of about 30 machines, most on various RedHat
distributions, a few AIX.
I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT
In addition to the comments Doug made, I just want to remind you that
a given Amanda client can only be in one configuration at a time. For
instance, you will not be able to put clientA:/etc in the configuration
run by the small tape drive machine and clientA:/home in the large
tape drive
There are 4 day-tapes day1-day4 which are used every week from Monday to
Thursday in rotation, so only the tape with the oldest data is overwritten.
It would be a good idea to get out of the habit of associating specific
tapes with specific days. Amanda will always use the oldest tape.
If you
The file vmlinuz-2.4.2 in the boot directory does not seem to be backed
up correctly.
If I use dump on the partition and then restore I get
'end-of-input encounted while extracting ./vmlinuz-2.4.2-2'
I assume what you mean is you told Amanda to use dump, right?
Amanda pretty much just manages
On Monday 08 April 2002 16:46, you wrote:
I'm a brand new if about amanda and mtx so please don't laugh too hard
at me. ...
We never laugh at new users!!! :-)
That's what I was thinking but, actually, I don't mind if somebody wants to
laugh at me if at the same time I can learn
33 matches
Mail list logo
