On Thu, Nov 8, 2018 at 5:35 PM Nathan Stratton Treadway <[email protected]> wrote: > > > I haven't quite followed this whole thread, either, but have you taken a > look at > http://wiki.zmanda.com/index.php/How_To:Split_DLEs_With_Exclude_Lists > ? It may help explain some of the nuances in how things work. >
That information is very similar to the information in the example disklist file included with Amanda. > As Stefan mentioned, it would be helpeful to know what amanda version > you are using, and which dump program. If your client supports it, > using APPLICATION amgtar (rather than GNUTAR) is definitely a good idea. This client is running 3.3.1. The server is running 3.3.6. Dump program is GNUTAR. I can switch to amgtar. > > But, especially if you are using GNUTAR, an important thing to keep in > mind is that the exclude list is processed by passing the whole list > using an --exclude option to GNU tar, which then processes that list as > it does the dump -- while in contrast the "include" options are > processed ahead of time by Amanda to build a list of directories to pass > on the command line (thus making up tar's list of "what should I be > backing up"?). The tricky thing is that the tar process runs with root > priviledge, so it can see any directory out there... but the "include" > work is done by an unprivileged process and so the directory *above* the > include pattern must be readable by the amanda user... > That explains a lot. > So, what are the permissions on the /netdrives/CAMPUS/ directory itself? root@fileserver:~# stat -c "%a %n" /netdrives 755 /netdrives root@fileserver:~# stat -c "%a %n" /netdrives/CAMPUS 2771 /netdrives/CAMPUS Which explains the problem if I understand correctly. 771 would prohibit the amanda user from reading everything below CAMPUS. Chris
