[Discuss] rsnapshot vs. rdiff-backup

[John Abreau]

I never used the hourly level, just the daily, weekly, monthly, and yearly.
I believe the higher levels were each grabbing the oldest instance of the
level immediately below it, rather than the newest instance.

i wanted the higher levels to use the newest, so that, e.g.,, the monthly
snapshot made on March 1, 2012 would be a copy of the daily snapshot from
March 1, 2012, and the yearly snapshot made on January 1, 2013 would be a
copy of the daily snapshot from January 1, 2013. That way the age of each
archival directory would be more predictable.




On Wed, Dec 4, 2013 at 11:37 AM, Richard Pieri <richard.pieri at gmail.com>wrote:

> John Abreau wrote:
>
>> I've never liked the way rsnapshot handles the additional levels of
>> snapshots. As I recall, the most recent weekly was several weeks old, the
>> most recent monthly  was always several months old, etc.
>>
>
> This suggests to me that the scheduling is off. It could be due to
> incorrectly staggered cron jobs or runs overlapping. Overlaps /will/ wreck
> the rotation cycles so it's important not to set your backup runs too close
> together. Despite the name, the "hourly" increments aren't necessarily
> hourly; I typically run them 3-6 hours apart.
>
> Tedious, like I originally wrote. :/
>
>
>  Also, when I used rsnapshot to back up dozens of servers, I found that if
>> only one portion of one server's backups failed, it would roll back
>> everything, and I'd lose backups for all servers.
>>
>
> I discovered this the hard way. It's more reliable if each node runs its
> own installation and pushes to a unique directory on the backup target.
> Trying to glom many nodes together in a single rsnapshot run is not a good
> way to do it.
>
> --
> Rich P.
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>



-- 
John Abreau / Executive Director, Boston Linux & Unix
Email: abreauj at gmail.com / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6
PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23  C2D0 E885 E17C 9200 63C6