This document is to guide how to set up a mediastore that can send commands to StoreNext API to get the Tape Label and Location of the asset.
Background
To further explain what we are trying to achieve, when archiving an asset on StorNext, it gets stored on one tape or multiple. The location of the asset tells us the status of the asset if it's just on Tape or if it's on Disk & Tape. StorNext is Linux based therefore we use a Linux path along with FsFileInfo Command to get both Tape Label & Location of the asset in StorNext as in the examples shown below:
fsfileinfo /stornext/snarchive/curator_archive/ipvcuratorprod/SourceFiles/Projects/C-LAB/ICD/123456789/20220412160656/TestIPV.mp4
Filename: /stornext/snarchive/curator_archive/ipvcuratorprod/SourceFiles/Projects/C-LAB/ICD/123456789/20220412160656/TestIPV.mp4
Stored Name: /stornext/snarchive/curator_archive/ipvcuratorprod/SourceFiles/Projects/C-LAB/ICD/123456789/20220412160656/TestIPV.mp4
Last Modification: 12-aug-2022 15:07:28
Owner: unknown Location: DISK AND ARCHIVE
Group: unknown Existing Copies: 2
Access: 644 Target Copies: 2
Expired Copies: 0
Target Stub: 16 (KB) Existing Stub: n/a
File size: 160,932,515 Store: MINTIME
Affinity: n/a Reloc: MINTIME
Class: curator_archive Trunc: MINTIME
Alt Store Copy: Disabled Clean DB Info: NO
Media: IM0048(1) IM0047(2)
Checksum: N
Encryption: N
Compression: N
Object Ids: N
FS0000 12 0026257291 fsfileinfo completed: Command Successful.
MediaStore
Here is the Mediastore that we will use to query StorNext to get the Tape Label and Location of the asset in StorNext, you don’t need any DD profile or devices creating for this.
<QUERY-STORNEXT>
<ApprovalRequiredLocations></ApprovalRequiredLocations>
<ArchiveIgnoreField></ArchiveIgnoreField>
<ArchiveIgnoreStates></ArchiveIgnoreStates>
<AvailableMetadataKey>Archived</AvailableMetadataKey>
<FileNamePattern></FileNamePattern>
<FolderPattern></FolderPattern>
<HiResAccessible>False</HiResAccessible>
<Host>https://10.214.161.50</Host>
<MediaStoreDescription>The MediaStores used to archive a source Hi-Res file to and retrieve the file from StorNext. oaky</MediaStoreDescription>
<MediaStoreTemplate>Archive</MediaStoreTemplate>
<NoApprovalRequiredLocation></NoApprovalRequiredLocation>
<ObjectStoreString></ObjectStoreString>
<OutputProfile></OutputProfile>
<Password>qtmimfpw!</Password>
<Path></Path>
<PathMetadataKey>imfSNSMPath</PathMetadataKey>
<PrefixSwap>StoreNextPrefixSwap</PrefixSwap>
<PurgeWorkflow></PurgeWorkflow>
<Source>STORNEXT-ARCHIVE</Source>
<StoreType>Dynamic</StoreType>
<TransferProcess>Spawn - Query StorNext</TransferProcess>
<UnmanagedStorage></UnmanagedStorage>
<UpdateMetadata>True</UpdateMetadata>
<Username>admin</Username>
<Workflow>Spawn - Query StorNext</Workflow>
</QUERY-STORNEXT>
Important Information
Host: Host will be the hostname of IP address of StorNext
Username: Username to access the StorNext
Password: Password to access the Stornext
Source: Assuming you have already configured Archive mediastore
Version: Spawn - Query StorNext 1.2.12
PrefixSwap: You would add a key in Global MediaStore StoreNextPrefixSwap, you would add your Linux to windows swap there like this
In the above example we have L: drive as windows and Linux path /stornext/snarchive
The above configured mediastore can then be called via a plugin, or transfer to.
If using a plugin, using a standard send to destination plugin, along with the send to generic workflow to call this mediastore should work as expected.
When the plugin is actioned against an asset the information will be published against metadata on the asset. Example shown below:
Metadatanames to note:
StorNext1Tapeid
StorNext2Tapeid
StorNextLocation