Downloading objects
Download of an object is important when the AFM to cloud object storage relation is created in the
ObjectOnly
mode. With the ObjectOnly
mode, the
fileset does not automatically synchronize with a cloud object
storage. This behavior is the default behavior of operation.
You need to manually download data or metadata from the object storage server into the AFM to cloud object storage filesets by using the mmafmcosctl command. The data transfer from a fileset to an object storage server does not need any manual intervention (single-writer (SW), independent-writer (IW) mode).
When selected objects are needed for an application to run on an AFM to cloud object storage fileset, they can be downloaded by using the --object-list option. All objects can be download by using the --all option. These objects are prefetched or downloaded from a cloud object storage.
You can specify individual objects and also directories containing objects in the same
list-file and use this list-file for downloading them from the bucket. This list-file is a line
separated file, where each entry is specified in a line. This list-file must not have any space in
between two lines.
The modifications to objects on a cloud object storage are not synchronized to the cache. Therefore, you need to download the objects. The modification to objects in IW and SW-modes is pushed to the cloud object storage.
When you download an object from AFM to cloud object storage or list objects, many objects or nested directories on a cloud object storage have extended attributes. The read directory operation takes time to populate metadata because the extended attributes need to be fetched.
In many AFM to cloud object storage use cases such as running analytics, when extended attributes (xattrs) synchronization is not required at the fileset level, set the afmObjectFastReaddir parameter value to yes for the improved read directory performance. To set this parameter, you must stop a fileset and start the fileset by using mmafmctl and mmchfileset commands.
When the afmObjectFastReaddir parameter value is set to yes, the AFM to cloud object storage read directory operation ingests metadata faster. Therefore, the metadata and later data read performance is improved. Extended attributes are not fetched from a cloud object storage. Also, objects that are deleted on a cloud object storage are not reflected in an AFM cache.
- Failed Object list
-
While downloading objects, because of network errors some objects can fail to download. To resolve this problem, system administrators can use --enable-failed-file-list option from mmafmcosctl download command.
Enabling --enable-failed-file-list option creates a list of failed objects on the gateway node or node specified in the command. System administrators can run the download command again by using --object-list parameter and the failed file list is generated to download the objects again.