Grass Valley K2 System Guide v.7.2 - Manual (Page 62)

62 K2 System Guide 07 April 2010
Chapter 3 System connections and configuration
• Archive — If there are files in the source directory when the Hot Bin service first
starts up, it does not attempt to import those files into the K2 system. Instead, it
moves those files into the Archive directory. This occurs when you first configure
the Hot Bin service, if you manually stop/start the Hot Bin service, and when you
upgrade K2 system software.
Prerequisite for using the HotBin service
• K2 system software must be at version 3.2.56 or higher.
Configuring the HotBin service
When configuring the HotBin service, bear in mind the following considerations:
• You must be logged with administrator privileges on the local K2 system as well
as having the appropriate security permissions to access the source directory.
• If using the HotBin service on a K2 SAN, the K2 Capture Services utility must be
on a K2 server that is also an FTP server. If your K2 SAN has multiple FTP servers,
the utility must be on the primary FTP server.
• The “Cleanup Frequency” (purge) feature deletes files in the Success sub-directory
and in the Fail sub-directory. It does not delete files in the Archive sub-directory.
• Files in the Success, Fail, and Archive sub-directories are “hidden” files in
Windows Explorer. To see these files you must select Show Hidden Files in the
Windows Explorer Folder Options dialog box.
• It is recommended that you keep the source directory and destination bin located
on the local V: drive, which is their default location.
• Do not configure the root of C:\ as the source directory or any other location with
files that must be retained. When the HotBin service first starts up it removes files
in the source directory.
• If you require that the source directory and destination bin be on different systems,
system clocks must be synchronized. The Cleanup Frequency function depends on
accurate system clocks.
• If you specify a destination bin name that does not yet exist, the K2 system creates
it when files are transferred to it.
• HotBin imports are serialized. For example, if fourteen items are already queued
up from ordinary transfers, and you drop a clip into the HotBin, the HotBin clip will
get transferred as the fifteenth clip in the transfer queue. Unlike the normal transfer
process, the HotBin service does not queue the second clip until the first clip is
imported.
Grass Valley recommends that you use the HotBin service as demonstrated in the
following diagram.