> I'm using rsync to do an incremental backup of my desktop here, to a
> remote server as follows:
>
> #/usr/bin/bash
>
> old=$(date -d 'now - 1 week' +%Y-%m-%d)
> new=$(date +%Y-%m-%d)
>
> rsync -avP --delete --link-dest=../$dir /home/bakers
> bak...@perturb.org:/home/bakers/backup/$new/
>
>
In <4e03c170.2020...@perturb.org>, on 06/23/11
at 03:42 PM, Scott Baker said:
Hi,
>If it were local that would be easy. This is remote (via SSH), so I'd
>have to login before I run rsync to verify that directory is that. I was
>hoping I could save that step since rsync is already doing all th
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 "dai
Scott Baker (sc...@perturb.org) wrote on 23 June 2011 15:30:
>I'm using rsync to do an incremental backup of my desktop here, to a
>remote server as follows:
>
>#/usr/bin/bash
>
>old=$(date -d 'now - 1 week' +%Y-%m-%d)
>new=$(date +%Y-%m-%d)
>
>rsync -avP --delete --link-dest=../$dir /home
On 06/23/2011 03:40 PM, Lancashire, Pete wrote:
> pretty easy to put a wrapper around the script or add it ..
If it were local that would be easy. This is remote (via SSH), so I'd
have to login before I run rsync to verify that directory is that. I was
hoping I could save that step since rsync is
