I am running Amanda 2.4.1-p1 on some Compaq tru64 boxes (vers 4.0D) and
using dump/vdump to run my backups. Last weekend I switched to an automated
failover of two of my systems (ASE) which required me to carve up my shared
disk array and create separate filesystems that were then assigned to
services on the two systems. If one system fails the other will pick up it's
IP based service and mount the data filesystems from the failed system.
To do this I have had to remove the disks from /etc/fstab, so that the
failover software has control of mounting and dismounting the data disks. I
am now receiving this error in the sendsize.debug log:
dump: Bad file system specification or bad file system. The raw device must
dump: be entered when the file system's pathname has not been entered in the
dump: fstab file. A bad file system is reported when the the magic number
dump: is not found in the super block.
dump: The ENTIRE dump is aborted
.....
(no size line match in above dump output)
Which results in the data filesystems not being backed up (only the system
stuff that is still in /etc/fstab)
This is how my disklist is set up (for one of the systems):-
##SYSA
sysa / nocomp-root
sysa /usr comp-high
sysa /usr/adm01 nocomp-high
sysa /usr/adm02 nocomp-high
sysa /usr/adm03 nocomp-high
sysa /usr/adm04 nocomp-high
#203.2.nn.nnn /usr/adm01 nocomp-high
#203.2.nn.nnn /usr/adm02 nocomp-high
#203.2.nn.nnn /usr/adm03 nocomp-high
#203.2.nn.nnn /usr/adm04 nocomp-high
#sysa /dev/rz19c nocomp-high
#sysa /dev/rzb19c nocomp-high
#sysa /dev/rzb18c nocomp-high
and the same for the 2nd system- the commented lines are some of the
alternatives I have tried. The ip address is the address of the service
these filesystems are assigned to.
I have added the disks back into the /etc/fstab for the moment so that I can
backup until I get a long term solution.
Any suggestions would be appreciated.
Regards, John
John Gormley
Senior Unix Systems Administrator
Southern Cross University
Lismore NSW
AUSTRALIA
[EMAIL PROTECTED]
