At Mon, 22 Jul 2024 18:00:16 +0200 Exuvo <[email protected]> wrote:
>
> According to man amanda-changers the device properties can be specified in
> multiple places so where you have them should also work.
I don't think that is the problem. According to this:
https://stackoverflow.com/questions/30518899/amazon-s3-how-to-fix-the-request-signature-we-calculated-does-not-match-the-s
The problem might be the pathname going to Amazon is bad (leading . or leading
/), but *I* am not using either, so I guess Amanda is messing up the
"signature" somehow. So this might be a bug? This used to work with Amanda
3.3, so it might be something broke in 3.4 or 3.5.
(I've also opened an issue on github.)
And I think the "tapedev" is indicated by the
tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
line: it is a changer on an Amazon s3 device with with a Bucket of
sharky5-backups, with slots slot-00 through slot-40.
>
> Anton "exuvo" Olsson
> [email protected]
>
> On 2024-07-22 17:19, Robert Heller wrote:
> >
> > At Mon, 22 Jul 2024 17:10:23 +0200 Exuvo <[email protected]> wrote:
> >
> >> Never used S3 but dont you need to use a "tapdev" line and device
> >> properties on that instead of on the changer?
> >> See man amanda-devices S3 Device
> > No, that does not work. Get a config file syntax error... The docs are
> > somewhat wrong.
> >
> >> Anton "exuvo" Olsson
> >> [email protected]
> >>
> >> On 2024-07-22 14:24, Robert Heller wrote:
> >>> backup@sharky5:~$ amcheck sharky5
> >>> Amanda Tape Server Host Check
> >>> -----------------------------
> >>> NOTE: tapelist file does not exists
> >>> it will be created on the next run
> >>> NOTE: Holding disk '/var/lib/amanda/holdings/sharky5': 38816 MB disk
> >>> space available, using 12000 MB as requested
> >>> slot 1: While creating new S3 bucket: The request signature we calculated
> >>> does not match the signature you provided. Check your key and signing
> >>> method. (SignatureDoesNotMatch) (HTTP 403)
> >>> slot 2: While creating new S3 bucket: The request signature we calculated
> >>> does not match the signature you provided. Check your key and signing
> >>> method. (SignatureDoesNotMatch) (HTTP 403)
> >>>
> >>> backup@sharky5:~$ cat /etc/amanda/sharky5/amanda.conf
> >>> org "Deepwoods Software Sharky5" # your organization name for
> >>> reports
> >>> mailto "[email protected]" # space separated list of operators at
> >>> your site
> >>> dumpcycle 28 days # the number of days in the normal dump cycle
> >>> runspercycle 28 # the number of amdump runs in dumpcycle days
> >>> # (1 week * 5 amdump runs per week -- just
> >>> weekdays)
> >>> tapecycle 40 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 3 # number of tapes to be used in a single run of
> >>> amdump
> >>>
> >>> define changer my_s3 {
> >>> tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
> >>> device-property "S3_ACCESS_KEY" "XXXXXXXXXXXXXXXXXXXXXX"
> >>> device-property "S3_SECRET_KEY" 'xxxxxxxxxxxxxxxxxxxxxxxxxx"
> >>> device-property "NB_THREADS_BACKUP" "3"
> >>> # changerfile "/etc/amanda/sharky5/changer.conf"
> >>> }
> >>> tpchanger "my_s3"
> >>> tapetype S3 # what kind of tape it is (see tapetypes below)
> >>>
> >>>
> >>> I am sure the S3_ACCESS_KEY and S3_SECRET_KEY are correct.
> >>>
> >>
> >>
> >>
>
>
>
>
--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
[email protected] -- Webhosting Services
