from the rsync man page:

--del                   an alias for --delete-during
--delete                delete files that don't exist on sender
--delete-before         receiver deletes before transfer (default)
--delete-during         receiver deletes during xfer, not before
--delete-after          receiver deletes after transfer, not before
--delete-excluded       also delete excluded files on receiver



On 4/25/06, Colin Corr <[EMAIL PROTECTED]> wrote:
> Garrett P. Taylor had this to say on 04/25/2006 10:11 PM:
>
> >Proposed Solution:
> >Build an identical server with another huge array. Put it out at a
> >remote branch. Have a nightly cron job that runs rsync or something to
> >copy over new data or files which have been changed (but to not
> >replicate deleted files).
> >
> >Question:
> >Does anyone have any suggestions or prior experience they wish to share?
> >
> >
> >
> Garrett,
>
> Your proposed solution sounds good and practical. If you are looking for
> a solid example of how to do this, then...
>
> A buddy of mine on SCLUG wrote this rsync script (in part with contribs)
> to do the job you mention. It is pretty slick (and fairly well
> commented), and is used extensively in my smb and personal backup
> schema. It allows you to perform full backups over an SSH connection, so
> you can do it remotely and securely as needed (assuming your backup
> server is secure).
>
> Here is a link to the script:
> http://mirror.actusa.net/pub/sample-files/mirror.dist
>
> The basic default schema is:
> take snaphosts every 4 hours and store them for 7 days before rolling
> them off. Backup consists of a an initial full disk image (first sync)
> plus hardlinks for changes in 4 hour increments (all defined by cli
> params and run as a cron job). So, it is fairly gentle on disk space.
> You can obviously set the script to run for more than 7 days, if your
> storage space allows. The major missing feature based on your
> requirements is the non replication of deleted files... which it
> doesn't... but you will need to set your rollover policy accordingly and
> possibly add some diff logic to alert you of such changes. It works
> quite well on Debian based systems, and I must admit that I have not
> done much testing on non-Debian distros... so your results may vary...
> if only slightly...
>
> HTH,
>
> Colin
>
>
>
>
> --
> ^X^C
> q
> quit
> :q
> ^C
> end
> x
> exit
> ZZ
> ^D
> ^Z
> ^K^B
> ?
> help
>
>
> _______________________________________________
> RLUG mailing list
> [email protected]
> http://lists.rlug.org/mailman/listinfo/rlug
>

_______________________________________________
RLUG mailing list
[email protected]
http://lists.rlug.org/mailman/listinfo/rlug

Reply via email to