omv7:omv7_plugins:borgbackup

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
omv7:omv7_plugins:borgbackup [2024/05/05 19:20] – [What is the basic operation of BorgBackup?] chenteomv7:omv7_plugins:borgbackup [2025/01/11 13:40] (current) – [Create] chente
Line 202: Line 202:
 Do not confuse data integrity of an ARCHIVE in a REPOSITORY with data integrity of the backup source (your file system on the server where the data from which the backup is made is stored).<br> Do not confuse data integrity of an ARCHIVE in a REPOSITORY with data integrity of the backup source (your file system on the server where the data from which the backup is made is stored).<br>
 <b>Borgbakup does not in any way guarantee the integrity or bitrot of the backup source data.</b> Only integrity checks are performed on the data backed up in the REPOSITORY. If the data is corrupted at the source, it will end up irreparably corrupted in the backup.<br> <b>Borgbakup does not in any way guarantee the integrity or bitrot of the backup source data.</b> Only integrity checks are performed on the data backed up in the REPOSITORY. If the data is corrupted at the source, it will end up irreparably corrupted in the backup.<br>
-If you need to guarantee the integrity of the files in your file system you must use other means, such as a COW file system such as ZFS or BTRFS. <b>Borgbackup is not a substitute for a COW file system</b> for user data.<br>+If you need to ensure the integrity of files on your file system, you should use other means, such as a COW file system such as ZFS or BTRFS or a parity checking system such as SnapRaid. <b>Borgbackup is not a substitute for a COW file system</b> for user data.<br>
 </tr></table></body></html> </tr></table></body></html>
  
Line 356: Line 356:
 ''sudo omv-salt deploy run borgbackup'' ''sudo omv-salt deploy run borgbackup''
  
 +Example: setting the starting hour to 4 would mean the following:
 +  * yearly jobs start on January 1 at 4
 +  * monthly jobs start on the first day of the month at 4:30 (4 + 30 mins)
 +  * weekly jobs start on Mondays at 5 (4 + 1 hour)
 +  * daily jobs start at 5:30 (4 + 1 hour + 30 mins)
 +  * hourly start at 5 mins after the hour every hour
 ---- ----
  
Line 471: Line 477:
  
 {{ :omv7:omv7_plugins:borgbackup7-8.jpg?direct&600|Create Archive peter}} {{ :omv7:omv7_plugins:borgbackup7-8.jpg?direct&600|Create Archive peter}}
-The second step is to create a //ARCHIVE//. Since we have different timing needs for Mary's and Peter's folders we will need to create two separate //ARCHIVES// that will be stored in the same //REPOSITORY//. Each of them defines where the content we want to back up is, how often and how many versions we want to maintain. We start with the //ARCHIVE// in the mary folder: +The second step is to create a //ARCHIVE//. Since we have different timing needs for Mary's and Peter's folders we will need to create two separate //ARCHIVES// that will be stored in the same //REPOSITORY//. Each of them defines where the content we want to back up is, how often and how many versions we want to maintain. 
-  * In the SERVICES > BORGBACKUP > REPOS tab, press the CREATE button and establish the following configuration: + 
-    * ENABLE: We activate this button so that the programming is active. +We start with the //ARCHIVE// in the mary folder. In the SERVICES > BORGBACKUP > REPOS tab, press the CREATE button and establish the following configuration: 
-    * NAME/PREFIX: ''mary'' +  * ENABLE: We activate this button so that the programming is active. 
-    * REPO: We select the //REPOSITORY// that we have created, ''borg_local_repo'' +  * NAME/PREFIX: ''mary'' 
-    * COMPRESSION TYPE: ''lz4'' (to compress the backup content)+  * REPO: We select the //REPOSITORY// that we have created, ''borg_local_repo'' 
 +  * COMPRESSION TYPE: ''lz4'' (to compress the backup content)
   * COMPRESSION RATIO: ''9'' (highest compression value)   * COMPRESSION RATIO: ''9'' (highest compression value)
   * ONE FILESYSTEM ONLY: We activate this button since we only want to backup a folder in a single file system.   * ONE FILESYSTEM ONLY: We activate this button since we only want to backup a folder in a single file system.
   * NO ATIME: We activate this button to avoid backing up versions with different access times.   * NO ATIME: We activate this button to avoid backing up versions with different access times.
   * INCLUDES: ''/srv/dev-disk-by-uuid-eb24d436-abba-4190-a343-4741b86fd2a7/data/documents/mary''   * INCLUDES: ''/srv/dev-disk-by-uuid-eb24d436-abba-4190-a343-4741b86fd2a7/data/documents/mary''
-  * EXCLUDES: (We leave it blank, we don't want to exclude anything from the peter folder)+  * EXCLUDES: (We leave it blank, we don't want to exclude anything from the mary folder)
   * RETAIN HOURLY: ''8'' (the value 8, non-zero, determines that backups are made every hour since it is the first non-zero value and the backups of the last 8 hours will also be kept)   * RETAIN HOURLY: ''8'' (the value 8, non-zero, determines that backups are made every hour since it is the first non-zero value and the backups of the last 8 hours will also be kept)
   * RETAIN DAILY: ''7'' (the value 7 determines that the last 7 daily backups will be retained)   * RETAIN DAILY: ''7'' (the value 7 determines that the last 7 daily backups will be retained)
Line 512: Line 519:
  
 To see the versions of the backups generated so far, select the //REPOSITORY// and press the LIST button. To see the versions of the backups generated so far, select the //REPOSITORY// and press the LIST button.
 +\\ 
 +\\ 
 +\\
 ---- ----
  
  • omv7/omv7_plugins/borgbackup.1714936856.txt.gz
  • Last modified: 2024/05/05 19:20
  • by chente