|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Sun, 27 Oct 1996 09:25:32 -0500 (EST) From: Info junkie <junkie@glcom.com> To: Mark Shacklette <mshack@mcs.com> cc: redhat-list@redhat.com In-Reply-To: <ML-2.3.846418767.9124.jmshack@lsmtsrvr1.lakeshore.com> Resent-From: redhat-list@redhat.com Reply-To: redhat-list@redhat.com On Sun, 27 Oct 1996, Mark Shacklette wrote: > The thread that dealt with this issue last summer mentioned cpio as a good > tool to use, and there was an article in the Linux Journal (March 1996, pp. > 44ff.) which explained how to do this using cpio. > > Essentially, the command would be (assuming the target partition is mounted as > /mnt/export): > > find / -depth -xdev | cpio --pass-through --preserve-modification-times > --make-directories --verbose /mnt/export > > This gets everything over, but avoids crossing over into mounted partitions, > which means the find will not venture to copy your CD contents, your mounted > nfs drives, your dos drives you might have mounted--only your root partition, > and all the files on it. > Ok so i guess this has been beaten to death. However, no-one mentioned that you also have to avoid copying your /mnt/export except for this response (which does so indirectly). One application i see once the contents of the hard-drive have been moved is the following scenario (via a crontab run nightly; assuming the new disk is always mounted to /mnt/export): - check which files have changed since last update. [HOW? have some hidden file which is touched everytime the backup is performed. Use some interesting combination of the find utility to find the files.] - on /mnt/export move those particular files to filename.backup.dayofweek (rotate on a weekly basis) [HOW? Just a simple cp or cpio which maintains permissions] - copy over and overwrite /mnt/export/somepath/filename with its equivalent from the other disk/partition [HOW? Just another cp or cpio which maintains permissions] - mail root the results. Anyone willing to write a script for the above? This helps in mirroring a disk so that if the first one screws up, you can replace it with the second one and keep going. You could do this by just physically moving the second drive where the first one used to be. Could you just boot off the second drive say after making zlilo on a floppy disk and entering "root=/dev/second-drive" when the first drive is physically absent? I could be re-inventing the wheel. Is there a simpler way to mirror a disk without resorting to RAID systems? cheers jamal -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! ________________________________________________________________________ http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists ------------------------------------------------------------------------ To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |