Does tarsnap-keygen force unique machine-name's ?

[Lonnie Abelbeck <lists@lonnie.abelbeck.com>]

HI,

We have just added tarsnap to our OSS project, cross-compiled using Buildroot.

Tarsnap is a gem, works exactly as described, minor learning curve.

Questions ...

1) Does tarsnap-keygen force unique machine-name's ?  In other words if a previously registered tarsnap.key with --machine foo and later another "tarsnap-keygen --machine foo ..." was attempted will that fail with an error ?

I would normally simply test this, but decided to play it safe and ask.


2) Is it best practice to create a single snapshot archive containing all the desired files, or would creating 2 or 3 snapshot archives all at the same time with non-overlaping scopes for organization and restore purposes be useful ?

It would seem 2 or 3 snapshot archives might add some extra metadata overhead and would probably take longer to archive, but for relatively small appliance-like systems would the organization benefit of 2 or 3 snapshot archives ever be useful?

Lonnie