Document Title, 6-66957-02 Rev A, January 2011, Product of USA.
Quantum Corporation provides this publication “as is” without warranty of any kind, either express or
implied, including but not limited to the implied warranties of merchantability or fitness for a particular
purpose. Quantum Corporation may revise this publication from time to time without notice.
Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior
written authorization of Quantum Corporation is prohibited by law and constitutes a punishable
violation of the law.
TRADEMARK STATEMENT
Quantum, the Quantum logo, DLT, DLTtape, the DLTtape logo, Scalar, and StorNext are registered
trademarks of Quantum Corporation, registered in the U.S. and other countries.
Backup. Recovery. Archive. It’s What We Do., the DLT logo, DLTSage, DXi, DXi-Series, Dynamic
Powerdown, FastSense, FlexLink, GoVault, MediaShield, Optyon, Pocket-sized. Well-armored, SDLT,
SiteCare, SmartVerify, StorageCare, Super DLTtape, SuperLoader, and Vision are trademarks of Quantum.
LTO and Ultrium are trademarks of HP, IBM, and Quantum in the U.S. and other countries. All other
trademarks are the property of their respective companies.
Specifications are subject to change without notice.
Quantum Timecode-Based Partial File Retrieval (PFR) allows you to
quickly retrieve and utilize segments of large media files—rather than
the entire file— based on timecode parameters.
Segments of large media files that have been archived to tape using
Quantum StorNext Storage Manager can be requested using a simple
XML request file. Quantum Partial File Retrieval instructs StorNext to
retrieve only the necessary portion from tape, and then presents that
segment as a complete MXF or QuickTime file.
If the file has not yet been truncated by StorNext Storage Manager, the
result will still be the same. However, in this case the Partial File will be
generated directly from the complete media file on disk.
The Quantum Partial File Retrieval feature requires a dedicated
Windows-based server on which to run. For larger scale installations, the
Quantum Partial File Retrieval functionality can be distributed across
multiple Windows server machines.
Chapter 1: Introduction to Timecode-Based Partial File Retrieval
Note: Partial File Retrieval is designed to work exclusively with
QuickTime and MXF video files, which makes PFR suitable for
applications which reference video by timecode.
The QuickTime or MXF wrapper for a retrieved file will be reconstructed during the Partial File Retrieval process, and as
such retrieved files will not be byte-for-byte replicas of the
original. However, the video frames and audio samples in the
retrieved files are not transcoded and therefore there is no
generation loss from the retrieval process. The only exception
to this is for retrieving MPEG Long GOP video (for example
Sony XDCAM HD 50), where a small number of frames are
transcoded at the start and end of the retrieval in order to
reconstruct a coherent GOP structure.
Quantum Timecode-Based Partial File Retrieval consists of two primary
components: an indexer which indexes media files before they are
archived to tape and truncated, and a Partial File Retrieval service that
performs the requested retrievals.
Partial File Retrieval Indexer
Chapter 2
File Retrieval Works
The Partial File Retrieval Indexer looks for new media to appear in
StorNext Storage Manager. When it finds a new media file it generates
an index for it, in effect mapping timecode values in the original media
file to byte offsets. This allows subsequent timecode- based requests to
retrieve only the necessary portions of a large media file from tape.
The index files, which are written as QuickTime reference files, are
generated in a parallel folder structure on the managed storage. The
two file locations below represent a MXF based media file and its
associated index file.
Chapter 2: How Timecode-Based Partial File Retrieval Works
Partial File Retrieval Service
Note: The index files do not contain any content themselves, and are
therefore very small in comparison with the files they index.
It is important that the indexed files themselves are never
truncated.
The Indexer does not attempt to index files that it thinks might
be currently in-record. Therefore, the first time the indexer
encounters the file, there may be some delay before a
particular file is indexed while the indexer is trying to establish
if the file is currently being written to.
Partial File Retrieval Service
Folder StructureWithin the Quantum Partial File Retrieval Configuration Tool, it is
possible to set up multiple sets of folders for different request types. For
example, a set of folders for news requests might look like this:
//StorNext/snfs1/Requests/News
//StorNext/snfs1/Requests/News/PFR‐REQUEST
//StorNext/snfs1/Requests/News/success
//StorNext/snfs1/Requests/News/fail
The configuration tool creates these folders for you and allows you to
set an output format: QuickTime Movie or MXF.
The four folders shown in the example are used in the following
manner:
1 The parent folder (in this case
extract will be placed once retrieved and created;
2 The
3 Once the request has been completed, the XML request file will be
Chapter 2: How Timecode-Based Partial File Retrieval Works
Partial File Retrieval Service
4 If an error occurred in retrieving the partial file, the XML request file
will be moved to the
fail
folder.
Issuing a RequestA Partial File Retrieval request is issued in the form of a small XML file,
the format of which can be seen in the example later in this User Guide.
The XML file simply describes a movie (via a full UNC path) with an in
and out timecode value.
Quantum PFR will handle a number of the requests simultaneously with
the overall retrieval performance dependant upon the quantity of tape
drives available.
The number of tape drives limits how many requests can be processed
simultaneously. Once all tape drives are busy, additional requests will be
queued until a tape drive becomes available.
Monitoring RequestsRequests will be processed automatically once the request file is
detected. The Partial File Retrieval service automatically detects the XML
request file, appends the processed request to the queue of pending
requests, and processes them in the order received. XML request files
are moved to the
status of the request.
success
or
fail
folder as appropriate based on the
Use the PFR status GUI to monitor requests, cancel pending or active
requests or change the priority of the pending requests.
Step 1: An MXF (or QuickTime) file is written into the managed file
system.
Step 2: Frames are read from this new file and converted into a
QuickTime reference index file.
Figure 2 PFR Steps 3 - 5
Index
XX
PFR-Request
3
4
5
<xml><xml><xml>
<xml><xml><xml>
Chapter 2: How Timecode-Based Partial File Retrieval Works
PFR Workflow
Step 3: Some time later, according to the policies that have been
configured, the Storage Manager copies the file to the tape archive and
truncates the file on disk.
Step 4: A third-party media asset management (MAM) system
generates an XML request for a partial file and writes it into the request
folder.
Step 5: PFR picks up the request XML and starts to parse it.
Quantum Partial File Retrieval consists of the following software
components:
• PFR Control Server and Configuration GUI: This is the core of the
system and the tool that configures it
• PFR Transfer Engine: This is the engine that retrieves and creates
the partial file
• PFR Status GUI: This is the user application which allows
monitoring and modifying the queue of pending and in-progress
retrievals
Chapter 3
• Index Engine and Configuration / Status GUI: This is the service
that indexes media files before they are truncated
• Virtual Machine (VM) with SNAPI and PFR Linux Component:
This is the interface to the StorNext API (SNAPI)
A typical installation of Quantum Partial File Retrieval installs all of the
above components on a single Windows-based server machine. This is
fine for most installations, but for larger installations the components
can be distributed as follows:
• PFR Server: Includes "PFR Control Server and Configuration GUI" and