On Wednesday 31 July 2002 11:44, support wrote:
>Hi,
>    We've been using Amanda for sometime to handle our tape back
> ups, but have recently encountered an issue. One of our servers
> has a rather large home directory that will not fit onto a
> standard 12gig tape, so for the most part, we have been
> attempting to split the dump into two parts for this drive. The
> format for the two part dumps in the amanda.conf when working
> were slightly different than below, but it was not backing up
> files properly, so have attempted the following. What we are
> trying to do is to back up the first part of the dump excluding
> any file or directory starting with letters a-l, and then on the
> second dump, backing up files excluding m-z.
>
>I believe I must have the exclude format incorrect, I was assuming
> that /home/[a-l]* would do the trick, but is causing Amanda to
> produce errors saying that the dumps failed, and that these two
> disks are "offline".
>
>define dumptype part1dump {
>    comment "Delta part 1"
>    global
>    priority high
>    exclude "/home/[a-l]*"
>}
>define dumptype part2dump {
>    comment "Delta part 2"
>    global
>    priority high
>    exclude "/home/[m-z]*"
>
>I'm trying to find out the proper way of splitting a dump into
> two, and have it work right.
>
>Anyone have any ideas? I was also trying to get amanda.conf to
> write to 10 tapes instead of 8, and that failed miserably as
> well. Changing the tape # from 8 to 10, Amanda would no longer
> recognize any labelled tapes, and would keep asking for a "new
> tape". So I'm back to 8 tapes again.
>
>
>Thanks,
>
>Tim
>[EMAIL PROTECTED]

First, you didn't specify the actual reader/writer program, beit 
dump or tar.  Dump does not support exclusions so I assume you are 
using tar.

The format I use, rather than a whole list of excludes (I do use one 
list, to exclude the holding disks) is to just name everything in 
the disklist, breaking it down to pieces that will fit on a 4gig 
dds2 tape.  I realize this will make for small archives, all 
stacked up on one tape in your case, but its one possibility.

The exclude files contents are a bit fussy, and according to the 
docs, only work in this format:
-------------------
./usr/dumps/*
./var/pacct
-------------------
note the preceeding ./ in each line, which anchors it to the current 
directory.  In my case these happen to be off the root branch, but 
this syntax I'm told is just as effective if I had a 
/home/joetheblowfish/usr/dumps/*
in which case the trailing "usr/dumps/*" portion of that path would 
be excluded.

Now, the tape problem.  One must 'amlabel' the added tapes else they 
probably won't be useable.  This operation can also cause an out of 
order useage by amanda, fixable by hand editing the tapelist after 
the labeling operation to put the newly added tapes into their 
proper place in the list, which, since amanda uses a circular 
buffer, may or may not mean they would be at the top or bottom of 
the list, but may be in some odd order resembling this tapelist:
20020730 DailySet1-15 reuse
20020729 DailySet1-14 reuse
20020728 DailySet1-13 reuse
20020726 DailySet1-12 reuse
20020725 DailySet1-11 reuse
20020724 DailySet1-10 reuse
20020723 DailySet1-09 reuse
20020722 DailySet1-08 reuse
20020720 DailySet1-07 reuse
20020719 DailySet1-06 reuse
20020718 DailySet1-05 reuse
20020717 DailySet1-04 reuse
20020716 DailySet1-03 reuse
20020715 DailySet1-02 reuse
20020713 DailySet1-01 reuse
20020712 DailySet1-19 reuse
20020711 DailySet1-20 reuse
20020710 DailySet1-18 reuse
20020709 DailySet1-17 reuse
20020708 DailySet1-16 reuse

As you can see, I have one tape out of order but its a very minor 
detail.  The last tape used, (or IIRC labeled) is at the top of the 
list, and the next tape amanda wants is at the bottom of the list.

As long as you are aware that adding tapes will insert the new ones, 
IIRC to the top of the list, not in a sorted order.  Amanda doesn't 
care about the order, just that the labels are used in *her* order 
if you do not hand edit the list to restore order.  I've never 
bothered.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.09% setiathome rank, not too shabby for a WV hillbilly

Reply via email to