Gary Nielson wrote:
> Linux Journal recently had a way to copy disks:
>
> tar clf - . | ( umask 0; cd /dir/to/copy/to; tar xvf - )
>
> c = create
>
> l = stay on local file system (don't cross
> filesystem boundaries)
>
> f = file (the next argument is the
> name of the tarfile or "-")
>
> - = write to standard out or
> read from standard in
>
> x = extract
>
> v = verbose
>
> "umask 0" ensures that the new files have the same permissions
> as the old ones.
>
> I tested it and it seemed to work great. What I am wondering is using this
> with two identical drives on the same machine as a way to routinely back
> up the first drive to the second. But in subsequent backups, how could I
> employ the "find" command to just back up files that have changed since
> the last backup?
I use similar commands, executed by cron in the middle of every night,
to back up my user directories. The one big disadvantage is that it does
not delete files on the copy that have you have deleted or moved on the
original. But for me that is not much of a problem; I just live with it.
But don't use this as your only backup method. What happens if something
happens to that computer, like a failed power supply sending a current
surge into both disks? Or it is stolen. Or, like I did, you accidently
knock the computer over, not hurting the computer but instantly reducing
the harddisks to scrap metal.
Duane
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
