> On Nov 15, 2018, at 1:22 PM, Chris Miller <[email protected]> wrote:
>
> Hi Brian
> From: "Cuttler, Brian R (HEALTH)" <[email protected]>
> To: "Chris Miller" <[email protected]>, "amanda-users" <[email protected]>
> Sent: Thursday, November 15, 2018 10:54:49 AM
> Subject: RE: Clients that return something else
> Why pipe dd to tar when you can just run tar?
> Good question. tar works at the filesystem level but dd works at the disk
> block level and I'm not aware of any way that tar can create a disk image, so
> I need to read the disk with dd. AMANDA expects a tar saveset, so I need to
> pipe anything I create to tar.
>
>
>
> Er – I think the answer is “yes”, but you may have to roll your own.
> Yeah, so do I. I'm just not exactly sure how I tell the client what to do. It
> appears that the dumptype uses something symbolic, and leaves the client up
> to its own devices to determine what it means. I could also do this, but I'd
> really like to be able to define the script on the server. Also, it's not
> exactly clear to me how the client understands what "GNUTAR" or "DUMP" means
> locally -- something must see "GNUTAR" and conclude, "Oh, he wants to run
> /usr/sbin/tar". For example, if I could put "BASH" in my dumptype definition
> for "program", and include that code somehow, that would be perfect! Ever
> hear of anything like that?
>
> Thanks for the help, Brian.
> --
> Chris.
Well, you do have to point amanda to tar and also to dump, when you compile
amanda.
Just yesterday had to recompile amanda, since dump and restore had been
installed AFTER
the first compilation. And there’s a flag you use to point to tar.
This would be on each client.
Deb Baddorf
