Re: limited keys (-r, -w), remote pruning

[Mathew Davies <mathew@nolimits-exchange.com>]

Mads Sülau Jørgensen <mads@...> writes:

> 
> On Mon, Dec 14, 2009 at 12:44 PM, Colin Percival <cperciva@...> wrote:
> > ... you really shouldn't be doing this.  Reconstructing the Tarsnap cache
> > directory can take a non-trivial amount of bandwidth if you have lots of
> > archives stored, so you'll generally be much better off with each system
> > storing data independently.
> 
> I'm fairly sure that everyone agrees, that the current "solution" to
> delete archives from a different machine than the one that normally
> runs the backups is bad for business.
> 
> I think a solution to prune/purge archives from a different machine is
> needed, which iirc would need to be able to fetch a list of archive
> names, and delete an archive. Is there anyway this could be done with
> the current architecture (e.g. a read only fsck)?
> 

I'm looking for this feature too. My server has a read/write only key, so it's impossible to remove old entries remotely without causing the --fsck message.

+1