Product specifications
Table Of Contents
- Title Page
- Contents
- Chapter 1 Installation Overview 15
- Chapter 2 Installing Software on Interplay Servers 30
- Chapter 3 Installing Software on Interplay Clients 67
- Chapter 4 Installing Optional Software 82
- Chapter 5 Installing and Configuring an Interplay Archive Engine 93
- Chapter 6 Additional Configuration Topics 97
- Chapter G Installing and Configuring the Interplay Streaming Server 108
- Chapter H Workgroups with Multiple ISIS Systems 125
- Appendix A SR2500 Slot Locations 138
- Appendix B Configuring the Copy Provider Server 142
- Appendix C Configuring the Move Provider Server 151
- Appendix D Installing Cards on the Interplay Transfer Server 154
- Appendix E Avid Interplay Port Usage 158
- Symbols and Conventions
- If You Need Help
- Interplay Documentation
- Viewing Help and Documentation on the Interplay Portal
- Avid Training Services
- Installation Overview
- Using the Interplay Installers
- Copying the Interplay Installers to a Server
- Creating a Recovery Image for the AS3000
- Upgrading Your System
- Installation Check Lists
- Set Up and Configure an Avid Shared Storage System
- Network Considerations
- User Names and Passwords Required For Avid Shared Storage and Product Servers
- Required Application Keys
- Installing Software on Interplay Servers
- Selecting the 32-Bit or 64-Bit Version of Avid Service Framework
- Starting the Interplay Server Installer
- Installing Software on the Interplay Engine Server
- Installing Software on the Interplay Transfer Server
- Installing Software on the Media Services and Media Services Provider Servers
- Installing Software on an Avid Interplay Media Indexer Server
- Configuring Media Indexer Servers and Clients
- Installing Software for Interplay Web Services
- Installing the Stream Publish Service and Auto-Publish Support
- Installing Software on Interplay Clients
- Installing Optional Software
- Installing and Configuring an Interplay Archive Engine
- Additional Configuration Topics
- Using Antivirus Software in an Interplay Environment
- Troubleshooting Firewalls and Avid Interplay
- Integration of Journal Data into the Database
- Mounting Workspaces as Drives: Lettered versus Letterless
- Using Time Synchronization in an Avid Interplay Environment
- Installing the Lookup Service on a Separate Server
- Connecting Systems Directly to the Lookup Service
- Installing and Configuring the Interplay Streaming Server
- Interplay Streaming Server and Direct Play of Proxy Media
- Streaming Server Configuration
- Check List for Installing and Configuring the Streaming Server Software
- Upgrading Interplay Stream Server v2.3 or Earlier
- Installing and Configuring the Streaming Server Software
- Uninstalling an Interplay Streaming Server
- Changing the Name of the Interplay Streaming Server
- Changing the Name of the Streaming Server Execution User
- Installing and Configuring an Additional Streaming Server
- Searching for Streamable Master Clips
- Workgroups with Multiple ISIS Systems
- Understanding Multiple ISIS Workgroups
- Check List for Adding Multiple ISIS Systems to a Workgroup
- Requirements for Multiple ISIS Workgroups
- Adding Remote ISIS Systems to ISIS Client Software
- Configuring Media Indexer for Additional ISIS Systems
- Adding Remote ISIS Systems in the Interplay Administrator
- Mounting ISIS Workspaces as UNC Paths
- Working with Media Services and Interplay Transfer in a Multiple ISIS Workgroup
- SR2500 Front View
- SR2500 Slot Locations
- Running the Copy Provider on an SR2500 System
- Copy Provider Configuration on an AS3000
- ISIS Connections and Client Software Installation
- Creating Copy Provider User Accounts for ISIS and Interplay
- Running the Copy Provider on an SR2500 System
- Move Provider Configuration on an AS3000
- ISIS Connections and Client Software Installation
- Creating Move Provider User Accounts for ISIS and Interplay
- Interplay Transfer Server Slot Locations and Network Connections
- Installing Cards in the Interplay Transfer Server
- Index
Mounting Workspaces as Drives: Lettered versus Letterless
99
Both core database and journal file are used for engine operations, like ingest, searching, or
deletion. The integration of data in the journal file into the core database is happening constantly
in a background thread.
The journal file can grow in size when the Interplay Engine is extremely busy (for example,
during a database schema upgrade), but will eventually shrink back to its default size (8 MB for
the CCS database _InternalData, 32 MB for AvidWG and AvidAM). Journal integration is no
longer suspended when a backup is performed. Therefore, journal data does not accumulate
when a backup is running.
If a Severe Error Occurs
If a severe error occurs during integration of journal data into the core database, the Interplay
Engine suspends the integration. Such severe error cases include:
• Failure of integration of journal data into the core database
• Failure to read/write from the journal file
• Failure to do deletes in the streamed property store (this is a central step in the journal
integration)
Usually in such cases, the Interplay Engine rejects all further write operations and reports an
error code in the server log and to the clients trying to perform write operations. There are cases
where the Interplay Engine can continue operating and adding data to the journal file, but this
data is not integrated into the core database.
Journal integration relies on disk access to the _Database folder at all times.
There is one point in time when the engine relies on the journal integration to be finished (at all
other times it is done in a parallel thread). This one point is when a database is loaded, for
example, when a database is brought up, a failover was triggered, or a cluster was taken offline
and back online. At this point, when the database is loaded, the journal integration is enforced.
Integration needs to go through and finish so that the database can be cleared and go online (be
accessible by clients).
Mounting Workspaces as Drives: Lettered versus
Letterless
Avid editing applications, Interplay Assist, and Avid Instinct require Avid shared storage client
software to function as clients in an Avid Interplay workgroup. Explicit mounting of workspaces
as drives might or might not be necessary, depending on your particular workflow. In general,
there is no harm in mounting the workspaces that you need.