Great examples here for you.  I'll make some comments about the parts we DON'T 
use,  in case you don't need them either.

On Aug 1, 2013, at 9:03 AM, Markus Iturriaga Woelfel <[email protected]>
 wrote:

> Alexander - You need to define your "dumptypes" in your amanda.conf file (or 
> another file included in that). You can then refer to them in your 
> "disklist". Your best source for information should be the amanda.conf manual 
> page. This is also where you can learn about the other features of the 
> amanda.conf file such as inheritance. 
> 
> You may only need one dump type for a very basic setup or you may want to set 
> up something more complex. You may also want to look at the manual page for 
> amgtar, amanda's interface with tar. Here is an example from our amanda 
> configuration:
> 
> First I set up the options for amgtar:
> 
> define application-tool app_amgtar {
>    plugin "amgtar"
>    property "ATIME-PRESERVE" "NO"
>    property "ONE-FILE-SYSTEM" "NO"
>    property "SPARSE" "YES"
>    property "ACLS" "YES"
>    property "SELINUX" "NO"
>    property "XATTRS" "YES"
>    property "CHECK-DEVICE" "NO"
>    property append "IGNORE" ": value .* out of time_t range"
>    property append "NORMAL" ": file changed as we read it"
>    property append "NORMAL" ": Exiting with failure status due to previous 
> errors"
> }
> 

You may not need amgtar at all,  if regular tar is sufficient for you.
I use amgtar only in SOME cases,  and I only bother with the last three lines, 
so that
I get less printed in my "error" outputs.



> This tells amgtar what flags to use for tar and what kind of messages to 
> ignore or consider normal. I have a few other "application-tool" definitions 
> as well.
> 
> Next, I have a global dump type template that sets options I want to include 
> in all my other dump types:
> 
> define dumptype global {
>    index yes
>    strategy standard
>    ssh_keys "/etc/amanda/eecs/ssh-key"
> }
> 
> Since I use SSH as the transport mechanism for Amanda, I want to define the 
> key to use in all dumptypes.
> 
> I can then inherit this in a specific dump type:
> 
> define dumptype amgtar-nolvm {
>    global
>    auth "ssh"
>    comment "Backup using amgtar with best server-side compression"
>    compress server custom
>    server_custom_compress "/usr/bin/pigz"
>    program "APPLICATION"
>    application "app_amgtar"
> }

You might be able to drop the last two lines and just use
  program "GNUTAR"
if gnu tar works for you.   It's easier to start with just plain tar, perhaps.
I personally change "global" into something that tells me it isn't a keyword:
I use   MYglobal    or something like that,  to indicate that it's a name.


> 
> As you can see, I include the "global" definition, tell it to use a custom 
> compress program (pigz, a multi-threaded version of gzip which gives me a 
> nice speed boost on this 8-core server). I then tell it that I want to use 
> the application tool app_amgtar (which I defined earlier) as the backup 
> program. 
> 
> I now have a dumptype I can use in my disk list, for example:
> 
> #Host                     Disk                            Dumptype            
>         Spindle Network
> abzu.eecs.utk.edu         /etc                            amgtar-nolvm        
>         2       main


The last two bits might not be necessary either -- I don't use them.   Just
hostname                      disk    dumptype
myhost.where.ok      /etc         MYtar

for example.

Deb Baddorf



> 
> My example may be more or less complex than what you need in your setup. I 
> hope that gets you started.
> 
> Grüße nach Deutschland,
> 
> Markus
> On Aug 1, 2013, at 6:38 AM, Alexander Geronymakis 
> <[email protected]> wrote:
> 
>> 
>> 
>> 
>> -------- Original-Nachricht --------
>> Betreff:     I need help!
>> Datum:       Wed, 31 Jul 2013 18:39:46 +0200
>> Von: Alexander Geronymakis <[email protected]>
>> An:  [email protected]
>> 
>> Hi,
>> I'm new to IT , I' m currently doing my internship in a firm in 
>> germany.I was recently asked to make a research on backup software and 
>> we all agreed on trying amanda community version as a best solution.So 
>> after I had succesfully  installed and tested the server, I'm currently 
>> having troubles setting up the clients.More specific ,I have 4 virtual 
>> machines running debian6-64bit  under a centOS host, 3 as clients and 
>> one as server.My question is how to setup exactly the dumptype  in the 
>> disklist configuration file.I mean what are the options/choices/format? 
>> amcheck is giving me errors for it and I could't find any helpful infos 
>> on the internet.Moreover, is amcheck supposed only to run on the 
>> server?because ,no matter how I tried on the clients I always get the 
>> same error: amcheck: command not found . I have double-checked 
>> dependencies,various procedures etc. and everything seems to be in 
>> order.The version I installed is the latest stable release 3.3.4. I know 
>> my questions might sound very noob to you,but hey, I'm new to this.I 
>> would be sooo happy if somenone could help me figure that out.
>> 
>> 
>> 
> 
> ---
> Markus A. Iturriaga Woelfel, IT Administrator
> Department of Electrical Engineering and Computer Science
> University of Tennessee
> Min H. Kao Building, Suite 424 / 1520 Middle Drive
> Knoxville, TN 37996-2250
> [email protected] / (865) 974-3837
> http://twitter.com/UTKEECSIT
> 
> 
> 
> 
> 
> 
> 
> 


Reply via email to