On Thu, 2003-07-17 at 13:18, Reuben D. Budiardja wrote: > On Thursday 17 July 2003 12:47 pm, Bret Hughes wrote: > > On Thu, 2003-07-17 at 08:27, Reuben D. Budiardja wrote:
> > > I have a shell access (SSH) on both machines, the source machine, and the > > > target machine. My local machine is the target machine. So I think > > > something like 'rsync' should probably work, combine with something else > > > for scheduling (cron maybe). But I am not sure how to stop after the > > > first ~500 MB is transferred, and continue the next day (of course the > > > number 500MB does not have to be exact, it could be a rough rounding, > > > because it's probably easier to stop after one file is completed, than > > > stop in the middle of the file). > > > > I would set up individual jobs of the approximate size and use rsync > > (over ssh of course) on them for the initial runs and then run rsysnc > > daily to keep them in sync. > > But that would require me to manually calculate the size of directories (eg. > with 'du'). It would be tedious since it's a lot of directories and sub-dir. > I am wondering if there's a way to automate the process. Not sure why I did not thing of this before. How bout simply running rsync against the whole shebang but having another cron job kill rysnc at the end of your time window? The next day, rsync should pickup where it left off even in the middle of a file IIRC. You can set rsync to compress on the fly or let ssh do the compression. I am not sure that it is as efficient as tar but should get you going quickly. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
