>When I run amdump and then amstatus, some of the 'backup jobs' issue the >following error/warning (which is it): > >localhost:/backup/dump27/. 0 [dumps too big, but cannot >incremental dump new disk]
That's an "error", as in, that file system is not going to be backed up. Amanda is telling you that after it made it's scheduling choices, the total size was larger than the amount of tape you had given it to work with. Normally it would demote some full dumps to incrementals until it had enough space, however, this disk is "new" to Amanda (never been dumped before) and so it cannot fall back to an incremental until the first full dump is completed. This error should work itself out after a few runs. Presumably there are a lot of "new" disks right now for you and as soon as Amanda gets a full dump of each, they will be candidates for incrementals which (again, presumably) will be small enough to leave room for full dumps of some other new disks. After everything gets a full dump once, Amanda will begin shifting the schedule around to balance things out. >Peter Normann John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
