Error messages when using Amazon S3

This article is for Amanda Enterprise (AE)

  1. ZMC Verify Server on a backup set that backs up data to Amazon S3 can fail with “slot is empty” message. For example:
     changer error: slot 6: chg-multi: slot is empty
    This implies that the Amazon S3 name (combination of bucket name and backup set name) is not globally unique. Please choose another bucket name.
  2. Amanda backups to Amazon S3 fail if Amazon S3 subscription has been cancelled or has expired. Example messages that will be seen:
     While creating new S3 bucket: Your account is not signed up for the S3 service. You must sign up before you can use S3. (NotSignedUp) (HTTP 403)
    You have to buy Amazon S3 subscription from Zmanda Network and upload the new AWS certificate file in ZMC Backup Where page.
  3. Amanda backups to Amazon S3 fail if the time skew on the Amanda server is large. The taper debug log files have the error message:
     While trying to read tapestart header: The difference between the request time and the current time is too large. (RequestTimeTooSkewed) (HTTP 403)
    Set the time on the Amanda server correctly. Synchronize the time on the Amanda server using ntp server.
  4. Amanda backups to Amazon S3 fail if the Objects have been removed, moved to glacier, or purged outside of Amanda’s control:
     amcheck-device: GET https://zmc-aws-linux.s3.amazonaws.com/BackupSet%2Dtapespecial%2Dtapestart failed with 404/NoSuchKey (NoSuchKey) (HTTP 404)
    Amanda uses special Objects to mark where data files begin and end. To identify the start point, Amanda searches for the tapestart which is a 32 kilobyte header. The header must be copied back into the zmc S3 bucket or recreated by using the amlabel command.

Powered by BetterDocs

Leave a Reply