Skip to main content

JetBackup Incremental

Comments

3 comments

  • cPRex Jurassic Moderator

    Hey there!  I reached out to JetBackup with this question and got this response - let me know if that helps!

    Incremental backups in JB5 do not re-generate a "full" backup at the end of the cycle. For Local/SSH (Legacy) destinations, these destinations perform incremental backups using the linux standard rsync utility. JetBackup is using standard rsync which uses hardlinks to only pass incremental changes and save disk space. Hardlinks are essentially a reference to the same file by the inode number, they are not duplicated files. As long as there's at least one link pointing to the inode, the data will remain intact and won't take up additional space. (https://www.redhat.com/sysadmin/linking-linux-explained)
    All other destinations in JB5 use our own backup engine which tracks new/changed files in an SQLite database and links the file IDs together to form the snapshot. Our automatic backup cleanup and Integrity Check validates the integrity of the backups and stored files and if any files are found missing, any dependent snapshots will be marked as damaged and JB5 will automatically re-upload those files in the next run.

    0
  • Patrik Johnsson

    Thanks cPRex

    0
  • cPRex Jurassic Moderator

    Sure thing!

    0

Please sign in to leave a comment.