X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=docs%2Fexclude.txt;h=030c06b4c47287c4bfb573d8c1fa341eca4cf0b2;hb=d3b2175e084f88c8736ad7073eacbf4670147aec;hp=cfb0f48dad5147b3555cd4bf06f71a8de67baa0d;hpb=0de2ad0a86685398621fb8ffa6990c029681bb3a;p=debian%2Famanda diff --git a/docs/exclude.txt b/docs/exclude.txt index cfb0f48..030c06b 100644 --- a/docs/exclude.txt +++ b/docs/exclude.txt @@ -44,22 +44,17 @@ Table of Contents -Note - -Refer to http://www.amanda.org/docs/exclude.html for the current version of -this document. - Introduction There are times when data needs to be excluded from a backup. When these times -arise be confident that AMANDA has this capability. (Actually it's not AMANDA, -it's tar.) There are three ways of excluding data in an AMANDA backup: +arise be confident that Amanda has this capability. (Actually it's not Amanda, +it's tar.) There are three ways of excluding data in an Amanda backup: * Exclude an individual item explicitly in the dumptype * Utilize an "Exclude List" * Do not include the data in the disklist -This document is based on AMANDA 2.4.2 and some of this might not work with +This document is based on Amanda 2.4.2 and some of this might not work with older versions. This was compiled from my personal experience and with help from the members of the amanda-users mailing list (mailto://amanda- users@amanda.org) when I was originally setting this up, to whom I wish to @@ -68,7 +63,7 @@ thank for all of their support. Please Read As far as I am able to tell the only way to exclude files or directories with -AMANDA is to use GNU-tar as the dump program (others?). The file system dump +Amanda is to use GNU-tar as the dump program (others?). The file system dump programs provided with unix systems (e.g. dump, ufsdump) get data at a raw drive level and generally do not allow exclusion of specific files or directories. @@ -83,7 +78,7 @@ The only exception that I am aware of is to just not include the data in question in the disklist. This option may not be suitable for everyone's needs and can confuse the issue some, so I have elected to include this mechanism in its own section named Do_not_include_the_data_in_the_disklist. -For the purpose of this document an AMANDA backup configuration named "exclude- +For the purpose of this document an Amanda backup configuration named "exclude- test" will be used. The machine that contains the tape drive which receives data to be archived will be referred to as "SERVER". The machine that data is being archived from will be referred to as "CLIENT". These two systems are @@ -92,7 +87,7 @@ machine. Parts of this setup are on the server and some are on the client. Note -When AMANDA attempts to exclude a file or directory it does so relative to the +When Amanda attempts to exclude a file or directory it does so relative to the area being archived. For example if /var is in your disklist and you want to exclude /var/log/somefile, then your exclude file would contain ./log/somefile. You may use one exclude file in multiple dumptypes without any restriction. @@ -100,18 +95,18 @@ You may use one exclude file in multiple dumptypes without any restriction. Before We Begin The first step that should be taken is to verify that backups are currently -working. Connect to SERVER and run amcheck as your AMANDA user, to verify that +working. Connect to SERVER and run amcheck as your Amanda user, to verify that there are no errors in the current setup. $ amcheck -cl CLIENT Output should look something like below for success: - AMANDA Tape Server Host Check + Amanda Tape Server Host Check ----------------------------- /path/to/holding-disk: 4771300 KB disk space available, that's plenty. - AMANDA Backup Client Hosts Check + Amanda Backup Client Hosts Check -------------------------------- Client check: 1 host checked in 0.084 seconds, 0 problems found. @@ -148,14 +143,15 @@ the need is to exclude multiple files or directories then use an Exclude List. The easiest way to exclude a file or directory is to specify it with the "exclude" option in the dumptype. This option accepts an argument of the file -or directory to be excluded. AMANDA allows only one exclude option in any +or directory to be excluded. Amanda allows only one exclude option in any dumptype at a time. Note -UPDATE: Recent AMANDA-releases bring the option "exclude append" which enables +UPDATE: Recent Amanda-releases bring the option "exclude append" which enables the administrator to define more than one exclusion-pattern within one dumptype -without using a exclude-list. Please look at the amanda.8-manpage for details. +without using a exclude-list. Please look at the amanda.conf.5-manpage for +details. Any path specified to be excluded must be encapsulated with quotes. Continuing with our example from above /var/log/somefile and using the same dumptype as above, the dumptype would now look like: @@ -168,7 +164,7 @@ above, the dumptype would now look like: } Next run amcheck again to verify that there are no problems with the revised -AMANDA configuration. If the data is not being excluded as expected please see +Amanda configuration. If the data is not being excluded as expected please see the Troubleshooting section below. This completes the setup of excluding an individual item in the dumptype. @@ -188,7 +184,7 @@ Connect to CLIENT and create the exclude directory as root. For example: $ mkdir -p /usr/local/etc/amanda/exclude $ cd /usr/local/etc/amanda/exclude -Next create the exclude list for AMANDA to use. You can name the exclude file +Next create the exclude list for Amanda to use. You can name the exclude file anything you wish it to be. Create a file, and in this file place all paths to files and directories that are to be excluded. Keeping with the /var example, assume that /var/log/XFree86.0.log, and /var/log/maillog need to be excluded. @@ -204,8 +200,8 @@ example: $ chmod 644 /usr/local/etc/amanda/exclude/exclude-filename This concludes the necessary configuration on the client. -Connect to SERVER and cd to the exclude-test AMANDA configuration directory. -Edit the AMANDA configuration file e.g. amanda.conf. Add an entry similar to +Connect to SERVER and cd to the exclude-test Amanda configuration directory. +Edit the Amanda configuration file e.g. amanda.conf. Add an entry similar to the following line, to the dumptype for the client in question, where the exclude-filename is the file that was created on CLIENT in the step above including the quotes. For example: @@ -222,14 +218,14 @@ The new dumptype should look something like: } Save the file. Run amcheck again to verify that there are no problems with the -revised AMANDA configuration. If amcheck succeeds then run amdump to verify the +revised Amanda configuration. If amcheck succeeds then run amdump to verify the data is being excluded correctly. If the data is not being excluded as expected please see the Troubleshooting section below. This completes the setup of an exclude list. Do not include the data in the disklist -AMANDA uses disklist entries to define which directories or partitions should +Amanda uses disklist entries to define which directories or partitions should be archived. This allows us to exclude data by just not placing the data in question in the disklist. Assume that there is a disk mounted on /example. The directory /example has five subdirectories "a", "b", "c", "d", and "e". The @@ -242,7 +238,7 @@ contain: CLIENT /examples/b exclude-test CLIENT /examples/c exclude-test -Run amcheck to verify that AMANDA is working correctly. If the data is not +Run amcheck to verify that Amanda is working correctly. If the data is not being excluded as expected please see the Troubleshooting section below. This completes the setup of using a disklist to exclude data. @@ -260,7 +256,7 @@ backup image but nothing below it. Wildcard Expansion -AMANDA has the ability to use wildcard expansion while excluding data as +Amanda has the ability to use wildcard expansion while excluding data as implemented by tar(1). The only places that wildcard expansion is allowed is in the "exclude" option in the dumptype, or in the exclude list. Some simple examples: @@ -296,7 +292,7 @@ the script. Broken gnutar? There are versions of GNU-tar that do not correctly exclude data. Version 1.12 -(plus the AMANDA patches from http://www.amanda.org) are known to work +(plus the Amanda patches from http://www.amanda.org) are known to work correctly, as does version 1.13.19 (and later). Anything else is questionable. Note @@ -331,8 +327,13 @@ then the string following the "=" is the file or directory that is currently set to be excluded. Contact the amanda-users mailing list: mailto://amanda-users@amanda.org. Subscription information is available at http://www.amanda.org. + +Note + +Refer to http://www.amanda.org/docs/exclude.html for the current version of +this document. ------------------------------------------------------------------------------- Prev Up Next -Chapter 2. AMANDA Installation Notes Home Chapter 4. Indexing with AMANDA +Chapter 2. Amanda Installation Notes Home Chapter 4. Indexing with Amanda