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

About GV STRATUS system databases
The GV STRATUS system has an SQL database, which contains the following databases:
GV STRATUS Database : The database that provides the core asset management functionality to
the GV STRATUS system. The database contains a repository of media asset management
information about the GV STRATUS system. Other components in the system refer to the GV
STRATUS Database for necessary information during configuration or while the system is
operating. This is a SQL database. The SQL database name is MediaFrame.
License Management Database : The database for the assignment of GV STRATUS licenses and
roles to groups and users This is a SQL database. The SQL database name is LicenseManager.
Ingest Database : The database for the Scheduler tool. This is a SQL database. The SQL database
name is ISDB.
SDB : SDB is the acronym for Simple Database, which is the database server component for
Aurora Playout. It provides status on clips and on playlists associated with NCS rundowns.
Workflow Database : The database for the workflow engine. Stores the workflow templates. This
is a SQL database. The database name is MediaFlow.
WfPersistence Database : The database for the runtime data of the workflow engine. Stores the
current state of running workpackages. This is a SQL database. The database name is
WfPersistence.
Rules Engine Database : The database for the Rules Engine. Stores the rules and the current state
of the active rules. This is a SQL database. The database name is RulesEngine.
On the GV STRATUS Core server, default directories for SQL database-related files are as follows:
• Database Engine user databases — D:\SQL
• Database Engine user database logs — C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data
• Database Engine TempDB files — D:\SQL
• Database Engine TempDB log files — C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data
• Database Engine backup files —
C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup
About redundant K2 SANs
If your GV STRATUS system accesses a redundant K2 SAN, it introduces some considerations for
operation and maintenance. A redundant K2 SAN has two K2 Media Servers (FSMs) that have the
role of media file system server. These are redundant servers, so either server can be primary and
either server can be backup. At any given time, one operates as the primary server and the other
operates as the backup server. All K2 SAN media access takes place via the primary server, with
the backup server online in a standby mode. Should a fault occur on the primary, a failover event
occurs in which the backup becomes primary and the former primary shuts down.
In the GV STRATUS application you do not see the two K2 Media Servers in the Navigator tree-view.
Instead, you see the K2 SAN represented as one location in the Assets view. Regardless of which
redundant server is currently primary, you see no difference in your view of assets. This view of
2013 12 19 GV STRATUS Installation and Service Manual 159
Understanding system concepts