Grass Valley GV STRATUS Installation v.3.1 - Manual (Page 160)

the K2 SAN is defined when you configure the Summit MDI in the GV STRATUS Control Panel
application.
In the GV STRATUS Control Panel application, K2 Storage settings provide a view of your K2
SAN that reports the primary or backup status of K2 Media Servers. When you refresh the view the
report of primary/backup status is updated.
If a failover event occurs on the redundant K2 SAN, a proxy-workflow GV STRATUS application
momentarily suspends access to assets on the K2 SAN. After the failover event is complete, you
can repopulate Asset Lists and other views of assets to continue with your media operations. Refer
to "K2 SAN Installation and Service Manual" for more information about K2 SAN failover and
steps for recovery after a failover.
Proxy Encoder iSCSI client requirement
A Proxy Encoder server must be connected to a K2 SAN as an iSCSI client. The reasons for this
requirement are as follows:
• The Proxy Encoder server has the SiteConfig role of K2 FTP Server and runs the FTP server
software. This FTP server software requires the connection to the K2 SAN as an iSCSI client in
order to access the high resolution assets on the K2 SAN.
• The Proxy Encoder software component that runs on the Proxy Encoder server uses FTP, so it
must be configured to use a FTP server. To ensure that adequate FTP bandwidth is available,
the FTP server used is the K2 FTP server on the Proxy Encoder server itself. This keeps the
Proxy Encoder FTP traffic off of the K2 SAN's primary FTP servers.
So the requirement for an iSCSI client connection comes from the K2 FTP server, not the Proxy
Encoder software.
Because the Proxy Encoder software does not require an iSCSI connection, it is possible to run the
software on a GV STRATUS Express server which does not have an iSCSI connection. In this case
the Proxy Encoder software is typically configured to use the FTP server on a stand-alone K2 Summit
system. This suits the design goals of the Express system as a small system with low bandwidth
requirements.
About GV STRATUS markers, Dyno markers, and the K2 database
Marker information is stored in the GV STRATUS database and in the K2/Summit/SAN database.
You can configure the way the GV STRATUS system synchronizes marker information between
the databases. If you use the K2 Dyno Replay Controller as part of your workflow, you must consider
this synchronization, since a Dyno marker is in the K2 database and a GV STRATUS marker is in
the GV STRATUS database.
Another consideration is the number of markers in the K2 database. A very large number of markers
can exceed the capacity of the K2 database. You can check logs on the K2 Summit/SAN system for
messages about the database size. If it exceeds 80MB, there is a risk of database errors. If all GV
STRATUS markers are synchronized to the K2 database the risk of exceeding the capacity increases.
Grass Valley recommends that you only synchronize GV STRATUS markers to the K2 database if
160 GV STRATUS Installation and Service Manual 2013 12 19
Understanding system concepts