linux_wiki:urbackup_server_and_client

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
linux_wiki:urbackup_server_and_client [2018/03/08 00:59]
billdozor [Client CLI] 		linux_wiki:urbackup_server_and_client [2019/05/25 23:50] (current)
Line 106: Line 106:
         * Using a snapshot method, a block snapshot is made of your data and that is used for the backup. (This is typically more reliable than a straight up file copy operation)         * Using a snapshot method, a block snapshot is made of your data and that is used for the backup. (This is typically more reliable than a straight up file copy operation)
         * **1) dattobd** volume snapshot kernel module from https://github.com/datto/dattobd         * **1) dattobd** volume snapshot kernel module from https://github.com/datto/dattobd
-          * Install instructions: https://github.com/datto/dattobd/blob/master/INSTALL.md                            +          * Install instructions: https://github.com/datto/dattobd/blob/master/INSTALL.md 
-        * **2) LVM** - Logical Volume Manager snapshots           +          * Good: No extra space needed, creates copy on write special device (not tested, just read about it) 
 +          * Bad: Extra kernel module install 
 +        * **2) LVM** - Logical Volume Manager snapshots 
 +          * Good: Native snapshots (if LVM already setup on system) 
 +          * Bad: Snapshots require free space in the same volume group as the logical volume being backed up, equal to the used size. (snapshots removed after backup completes)        
         * **4) Use no snapshot** mechanism         * **4) Use no snapshot** mechanism
 +          * Good: Simple, no add-ons, no extra space required
 +          * Bad: Since it is essentially a rsync, if files are modified during backup, there could be inconsistencies.
  
   * Enable and start (should automatically do this)<code bash>systemctl enable urbackupclientbackend   * Enable and start (should automatically do this)<code bash>systemctl enable urbackupclientbackend
Line 167: Line 173:
 Login to the web console and navigate to "Settings". Login to the web console and navigate to "Settings".
  
-  * **Settings -> Server**+  * **Settings -> General -> Server**
     * Backup storage path: Full path to file system location where you want backups stored     * Backup storage path: Full path to file system location where you want backups stored
     * Server URL: Set to URL that you can access the web console (so clients can access and restore files)     * Server URL: Set to URL that you can access the web console (so clients can access and restore files)
Line 176: Line 182:
       * **Note**: Its a good idea to have a window of an hour or two in which backups will not run so cleanup jobs can run successfully.       * **Note**: Its a good idea to have a window of an hour or two in which backups will not run so cleanup jobs can run successfully.
  
-  * **Settings -> File Backups**+\\ 
 +  * **Settings -> General -> File Backups**
     * Two types of wildcards are available:     * Two types of wildcards are available:
       * *  (star) -> Matches any character, including file system path slash (forward slash for Linux, back slash for Windows)       * *  (star) -> Matches any character, including file system path slash (forward slash for Linux, back slash for Windows)
Line 200: Line 207:
       * Example<code bash>/home/;/etc/</code>       * Example<code bash>/home/;/etc/</code>
  
-  * **Settings -> Permissions**+\\ 
 +  * **Settings -> General -> Permissions**
     * Review the list of permissions and decide what you want each client to be able to do.     * Review the list of permissions and decide what you want each client to be able to do.
  
-  * **Settings -> Client**+\\ 
 +  * **Settings -> General -> Client**
     * Delay after system startup: Delay in minutes after system startup before backups can begin on clients.     * Delay after system startup: Delay in minutes after system startup before backups can begin on clients.
     * Backup window: Set the days/hours during which backups can run.     * Backup window: Set the days/hours during which backups can run.
Line 210: Line 219:
     * Perform autoupdates silently: Check if you want client software to update in the background.     * Perform autoupdates silently: Check if you want client software to update in the background.
  
-  * **Settings -> Archive**+\\ 
 +  * **Settings -> General -> Archive**
     * FIXME - to add when I get around to it     * FIXME - to add when I get around to it
  
-  * **Settings -> Alerts** +\\ 
-    * FIXME - to add when I get around to it+  * **Settings -> General -> Alerts** 
 +    * E-Mail addresses: enter email address(es) semi colon separated to get alerts. 
 +    * Send ok mail after backup status goes from not ok to ok: check this to get the recovered email.
  
-  * **Settings -> Internet**+\\ 
 +  * **Settings -> General -> Internet**
     * FIXME - to add when I get around to it     * FIXME - to add when I get around to it
  
-  * **Settings -> Advanced** +\\ 
-    * FIXME - to add when I get around to it+  * **Settings -> General -> Advanced** 
 +    * Most defaults are good settings. 
 +    * Database cache size: 512 MB    (I increased this from 200) 
 +    * Run backups with background priority: Check this to not impact the clients as much when backups run. 
 + 
 +\\ 
 +  * **Settings -> Mail** - Google SMTP example 
 +    * Mail server name: smtp.gmail.com 
 +    * Mail server port: 587 
 +    * Mail server username: yourgoogleaccount@gmail.com 
 +    * Mail server password: [[https://security.google.com/settings/security/apppasswords|generate an application password here]] 
 +    * Sender E-mail Address: yourgoogleaccount@gmail.com 
 +    * Send mails only with SSL/TLS: Checked 
 +    * Send test mail to this email: yourgoogleaccount@gmail.com
  
 ===== Server CLI ===== ===== Server CLI =====
Line 245: Line 271:
       * LVM snapshots<code bash>create_filesystem_snapshot=lvm_create_filesystem_snapshot       * LVM snapshots<code bash>create_filesystem_snapshot=lvm_create_filesystem_snapshot
 remove_filesystem_snapshot=lvm_remove_filesystem_snapshot</code> remove_filesystem_snapshot=lvm_remove_filesystem_snapshot</code>
-      * No shapshots (regular file copy)<code bash>create_filesystem_snapshot=/usr/local/share/urbackup/filesystem_snapshot_common +      * No shapshots<code bash>rm /usr/local/etc/urbackup/snapshot.cfg 
-remove_filesystem_snapshot=/usr/local/share/urbackup/filesystem_snapshot_common</code>+touch /usr/local/etc/urbackup/no_filesystem_snapshot</code>
   * Restart the backend client service<code bash>systemctl restart urbackupclientbackend</code>   * Restart the backend client service<code bash>systemctl restart urbackupclientbackend</code>
  
Line 264: Line 290:
     * Backup Status<code bash>urbackupclientctl status</code>     * Backup Status<code bash>urbackupclientctl status</code>
     * Start a full backup<code bash>urbackupclientctl start --full</code>     * Start a full backup<code bash>urbackupclientctl start --full</code>
-    * Start an incremental<code bash>urbackupclientctl start --incremental</code>+    * Start an incremental backup<code bash>urbackupclientctl start --incremental</code>
  
 \\ \\
Line 278: Line 304:
     * Add directory to backup list<code bash>urbackupclientctl add-backupdir --path /path/here/</code>     * Add directory to backup list<code bash>urbackupclientctl add-backupdir --path /path/here/</code>
     * Remove directory from backup list<code bash>urbackupclientctl remove-backupdir --path /path/here/</code>     * Remove directory from backup list<code bash>urbackupclientctl remove-backupdir --path /path/here/</code>
 +    * **Warning**: If you modify directories to be backed up from an individual client (add or remove), it will no longer use the global file backup settings.
  
 ---- ----
 +
 +====== Mirroring the Backups ======
 +
 +The backup location on the server can be rsync'ed to another location to create a backup of the backups.
 +
 +This is useful if you were to attach removable storage to the server, run the rsync of the latest backups, and take the removable storage offsite.
 +
 +Due to urbackup's space saving methods, rsync'ing the most current backup with the correct rsync options will provide the most accurate mirror.
 +
 +Example
 +  * Urbackup location: /home/urbackup/
 +  * The clients directory has symlinks to the latest backups: /home/urbackup/clients/
 +  * Rsync example: sync the latest backups to an external drive<code bash>/usr/bin/rsync --archive --partial --progress --delete --copy-links -h /home/urbackup/clients/ /mnt/usb-storage/</code>
 +
 +----
 +
  • linux_wiki/urbackup_server_and_client.1520488782.txt.gz
  • Last modified: 2019/05/25 23:50
  • (external edit)