Re: dar_manager: dar process fails

Am Samstag, den 18.07.2020, 21:59 +0200 schrieb Denis Corbin:
> 
> On 18/07/2020 19:23, Volker Wysk wrote:
> > Am Samstag, den 18.07.2020, 15:21 +0200 schrieb Denis Corbin:
> > > On 18/07/2020 07:57, Volker Wysk wrote:
> > > then you should rather use -e option than -o option. See
> > > dar_manager man page for details :)
> > 
> > The documentation of -o doesn't mention that the arguments will be
> > stored in the database. I also couldn't find it mentioned
> > somewhere else in the dar_manager man page. I also don't know for
> > sure what those stored arguments will do, and what they are for.
> 
> in a way you are right, this is not explicitly said for -o option.
> Though you have a list of available *actions* on a database as showed
> at the top of the man page (-A, -l, -D, -b, -o, ...) what would -o do
> el
> se
> than modifying a database as dar_manager reason of existence is to
> build, use and manages databases... ;)
> 
> You have also the -r option to restore files, having dar_manager
> invoking dar with the correct archive name and path and filters for
> the specified requested files. This is a short cut to easy the work.
> 
> If you look carefully the -r description you will see that it has -e
> as sub-option which description explains the difference with -o
> option:
> 
> "-e: pass some more options to dar. While the -o options takes all
> that follows on the command line as argument to pass to dar and
>                    *write these in the database*, the -e option does
> not alter the database and has only one argument. In other words, if
> you need to pass several options to dar through the use of the -e
> option, you need to use quotes (simple quotes ' or double quotes ")
> to
> enclose these options"

Oh, you're right. I missed this. Sorry.

> > > From the documentation of -e, I should have looked more closely,
> > > but I
> > thought that the (only) difference was that -e takes one argument
> > (containing several arguments for dar), whereas -o takes a list of
> > arguments.
> > 
> > Could you please add information, what those stored dar options
> > are about?
> 
> sure, I will enhance the man page. For your information, options for
> dar stored in the database are passed systematically to dar when it
> is
> run from dar_manager by mean of -r option.
> 
> I my own databases, I usually set '-R /' using -o option. This way
> when I want to restore a particular file in a particular version it
> goes directly to the correct place without having to specify anything
> else.
>
> But sometimes I want to restore a file in the current directory to
> see
> its content not touching the running system, so when invoking -r
> option with dar_manager I also add -N option for the option to dar
> stored in the database be ignored. Usually I also add -e "--flat"
> with
> -r option of dar_manager, for dar does not restore directory tree and
> I get just the files I asked for restoration from a particular
> version/date in the current directory.

Sounds sophisticated.  :-)

> I hope this use case will help you see which way to have these
> options
> useful for you too.

I use dar only (but regularly) for my whole system backups. It's all in
some shell scripts, and a program which I've written for this purpose.
So I want to "keep it simple, stupid" (KISS). It's more important to
me, that it's easy to see what's going on, than a comfortable command
line interface. Therefore, I'm not using those this stored dar options
feature (yet).

Regards,
Volker