Jump to content

mattengland

Members
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mattengland

  • Rank
    Newbie
  1. In the Retrospect 7.6.x docs I don't see any mention of needing to rerun full backups (in the Normal/Progressive Backup scheme). I'm hoping this is because it (Retrospect) can support "reverse incremental" backups, as described below, making restore times reasonable even after many successive, Progressive Backups. Can Retrospect do this ("reverse-incremental" backups for disk-based backup sets)? If not, how does one address the restore performance lag due to a "stack of incrementals" that are only stored "forward" (instead of "backward") in time? And/or where can I find out policies and scheduling tricks/suggestions for re-running a full backup? [An aside: This presumably only works for disk-based backup sets, for the "reverse incremental merge" operation on the backend server calls for all the data to be stored in a contiguous device, instead of say storing incrementals on separate tapes.] Confused? See how rdiff-backup works, explained below (aka "reverse diffs"). References: * http://en.wikipedia.org/wiki/Incremental_backup#Reverse_incremental * http://www.hs4cl.com/2008/07/02/reverse-incremental-backups-and-rdiff-backup/ * http://www.nongnu.org/rdiff-backup/
  2. I'm a new user. Retrospect 7.6.x and it's documentation uses the terms "restore" and "retrieve" operations seemingly interchange-ably, but inconsistently. (eg, the docs say "restore" some places where the GUI says "retrieve.") Is there any fundamental different between "restore" and "retrieve"? Thanks for any help, -Matt
×