Changes

From SME Server
Jump to navigationJump to search
1,693 bytes added ,  00:07, 2 August 2009
Line 171: Line 171:       −
===Adding Directories and Files to the list of backup inclusions===
+
===Adding/Excluding Directories and Files from the backup list===
    
{{Warning box|The e-smith-backup panel is designed to be used as a full disaster recovery backup & restore method for your sme server, and as such relies on the correct directories being included in the backup. Do not delete any of the default directories from 40go-into as these are all essential for a successful full Restore of your backup to a clean install of the sme server operating system (you will need to reinstall add on apps or contribs). You can safely add directories eg /opt, as indicated, but that should typically be the extent of changes made.}}
 
{{Warning box|The e-smith-backup panel is designed to be used as a full disaster recovery backup & restore method for your sme server, and as such relies on the correct directories being included in the backup. Do not delete any of the default directories from 40go-into as these are all essential for a successful full Restore of your backup to a clean install of the sme server operating system (you will need to reinstall add on apps or contribs). You can safely add directories eg /opt, as indicated, but that should typically be the extent of changes made.}}
 
+
====Adding Files and Directories====
 
The default backup does not include /opt
 
The default backup does not include /opt
   Line 193: Line 193:  
It is also prudent to do a test full restore and verify that /opt (& all other backed up directories & files) are restored, as anticipated.
 
It is also prudent to do a test full restore and verify that /opt (& all other backed up directories & files) are restored, as anticipated.
 
If something is wrong with your backup or restore procedures, then required files may not be backed up and restored, so it is wise to do a test full backup & restore to fully prove your procedures are working correctly.
 
If something is wrong with your backup or restore procedures, then required files may not be backed up and restored, so it is wise to do a test full backup & restore to fully prove your procedures are working correctly.
 +
 +
{{Note box|<tt>--include <mask></tt> will include single files into the backup when using a path (without leading '/' ) and file name for the mask, or all files matching the mask when using wildcards. Like:
 +
  --include path/to/file/sampleFileName.txt
 +
  --include "*.backMeUp"
 +
<tt>--go-into <path></tt> will include entire directories with all of it's contents (files and subdirs) into the backup. Like:
 +
  --go-into /path/to/dir/sampleDirName
 +
}}
 +
 +
====Excluding Files and Directories====
 +
As an example let's say you have an ibay called 'mirror' you don't want backed-up. To exclude this ibay from the backup list, create a custom template fragment and exclude it from the the list.
 +
 +
Create custom template fragment to exclude the unneeded files and directories
 +
  mkdir -p /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf
 +
  pico -w /etc/e-smith/templates-custom/etc/dar/DailyBackup.dcf/45prune
 +
 
 +
  --prune home/e-smith/files/ibays/mirror/cgi-bin
 +
  --prune home/e-smith/files/ibays/mirror/files
 +
  --prune home/e-smith/files/ibays/mirror/html
 +
 +
Then expand the template
 +
  expand-template /etc/dar/DailyBackup.dcf
 +
 +
Again, check your backup (eg using the mc dar plugin) to see that the ibay is not backed-up any more.
 +
 +
{{Note box|<tt>--exclude <mask></tt> will exclude single files when using a path (without leading '/' ) and file name for the mask or all files matching the mask when using wildcards, from the backup. Like:
 +
  --exclude path/to/file/sampleFileName.txt
 +
  --exclude "*.NoBackup"
 +
<tt>--prune <path></tt> will exclude entire directories with all of it's contents (files and subdirs) from the backup. Like:
 +
  --prune /path/to/dir/sampleDirName
 +
}}
    
== Some notes ==
 
== Some notes ==
167

edits

Navigation menu