You are probably right about the first problem, it should be permissions.
You can check the permissions of the disk device with the command `ls -l
/dev/hda`. The amanda backup user, or a group the amanda backup user is a
member of, needs to have read access to this device to back it up.
For the second error, the only reason I know of that a disk can't switch to
incremental mode is if there is no previous level 0 backup to base the
incremental on. Look in the log files for the level 0 estimate for that
drive, and it is probably larger than the amount of tape AMANDA thought she
would have left after completing all other required backups. You have a
couple of choices to fix this: You could just let it ride, knowing that that
disk isn't getting backed up, and sometime in the next few tapes, AMANDA
might have enough space (because other disks backups get bumped to higher
incremental levels) to do the level 0 backup; OR, you could temporarily edit
your disk list to just include this one partition, do a separate backup run
to get it started, and then put your other disks back in the disk list for
the next run.
-----Original Message-----
From: Justin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 19, 2000 4:18 PM
To: [EMAIL PROTECTED]
Subject: AMDUMP errors
I have been receiving 2 different errors lately.
The first one started to occur after rebuilding my Tape Backup Server after
a Hard Disk Crash. I changed it from a SCSI disk to a IDE disk. Now when
ever it goes to dump any of the file systems on that system (sol), it gives
this in the AMDUMP report:
sol hda1 lev 0 FAILED [disk hda1 offline on sol?]
When I do amcheck it gives this:
ERROR: sol: [can not access hda1 (hda1): No such file or directory]
And this is how it is configured in disklist:
sol hda1 comp-root-tar
It seems to me that it must be some sort of permissions error, but I thought
I checked everywhere. It is running RedHat 7.0, and all the Amanda services
(amandad, amandaidx, amidxtape) are running as user=backup group=disk.
Backup is in group disk.
The second error I am not to sure about:
tigereye hda4 lev 0 FAILED [can't switch to incremental dump]
Why would it not be able to switch to a incremental dump? Is there some
sort of lock file somewhere that I need to remove?
Thanks for your help in advance.
.~.
/v\
-- // \\
JA /( )\
^`~`^
L I N U X
[---------------------------------------------------]
Justin Ainsworth
PHONE: (530) 879-5660x108 Systems Administrator
FAX: (530) 879-5676 Sunset Net LLC
WEB: http://www.sunset.net 1915 Mangrove Ave
EMAIL: [EMAIL PROTECTED] Chico, CA 95926
[---------------------------------------------------]
