Page History

...

When completed is non-0, the message indicates that message referenced by ID has completed. If error is non-zero, then the action has failed with given error code. If error is 0, then the action has succeed, and the offset and length range of data has been copied by the mover. If file_id is included, then the agent will store this and include this with future actions referring to this file. 

POSIX Mover

The POSIX mover allows another filesystem to be used a second storage tier for Lustre. The mover copies data between Lustre and another local filesystem. The POSIX mover configuration includes the archive ID and path for each archive backend managed by the mover.

Each time a file is submitted to the mover for archiving, the mover generates a new UUID which is used to identify the data object in the archive directory. The path to the object is <archiveDir>/objects/xx/yy/UUID, where:

xx = UUID[0:2] 
yy = UUID [2:4]

Once the archive is complete, the mover returns the UUID to the agent. The UUID is used during restore operation to locate the data object in the archive directory.

S3 Mover

The S3 mover allows an S3-style object storage system to be used a second tier for Lustre. The mover copies data between Lustre and an S3 bucket. The configuration includes the archive ID and bucket to be used to store data. 
A UUID is generated for each file, and the object is stored in the bucket with similar path as the POSIX mover. Once the archive is complete, however, a URL for the object is returned to the Agent:

s3//<bucketName>/<prefix>/objects/xx/yy/UUID

The S3 mover can also be used to import existing data set from S3 into Lustre. To do this, the “lhsm import” command is used to replicate the path names from S3 into the Lustre filesystem, and the import also adds the s3 URL to each file so the mover can retrieve the data.