> On Nov 16, 2018, at 2:09 PM, Gene Heskett <[email protected]> wrote:
>
> On Friday 16 November 2018 14:38:58 Chris Nighswonger wrote:
>
>> On Fri, Nov 16, 2018 at 2:30 PM Gene Heskett <[email protected]>
> wrote:
>>> from amanda as usr, find /usr/local -name 'planner'
>>> returns that its in /usr/local/libexec/amanda/planner
>>> Now I'll find out (maybe) what it thinks of my changes. Ignore that
>>> faint knocking sound. :) But I assumed you meant backup_job was your
>>> config dir, in my case /usr/local/etc/amanda/Daily so it failed.
>>
>> backup_job is the name of the backup rather than the directory. So in
>> my case it looks like this:
>>
>> /usr/lib/amanda/planner campus
>>
>
> ooohhkkaaay. Can I use wild cards like "Daily PublicA*" ?
>
> No, the logfile error already posted prevents it from running so it
> never gets to PublicA in any form.
>
>> Be sure to run it as your backup user.
>
> amanda in this case.
>
>> Sorry for any confusion there.
>>
>> Kind regards,
>> Chris
>
> Thanks Chris
>
I’m not familiar with the syntax, but I would suspect it wants
planner <configname> node <DLE-Nickname>
which in my case, is the “homeu” word in the following:
node homeu /home {
include “./u*”
}
You have to give it a nickname, because ALL the DLEs for this
disk (“/home”) are based on that same disk location /home
So you nickname the A parts, or the AF (a-f) parts, etc.
If it WASN’T a tar subset (using includes or excludes) then you
would skip the nickname and just put the disk area /home
But for subsets, you need a name for each one.
Deb Baddorf
