> 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.
[backup@sol /dev]$ ls -la | grep hda
brw-rw---- 1 root disk 3, 0 Aug 24 02:00 hda
brw-rw---- 1 root disk 3, 1 Aug 24 02:00 hda1
brw-rw---- 1 root disk 3, 10 Aug 24 02:00 hda10
brw-rw---- 1 root disk 3, 11 Aug 24 02:00 hda11
brw-rw---- 1 root disk 3, 12 Aug 24 02:00 hda12
brw-rw---- 1 root disk 3, 13 Aug 24 02:00 hda13
brw-rw---- 1 root disk 3, 14 Aug 24 02:00 hda14
brw-rw---- 1 root disk 3, 15 Aug 24 02:00 hda15
brw-rw---- 1 root disk 3, 16 Aug 24 02:00 hda16
brw-rw---- 1 root disk 3, 2 Aug 24 02:00 hda2
brw-rw---- 1 root disk 3, 3 Aug 24 02:00 hda3
brw-rw---- 1 root disk 3, 4 Aug 24 02:00 hda4
brw-rw---- 1 root disk 3, 5 Aug 24 02:00 hda5
brw-rw---- 1 root disk 3, 6 Aug 24 02:00 hda6
brw-rw---- 1 root disk 3, 7 Aug 24 02:00 hda7
brw-rw---- 1 root disk 3, 8 Aug 24 02:00 hda8
brw-rw---- 1 root disk 3, 9 Aug 24 02:00 hda9
[backup@sol /dev]$ id backup
uid=501(backup) gid=501(backup) groups=501(backup),6(disk)
backup is a member of group disk, which does have read/write ability on all
hda devices. Is there any other place I should look where there could be a
permissions problem?
> 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.
>
I just looked at the Dump Stats, and this is what it shows:
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-------------------------- -------------------------------------- ----------
----
diamond rd/c0d0p1 1 7180 1120 15.6 0:13 87.8 N/A
N/A
diamond rd/c0d0p7 1 31010 12832 41.4 1:51 116.1 N/A
N/A
diamond rd/c0d1p1 0
FAILED --------------------------------------------
diamond rd/c0d1p5 0
FAILED --------------------------------------------
diamond rd/c0d1p6 2 5460 384 7.0 0:49 7.8 N/A
N/A
krypton wd0a 1 164 32 19.5 0:02 13.0 N/A
N/A
krypton wd0d 1 10876 3296 30.3 0:18 183.0 N/A
N/A
krypton wd0h 1 3952 480 12.1 0:58 8.3 N/A
N/A
ns1 sda1 1 8850 960 10.8 0:18 53.5 N/A
N/A
ns1 sda5 0
FAILED --------------------------------------------
ns1 sda6 1 2760 544 19.7 0:12 46.6 N/A
N/A
ns1 sda7 1 16390 6624 40.4 1:01 108.0 N/A
N/A
sol -dian/IISsites 1 52192 52192 -- 9:24 92.6 N/A
N/A
sol hda1 0
FAILED --------------------------------------------
sol hda5 0
FAILED --------------------------------------------
sol hda6 0
FAILED --------------------------------------------
sol hda7 0
FAILED --------------------------------------------
tigereye hda1 1 18200 1888 10.4 0:13 145.9 N/A
N/A
tigereye hda4 0
FAILED --------------------------------------------
It looks to me like it is not writing anything to tape. I checked the
permissions on that, and the user backup does have write access on
/dev/nst0. So why would it not be writing to tape? I am pretty new to
Amanda, and I did not originally set up this system. So I am learning as I
fix.
Thanks in advance.
