meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
sw:urbackup:vera_crypt [2023/06/19 16:08] – created niziaksw:urbackup:vera_crypt [2023/06/19 16:25] (current) niziak
Line 4: Line 4:
  
 ===== VC container file incremental backup ===== ===== VC container file incremental backup =====
 +
 +In result this is not incremental backup. Every backup is a full backup, but only changes are transferred.
  
 ==== Setup ==== ==== Setup ====
Line 18: Line 20:
 Urbackup server: Urbackup server:
   * Backup storagae on BTRS file system   * Backup storagae on BTRS file system
 +  * Image backup storage set to ''Raw copy-on-write file” (COW)''
  
 ==== Results ==== ==== Results ====
Line 28: Line 31:
     * every next backup is a reflink-copy of previous one (it points to the same data), and only changed blocks are modified     * every next backup is a reflink-copy of previous one (it points to the same data), and only changed blocks are modified
       * so with our example setup next backup create new directory with 32GB .raw file, but it only takes few MB more data on BTRS.       * so with our example setup next backup create new directory with 32GB .raw file, but it only takes few MB more data on BTRS.
-    * every backup looks like full backup - 32GB .raw file with full disc image is present. +    * There is **no real incremential backups chain**. There is no risk of loosing one element from chain. Every backup looks like full backup - 32GB .raw file with full disc image is present. **No need to refresh ''full backup''** every n-th backup. It is possible too keep unfinished number of incremental backups without risk.
-    no need to refresh ''full backup'' every n-th backup. There is **no differential backups chain**. It is possible too keep unfinished number of incremental backups without risk.+