of successful daily backups and 4 months of
depth backups.
--
Larry Irwin
Email: lrir...@alum.wustl.edu
On 06/26/2018 04:36 PM, Dan Stromberg via rsync wrote:
On Tue, Jun 26, 2018 at 12:02 PM, Дугин Сергей via rsync
mailto:rsync@lists.samba.org>> wrote:
I am launching a
of the process at sites with less than perfect internet service)
--
Larry Irwin
Email: lrir...@alum.wustl.edu
On 06/22/2016 09:20 PM, Bell, Robert (CSIRO IM, Docklands) wrote:
Folks,
Am 20.06.2016 um 22:01 schrieb Larry Irwin (gmail):
> The scripts I use analyze the rsync log af
years and, in my environment, the 10
copies take about 4 times the space of a single copy.
(we do complete copies of linux servers - starting from /)
If there's a good spot to post the scripts, I'd be glad to put them up.
--
Larry Irwin
Cell: 864-525-1322
Email: lrir...@alum.wustl.edu
Skype
The device names might be different - the mount folder may be different
- etc...
But the idea works. - With a new, blank drive, you could recreate the
partitions using fdisk, reverse the dd commands, boot and then work on
getting the second partition back up and running.
--
Larry Irwin
On 07/17/2015
are still running...
Any ideas would be greatly appreciated.
Thanks,
Larry Irwin
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart
We handle it via 2 scripts.
One script (on the server side) does daily rotations mid-morning on
successfully completed rsyncs from the night before.
(i.e. removes daily.7, moves daily.6 to daily.7, etc... - if the rsync
was successful)
The client side always sends to daily.0 and uses the
I am using a configuration file on rsync client machines to list the files to
exclude for that machine.
When I get a log containing vanished files, I get on that machine, confirm they
are temp files (like pirnt spool files, etc.), and add them to the exclude list:
So, I have a file like
to generate the initial image of a client
machine...
Just keep running the rsync process over and over until the first image is
completed.
Then the process reduces to a minimal transfer/execution time from that
point forward.
Especially when using the --link-dest option...
Hope that helps!
Larry