Re: why is the remote backup still writing it's indexes locally?

[On 11 Feb, @23:27, Thomas wrote in "[hdup-user] why is the remote  ..."]
> Mr. Gieben, 
>    First of all, this program rocks - thanks for
> writing it. It's really ideal for my needs - not too
> complex, and still flexible. I was starting to read
> about Amanda and it was overkill for what I needed.

Thanks! :-) Before making hdup I also looked at Amanda, actually
even installed it, but I really could not bring myself to actually
_use_ it :-)

>    I'm wondering about one thing, though. I'm doing
> remote backups from a couple of servers to a central
> one with cron jobs  - "monthly @[email protected]", etc.. 
>    I noticed, though, that the file indexes
> (inclist.monthly), etc., are being written locally to
> the machine though, and not to to the remote host
> along with the data.  To get around that, I made a
> little script to scp them over after the backup with
> the "postrun" directive.  Is there something I'm doing
> wrong here?

no, I'm still wondering if the remote backup stuff is only
"inverted" from what people expect or just plain inconsistent :-)

Let me explain:
We have 2 machines: A and B. 
B is used as a remote backup host, ie. there live the tar files.


backup:

hdup monthly a @b (executed on A)

                 tar file(s) 
A       --------------------------> B
incfiles                          no incfiles

When restoring no incfiles are consulted, the are only used for
backing up. So:

restore:

                              hdup restore a @a (executed on B!)
       
                 tar files(s)         B
A       <---------------------------
incfiles

and the tar get's unpacked (and maybe unencrypted) on A.

regards,
Miek