MirrorArchive strategy plausible
Captain Dondo True. And I should preface this by saying that I have little sympathy with the OP on just about anything he says, but this is one...
I'm trying to develop an offsite mirror and archive strategy for two linux boxes I have. I have an offsite machine with 3 disks. One is a big disk that I use for incremental archives. The other two disks are mirrors of disks I have in my primary linux machines. I'm using rsync to do the mirroring and tar to do the incremental archiving.
My question has to do with linux recognizing the the file systems on the two mirror disks. Since they will have boot and swap areas, will this confuse the machine's file system? Can I just map them to something local and ignore the boot particians?
My goal is to be able to take a disk out of my backup machine and plug it into the primary machine if it fails. I'll of course have to do database dumps on the primaries and restores on the mirrors to get the databases properly. Either that or have some sort of replication system which may be more bandwidth friendly.
I'm also a bit concerned about file ownerships. I guess this is an rsync isssue, but I'm hoping it will use ownership numbers that will become relevant only when the mirror drives are booted. Is that what will happen?
No. I'm not knocking Linux in general, just some of its code writers, and am grateful for their work even while I complain about certain aspects of it. I was cleaning my...
Mirroring-Archiving is a very complex issue, I know. Thanks for any help.
Linux groups from Newsgroups