Hello

I'm installing amanda-backup_server-3.3.2-1.rhel6.i686.rpm with Amazon S3 as 
storage.

In this server (Centos 6.3 x86) I had amanda client, I've desinstalled it and 
installed amanda-backup_server-3.3.2-1.rhel6.i686.rpm 

When I run amlabel I have a "Segmentation fault" message.



 for i in 1 2 3 4 5 6 7 8 ; do amlabel DailySet1 DailySet1-$i slot $i; done;
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault



My amanda.conf


org "SERVER4 backup"    # your organization name for reports
mailto "[email protected]"       # space separated list of operators at 
your site
dumpcycle 1 week        # the number of days in the normal dump cycle
runspercycle 7          # the number of amdump runs in dumpcycle days
                        # (1 week * 5 amdump runs per week -- just weekdays)
tapecycle 8 tapes       # the number of tapes in rotation
                        # 1 week (dumpcycle) times 5 tapes per week (just
                        # the weekdays) plus a few to handle errors that
                        # need amflush and so we do not overwrite the full
                        # backups performed at the beginning of the previous
                        # cycle
runtapes 1              # number of tapes to be used in a single run of amdump

device_property "S3_ACCESS_KEY" "XXXXXXXXXXXXXXXXXXXXXXXXXXX"                # 
Your S3 Access Key
device_property "S3_SECRET_KEY" "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX  # Your S3 
Secret Key
device_property "S3_SSL" "YES"                                        # Curl 
needs to have S3 Certification Authority (Verisign today)
device_property "S3_STORAGE_CLASS" "REDUCED_REDUNDANCY"
#device_property "S3_BUCKET_LOCATION" "EU"
                                                                      # in its 
CA list. If connection fails, try setting this no NO
tpchanger 
"chg-multi:s3:server4-amanda-backup/DailySet1/slot-{01,02,03,04,05,06,07,08}" # 
Number of tapes in your "tapecycle"

tapetype S3     # what kind of tape it is (see tapetypes below)

#holdingdisk hd2 {
#    directory "/var/lib/amanda/holdings/DailySet1"
#    use 1000 Mb
#    }

autolabel "DailySet1-%%%%" empty
labelstr "^DailySet1-[0-9][0-9]*$"      # label constraint regex: all tapes 
must match

dtimeout 1800           # number of idle seconds before a dump is aborted.
ctimeout 30             # maximum number of seconds that amcheck waits
                        # for each client host
etimeout 300            # number of seconds per filesystem for estimates.

define dumptype global {
        comment "Global definitions"
        auth "bsdtcp"
}

#define application-tool and dumptype for the amgtar application
define application-tool app_amgtar {
    comment "amgtar"
    plugin  "amgtar"
    property "GNUTAR-PATH" "/sbin/gtar"
    property "GNUTAR-LISTDIR" "/usr/lib/amanda/gnutar-lists"
}

define dumptype server-encrypt-best {
        global
        program "GNUTAR"
        comment "dump with best client compression and server symmetric 
encryption"
        compress server best
        encrypt  server
        server_encrypt "/usr/sbin/amcrypt-ossl"
        server_decrypt_option "-d"
        index yes
        exclude list "/etc/amanda/DailySet1/exclude-filename"
}

define tapetype S3 {
    comment "S3 pseudo-tape"
    length 10240 gigabytes
    part_size 100G
    part_cache_type none
}

includefile "./advanced.conf"
#includefile "/etc/amanda/template.d/dumptypes"
#includefile "/etc/amanda/template.d/tapetypes"



I've just  configured another Centos 6.3 x64 server with S3 storage and all 
works well.

Any help ? maybe a x386 amanda bug ?

Thanks in advance and excuse my english.


roberto


Reply via email to