Other Topic Library Versions

About the K2 FTP interface

The K2 FTP interface has the following modes:
  • Movie mode — FTP operations are performed on assets in the K2 media database. This is the mode on a K2 systems with a media database, such as online/production K2 SANs and stand-alone K2 Summit systems.
  • File mode — FTP operations are performed on files. This is the mode on systems without a media database, such as Nearline K2 SANs.
The K2 FTP interface can run in the movie mode and the file mode simultaneously.

On online/production K2 SANs and stand-alone K2 Summit systems, FTP clients can log into the K2 FTP server using credentials for Windows user accounts that are registered on the K2 system. When such accounts are used, the K2 FTP server exposes “virtual” folders at the FTP root. A virtual folder exists for each video file format that is supported by the FTP server. Navigation to one of these virtual folders allows an FTP client to get or put clips in that file format.

In addition, the K2 FTP server supports reserved user login names that directly places the FTP client in a particular mode of operation. The FTP login names and their modes are as follows:
movie
FTP gets/puts supported for K2 clips in the GXF file format; the clip's root becomes the FTP root.
mxfmovie
FTP gets/puts supported for K2 clips in the MXF file format; the clip's root becomes the FTP root
mpgmovie
FTP puts supported for MPEG program and transport streams; the clip's root becomes the FTP root
qtmovie
FTP gets/puts supported for K2 clips in the QuickTime file format; the clip's root becomes the FTP root
video_fs
Pinnacle FTP emulation mode
k2vfs
All FTP operations supported on generic files on the K2 system's media file system; media file system root becomes the FTP root.

You can use Internet Explorer to access the FTP interface to see an example.

The K2 FTP server runs on K2 Media Server that has the role of FTP server. While it also runs on the K2 Solo Media Server, stand-alone storage K2 Summit Production Clients and K2 Media Clients, it is important to understand that it does not run on shared storage K2 clients. When you FTP files to/from a K2 SAN, you use the FTP server on the K2 Media Server, not on the K2 client that accesses the shared storage on the K2 SAN.

If clips are created by record or streaming on a K2 file system such that media files have holes/gaps, i.e. unallocated disk blocks, in them, then that clip represents a corrupt movie that needs to be re-acquired. The K2 system handles corrupt movies of this type on a best-effort basis. There is no guarantee that all available media, especially media around the edges of the holes/gaps, is streamed.

You can also apply K2 security features to FTP access.

When using FTP in a shared storage environment, ensure that all FTP communication takes place on the FTP/streaming network, and not on the Control network.


Copyright © 2015 Grass Valley USA, LLC. All rights reserved. K2 Summit 9.4 gvtp_20150218_00:14:46