Object storage
Object storage hardware refresh: Replacing aging nodes
Servers bought five years ago still hold data, still appear in warranty renewals, and are still the nodes most likely to fail next. Replacing them is not ...
Topic
Object storage
Servers bought five years ago still hold data, still appear in warranty renewals, and are still the nodes most likely to fail next. Replacing them is not ...
Object storage
An application fails against object storage and the ticket says the upload did not work. The response that caused it carried an HTTP status, an S3 error code, ...
Object storage
Adding capacity to a running object storage cluster is documented as a short procedure and experienced by operators as a multi-week condition. The nodes join, ...
Object storage
An S3 endpoint is a single hostname standing in front of a set of nodes that fail individually. Most deployments put a load balancer in that position, point a ...
Object storage
A dashboard showing green capacity bars, an average latency figure and an uptime percentage can sit alongside an application team reporting intermittent ...
Object storage
Most on-premises S3 deployments start with one access key per application and a policy granting full access to a bucket, because that is what gets the first ...
Object storage
A migration completes, the copy tool reports no errors, and the source is scheduled for decommissioning. That report describes what the tool attempted and what ...
Object storage
A bucket listing shows completed objects. It does not show the parts of multipart uploads that were started and never finished, and those parts consume ...
Object storage
A lifecycle policy is a small piece of configuration that deletes data continuously, without confirmation, and without any human involvement after the moment ...
Object storage
Versioning is one of the most useful features in object storage and one of the most common causes of capacity that nobody can account for. The mechanism is ...