Re: Disk mirroring - rsync
Alvin Oga wrote:
> each time youupdate lilo.conf or add new kernels and modules,
> you'd have to remember to rerun lilo on the backup disk
> ( assuming that is to be a hard disk bootable replacement
> - order of magnitude easier ot do raid1 in this case
I don't think that I'd copy the kernel and the bootloader config files.
I mean, it is sufficient to copy them once and have the disk bootable,
and do the rest (data, applications) using rsync.
> - if you just want ot backup your main hd to a mirror/backup disks...
> there is no reason to worry about boot issues as it will not be
> able to boot ... ( /etc/fstab, /etc/lilo.conf, etc would be wrong,
Well, I think it depends how bad the first disk failure would be. If it
were a total failure, then the SCSI number (the /dev/sd<x>) would be
changed; /etc/fstab, etc. (on the second disk) would be all right. But
if it were a data failure, then the setup wouldn't work.
I think it would be easy to make the second disk bootable, especially if
it's done from a floppy. The difficult thing is how to predict what kind
of failure you expect from the first disk; hardware failure?; corrupted
filesystem? data loss? Each one of it needs a different setup in order
to make the second disk bootable. My other concern is that, if I make
the file copying done by cron, how would I know that the copy is not
done while the first disk is about to fail? I'd end up with another
non-working disk. It seems that copying it during the night is not a
good idea. Am I right? Am I wrong?
Oki
Reply to: