I cannot restore objects from Glacier or my lifecycle rules do not work
This page helps you solve issues related to storage classes and lifecycle rules in Scaleway Object Storage. Find the symptom that matches your situation in the following sections.
Before you start
To complete the following actions, you must have:
- Owner status or IAM permissions allowing you to perform actions in the intended Organization
I cannot restore my objects from Glacier
You need to retrieve your data from the Glacier storage class, but the restore operation does not seem to work.
Cause
The time it takes to restore an object depends on the size of the object, and on whether it was uploaded using multipart upload. If your object is larger than 1 MB, the restore can take from a few minutes to 24 hours to start.
Solution
- Run the following command in a terminal to retrieve the metadata of the object you want to restore:
An output similar to the following is displayed:
aws s3api head-object --bucket <BUCKET_NAME> --key <OBJECT_NAME>{ "AcceptRanges": "bytes", "Restore": "ongoing-request=\"true\"", "LastModified": "2024-03-13T16:30:44+00:00", "ContentLength": 5, "ETag": "\"sd11r084349bc25d97e29393ced1d\"", "ContentType": "application/octet-stream", "Metadata": {}, "StorageClass": "GLACIER" } - Check the
Restoreline."Restore": "ongoing-request=\"true\""indicates that the restore operation has already started. Wait for it to complete.
My lifecycle rules do not work as expected
Your lifecycle rules do not transition or expire objects as expected.
Cause
- The lifecycle rules are not properly set.
- The prefixes or tags of your objects contain spaces.
- You reached the limit of 500,000 lifecycle jobs per day.
Solution
- Make sure that your lifecycle rules are properly set in the Scaleway console.
- Make sure that the prefixes and tags of your objects do not contain any spaces.
- If you reached the limit of 500,000 jobs per day, transition or delete objects manually.
- For expiration rules, use the HeadObject command to check which rule applies to a specific object. The
x-amz-expirationheader returns the expiration date and rule ID.
Going further
- See the lifecycle rules API documentation for more information on lifecycle configuration elements.
- When you contact the Support team about Object Storage, include the endpoint (e.g.,
s3.fr-par.scw.cloud), the bucket name, and the object name if the request concerns an object.
If you still cannot solve your problem, open a support ticket, providing as many details as possible including the information below:
- Resource ID
- Resource name
- Date and time (timestamp)
- User-agent (SDK, client, console, etc.)
- Transaction ID (if possible)
- Log / trace of the error (if possible)
- Screenshots (using our secure pastebin tool (External link))
- HTTP status code (if applicable)
- Request type (PUT, GET, etc., if applicable)