Should I use skip-incr?

[Ulrik Sandberg]

I'm using a daily config named DailySet1 on a HP DDS3. Six days a
week. Works nicely.

DailySet1:

dumpcycle 2 weeks
runspercycle 12
tapecycle 16 tapes
...
define dumptype global {
    index yes
    maxdumps 2
}

I'm also experimenting with a weekly archive config named Archive. It uses
the same disklist as DailySet1 (symbolic link). It has been running for
six weeks now, but I'm suspecting a misconfig. I'm not using 'skip-incr yes'.

Archive:

dumpcycle 9 days
runspercycle 9
tapecycle 9 tapes
...
define dumptype global {
    index yes
    maxdumps 2
    record no     # no recording necessary, because...
    dumpcycle 0   # ... full dumps are always done

    # Not using the skip-incr yet, since Amanda seems to be keeping
    # correct incremental information.
    #skip-incr yes # skip incrementals in between; no use since no record
}

The tape doesn't fit all file systems as full dumps. That's OK. The ones
that don't fit will be dumped the next week, or the week after. I figured
it would be nice to have incrementals of the ones that didn't fit, so
I didn't enable 'skip-incr'. A quick check with amrecover and it looks
like the incrementals work.

Question 1: Should I use 'skip-incr yes' for the weekly Archive config?

Question 2: I'm assuming 'record no' means don't clear "archive bit" on
PCs. Is that correct?

Question 3: If the Archive dump doesn't clear the "archive bit", wouldn't
the following incremental using Archive be totally pointless? Especially
since DailySet1 does clear the bit once in a while...

--
Ulrik Sandberg