On Mon, Apr 11, 2005 at 07:00:06PM -0400, Jon LaBadie wrote:
> On Mon, Apr 11, 2005 at 04:18:13PM -0400, Eric Dantan Rzewnicki wrote:
> > I know this is one of the top 10 most frequent FAQs here. I understand
> > the answer conceptually, but I'm having trouble with the syntax, I
> > guess.
> > / is one filesystem. /raidion is an external raid unit. I want to split
> > /raidion into 2 DLEs: /raidion/home/techops and /raidion/home/*
> > (exlcuding /techops).
> > riffraff.rfa.org / comp-high-tar
> > riffraff.rfa.org /raidion/home/techops comp-high-tar
> > riffraff.rfa.org /raidion_HOME_REST /raidion/home/ {
> > comp-high-tar
> > exclude "/raidion/home/techops"
> > }
> > amcheck doesn't like the /raidion_HOME_REST DLE at all.
> An error message would be nice.
I didn't make my exclude relative. That was one problem ...
Sorry for the lack of error message.
See below.
> > What do the fields mean when you add an inline dump-type?
> They don't change because of the inline, the inline just replaces
> a dumptype name. From amanda manpage:
I read the manpage but couldn't figure out which of the optional fields
the /raidion_HOME_REST became. It turns out to not be needed. I was just
trying to follow the example given in the FAQ:
http://www.amanda.org/docs/topten.html#id2520555
which appears to give 4 fields for each DLE. But, with that 2nd field in
there amcheck says:
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): selfcheck does not
support device.
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): sendsize does not
support device.
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): sendbackup does not
support device .
ERROR: riffraff.rfa.org: [BOGUS REQUEST PACKET]
> DISKLIST FILE
> The disklist file determines which disks will be backed up
> by Amanda. The file usually contains one line per disk:
>
> hostname diskname [ diskdevice ] dumptype [spindle [interface]]
>
> All pair [ hostname diskname ] must be unique.
>
> If there are three fields before the dumptype the second is the entry name
> (diskname ?or disklist name?) and the third is the starting directory or
> device name. Thus the diskname need not resemble a pathname if there are
> both a diskname and a starting directory (device name). If there are only
> two fields before the dumptype, the second field is still called a diskname
> but serves as both diskname and device name. Thus it must be a pathname.
My amcheck doesn't seem to like 3 fields before the dumptype. It works
fine if diskname also serves as device name.
> I don't see any error in your sample above, that is why I'd like to see
> the error you get.
> Two additional comments, unless /raidion has only "home" under it, you will
> NOT be backing up the entire /raidion directory tree.
I understand this. I do not want to backup the other directory under
/raidion. Thanks for the scrutiny, though.
> And second, more than one DLE can start from the same directory IF the
> disknames
> differ. For example, the above could have been entered as:
>
> riffraff.rfa.org raidion_TECHOPS /raidion/home/ {
> comp-high-tar
> include file append "./techops"
> }
> riffraff.rfa.org raidion_HOME /raidion/home/ {
> comp-high-tar
> exclude file append "./techops"
> }
I see. thank you.
> And if you have to backup other parts of /raidion, this might work.
>
> riffraff.rfa.org raidion_NOHOME /raidion {
> comp-high-tar
> exclude file append "./home"
> }
Not needed in my case. But, again, thanks for the explanation.
> The "append" is optional. I tend to use it incase I'm nesting dumptypes
> and each might have their own excludes or includes. Or I might want to
> add more exclude directives and don't want to worry about having no more
> than one without an "append".
ah, ok. good to know.
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
network AT rfa DOT org.
|
