Skip to main content
Load object
Last update:

Load object

You can load objects into a container in two ways:

  • easy loading is available through the control panel and API. It can be used for files up to 100 MB in size. We do not recommend using Cyrillic characters in object names;
  • segmented loading is only possible via Swift API and S3 API. It is recommended to use it for files larger than 100 MB. We do not recommend using Cyrillic characters in object names.

You can load any number of objects into the container, unless you have set the container limits.

Easy loading⁠

  1. В control panels from the top menu, press Products and select Object Storage.
  2. Go to the section Containers.
  3. Open the container page → tab Objects.
  4. Click Download files
  5. Select the objects to load.

Segmented loading⁠

Segmented download is the downloading of objects in parts (segments), which is recommended for files larger than 100 MB.

Segmented downloading is only possible via Swift API (SLO/DLO technology) and S3 API (Multipart Upload technology). The segmented upload process depends on the API and utility used. Some API utilities (Rclone, Cyberduck) support segmented loading and automatically enable it for objects larger than a certain size. In other cases it must be initialized manually.

With segmented loading, you can:

  • load large objects with smaller segments;
  • increase the speed of object loading with the help of parallel queries;
  • in case of connection failures, do not reload the object, but repeat loading of only the necessary segments.

When segmented loading an object into the main container (<container_name>) creates a service container in which the object segments will be placed:

  • When loading objects via S3 API, the container is created automatically and is called <container_name>_s3multipartuploads;
  • When loading objects via the Swift API, the container is created using the API utility or SDK and is called <container_name>_segments or <container_name>.file-segments.

In the main container (<container_name>) instead of the object, a manifest — a file with a description of segments and paths to them — is downloaded. When the manifest file is downloaded, the segments are automatically substituted into the object.

By default, service containers do not appear in the control panel in the list of object store containers — you can enable the display of service containers in the settings.

When loading objects via API, take into account object storage limitations. Also consider the specifics de-segmentation.

Re-loading an object⁠

If the name of the object to be loaded is the same as the name of the object in the container, the behavior depends on whether the versioning in a container:

  • if versioning is enabled:

    • the new object will become the current version of the object, it will be assigned to the version ID;
    • the previous version of the object will not be overwritten by the new one, but will be transferred to the object version list with the same name;

  • if versioning is paused or disabled, the new object will overwrite the previous one.

Download speed⁠

The speed of loading objects into containers is affected:

  • channel capacity;
  • connection mode;
  • download manager programs used;
  • the distance between the storage servers and you;
  • host load.

Tariffication⁠

With any boot method tariffed storage capacity, number of API requests and outgoing traffic.

  • at easy loading The storage capacity of an entire object is charged;
  • at segmented loading object is stored in segments, so only segments are actually charged. The manifest file takes a minimal amount of space (a few KB), so the cost of storing an object with segments is almost the same as the cost of storing an entire object.