User`s guide

Controlling Clip Mirror Operation
007-4403-003 125
• If content resides on the mirror platform and is absent from the primary
SGI Media Server, a message is generated in /usr/vtr/adm/logs/vtrlog on
the primary SGI Media Server.
• Clip removal or renaming on the primary SGI Media Server generates clip removal
or renaming on the mirror platform. The clip may be removed manually from the
mirror using an MVCP commands (CRM).
Primary and Mirror Platform Failures
If the primary SGI Media Server becomes unavailable while being actively mirrored, the
mirror platform attempts to reconnect and reestablish mirror operations. This feature
persists until service to the primary SGI Media Server is restored.
In a dual-server environment, if the primary server becomes unavailable for an extended
period of time, you can reconfigure the redundant server to be the primary server. When
the original primary server is available again, you can reconfigure it as the new
redundant server. All clips on the new primary server are then automatically copied to
the newly organized and enabled mirror platform.
Clip mirroring ceases if the mirror platform fails. When the platform is restored, the
service resumes; all new or changed clips will be transferred from the primary
SGI Media Server. Once the clip caches on the primary SGI Media Server and mirror
platform are fully synchronized, the the clip mirror subsystem monitors the primary
SGI Media Server for content changes to the clip cache.
Controlling Clip Mirror Operation
The file /usr/vtr/config/system-defaults/clipmirror holds the control
parameters specific to configuring the clip mirror subsystem. Table 10-1 lists the four