Converting an AXR Namespace to an S3 Bucket
With Lattus 3.5.1, you can convert AXR namespaces to S3 buckets and make them accessible through the S3 interface. StorNext provides the capability to convert the media type from AXR to S3.

-
Using the StorNext MDC (CLI only), follow the steps below.
Note: Ensure that no store/retrieve operations are occurring on the same AXR namespace that you plan to convert. If there are any store/retrieve operations occurring on this namespace, wait for the operation to complete.
-
Execute the command
fsobjcfg
and retrieve the media ID of the AXR namespace to be converted. -
Stop TSM.
-
- Refer to the documentation in the "Converting an AXR Namespace to an S3 Bucket" section in the Lattus Service Reference Guide (Part Number 6-67798-xx). Log into the Lattus controller to perform the conversion.
-
After the Lattus conversion is complete, execute the following commands using the StorNext MDC CLI:
-
Add an S3 connection endpoint using the StorNext GUI or the
fsobjcfg
command as shown below. At least one S3 I/O path is needed to access the S3 buckets under the same appliance:#/usr/adic/TSM/exec/fsobjcfg -a -o iopath_alias -i connection_endpoint -e http -t S3 -n controller_node_alias -
Change the AXR namespace name and media type, using the
NameSpace
value from Step 2 and theMedia-ID
value from Step 1a:# fsobjcfg -m -b NameSpace -t S3 -U <S3_bucket_username> -P <S3_bucket_passwpord> -X -f <Media-ID> -
Modify the file /usr/adic/TSM/config/filesize.config and change LATTUS to S3 for the media ID corresponding to the converted namespace. Alternatively, you can achieve the same result using the StorNext GUI by changing the file system policy's steering information from Lattus to S3.
Note: To use the StorNext GUI, TSM should be available.
-
Start TSM.
-
Verify that the store and retrieve operations are working as expected with the converted media type.
-
Use the command
fsfileinfo -u
to verify that the object URL reflects (S3) for every file stored before or after the conversion.
-