User`s guide

128 007-4403-003
10: Clip Mirror Configuration
Alternatively, the mirror platform can replace the primary SGI Media Server, and the
former primary SGI Media Server can be configured as a mirror platform upon service
resumption.
Configuring Primary and Mirror Platform Filesystems
The SGI Media Server filesystem requires precise tuning and configuration to provide
optimal resource allocation. Therefore, it is important to match filesystem structures
between the primary SGI Media Server and a mirror platform. Nonmatching filesystem
structures may impede operation. The following steps ensure that the filesystems match:
1. Verify that the clip content filesystem on the mirror platform matches the real-time
extent size of the primary SGI Media Server. As root, enter the following
command:
# xfs_growfs -n /usr/vtr/clips
The output should resemble the following, which has been slightly reformatted:
meta-data=/usr/vtr/clips/ isize=256 agcount=8, agsize=8192 blks
data = bsize=16384 blocks=65536, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 1 bsize=16384
log =internal bsize=16384 blocks=1000
realtime =external extsz=2097152 blocks=4445586, rtextents=34731
In the last line, the extsz value is the extent size of the filesystem.
2. On the mirror platform, use the versions command to verify that the following
subsystems are installed:
• vst_eoe.sw.clipmirror
• vst_eoe.sw.ftpd
3. On the primary SGI Media Server, verify that the vst_eoe.sw.ftpd component is
installed.
4. On the mirror platform, verify that the configuration file
/usr/vtr/config/system-defaults/clipmirror contains clip mirror
controls and values with one control specification per line. A comment line is
denoted with a leading # character. Remove the # for each control desired for mirror
platform configuration as described in section “Controlling Clip Mirror Operation”
on page 125.