Amazon S3 : clock skew

  • This article is for Amanda Enterprise (AE)
  • Issue Type: Tip

Info Description:

Amanda Enterprise server machine time must be in sync with amanda clients. If the date on Amanda server is different from the Amanda client, then restore may fail due to clock skew between the Amanda server and Amazon. You can get the following errors:

While trying to read tapestart header: The difference between the request time
and the current time is too large. (RequestTimeTooSkewed) (HTTP 403)
DEVICE_ERROR

Solution:

The fix is to keep the date and time of Amanda server in sync with amazon. Amazon’s clocks are within a few milliseconds of the global time standard – they use Xen, not Vmware. Configure Amanda Server and Amanda client as ntp clients.

Powered by BetterDocs

Leave a Reply