Differences
This shows you the differences between two versions of the page.
en:services:storage_services:backup:tsm:anleitungen:inclexcl [2015/10/27 15:24] – created bnachtw | en:services:storage_services:backup:tsm:anleitungen:inclexcl [2024/09/09 10:57] (current) – [Notice] jbruene | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Using INCLude/ | ||
+ | ===== Notice===== | ||
+ | |||
+ | For creating Include and Exclude rules the [[https:// | ||
+ | |||
+ | **NOTICE:** | ||
+ | These examples are for Unices, but the statements are somehow identical on Windows. (''/'' | ||
+ | The configuration therefore will be in " | ||
+ | |||
+ | <WRAP center round important 90%> | ||
+ | The configuration of Include, but especially **'' | ||
+ | |||
+ | **//The GWDG//** therefore can only give suggestions and recommendations for creating rules, **//but is not taking any responsibility for the correctness of examples// | ||
+ | |||
+ | Please verify your chosen rules before use, either by a backup with the option //preview// in the GUI or calling //dsmc backup preview//! | ||
+ | </ | ||
+ | |||
+ | ===== Using Wildcards and Special Chrarcters ===== | ||
+ | |||
+ | TSM allows the usage of Wildcards in In- and Exclude rules: | ||
+ | * ''?'' | ||
+ | * '' | ||
+ | |||
+ | * ''/ | ||
+ | < | ||
+ | Representing all directories '' | ||
+ | < | ||
+ | Is representing all '' | ||
+ | |||
+ | * Groups of characters can be summed as a regular expression : '' | ||
+ | |||
+ | |||
+ | If a file or directory name includes special characters, they have to be masked | ||
+ | * Usually whitespaces can be captured in quotation marks:< | ||
+ | * The special characters < | ||
+ | * To Exclude the directory < | ||
+ | |||
+ | ===== Outsource Include/ | ||
+ | |||
+ | In- and exclude rules can get extensiv fast and therefore will substantially affect the configuration readability. | ||
+ | In this state or if you want to group rules you may find it helpful to outsource these rules in another or multiple other files. | ||
+ | These files can be imported into the " | ||
+ | Example: | ||
+ | INCLExcl | ||
+ | INCLExcl | ||
+ | INCLExcl | ||
+ | |||
+ | |||
+ | <WRAP center round important 90%> | ||
+ | Using '' | ||
+ | </ | ||
+ | |||
+ | ===== Hierarchy of InExClude ===== | ||
+ | |||
+ | * Generally the TSM client works through the '' | ||
+ | * The **rules which match first will be applied**, rules matching later may won't affect (See Example1). | ||
+ | <WRAP center round tip 90%> | ||
+ | === Example1: === | ||
+ | |||
+ | include / | ||
+ | exclude / | ||
+ | => The file '' | ||
+ | |||
+ | === Example2: === | ||
+ | |||
+ | exclude / | ||
+ | include / | ||
+ | => The file '' | ||
+ | </ | ||
+ | |||
+ | |||
+ | * Rules which exclude entire // | ||
+ | * Rules in a separate file will be applied at that time where the '' | ||
+ | ===== Management Classes ===== | ||
+ | |||
+ | The Management Class on the TSM server, which should be used for the backup can be managed also by the include rules: | ||
+ | include <path or file | search pattern> < | ||
+ | |||
+ | This feature applies only in individual cases at the backup service by GWDG. | ||
+ | If so, we will contact you personally. | ||
+ | |||
+ | ===== Compression ===== | ||
+ | |||
+ | All data will be compressed due to sever side default settings which enable the data transfer compression. | ||
+ | Compressed data (e.g. '' | ||
+ | This will most likely result in a high computational load rather than result in data reduction. | ||
+ | |||
+ | To avoid this unnecessary load all compressed data should be excluded from compression. | ||
+ | The relevant rules should be applied to the end of the file '' | ||
+ | (See [[en: | ||
+ | |||
+ | // | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | exclude.compression | ||
+ | \\ | ||
+ | ===== Encryption ===== | ||
+ | |||
+ | TSM supports file encryption before sending the data to a server. Beside the indisputable advantages the encryption comes with some disadvantages as well: | ||
+ | * The encryption is preventing every access to the data. Even from the TSM administrator. | ||
+ | * There is no way to decrypt the data if the password is lost! | ||
+ | Some disadvantages can be neglected: | ||
+ | * The compression rate is usually low. | ||
+ | * Functions as //subfile backup// or //client side deduplictaion// | ||
+ | |||
+ | Encryption can be used by defining rules for the files which should be encrypted. Therefore, you have to use the keyword //encrypt// with an include statement, e.g.: | ||
+ | |||
+ | include.encrypt /home/.../* | ||
+ | exclude.encrypt / | ||
+ | |||
+ | \\ | ||
+ | ===== Excluding TSM files ===== | ||
+ | |||
+ | Backing up the TSM directories is in general not very useful. | ||
+ | Therefore, it could be excluded by '' | ||
+ | Somehow, if the configuration files should be backed up, two approaches are possible: | ||
+ | - The files could be saved at a separate path and only have a symlink / shortcut in the TSM client directory. The TSM directory is excluded as mentioned above. | ||
+ | - Using wildcards instead of '' | ||
+ | |||
+ | exclude / | ||
+ | include / | ||
+ | include / | ||
+ | include / | ||
+ | \\ | ||
+ | ===== Server Side Include-Exclude Rules ===== | ||
+ | |||
+ | Server sided in- exclude rules are overriding the client side configuration. | ||
+ | The GWDG largely dispenses server sided rules | ||
+ | since only the administrator can usefully define the files to be excluded or encrypted. | ||
+ | |||
+ | |||
+ | At the present time (date of this text) only the management class //3COPIES// is specified to back up the //system state// (Windows only) to limit the amount of //system state// versions by the number of three. | ||
+ | Relevant only for //Bare Metal// restores, the //system state// uses an excessive amount of storage. | ||
+ | The system restore points in //Windows// providing an easier way for restoring older system states on running systems. |