Configure the media file system for bandwidth expansion
If Aurora media is present, modify
VolumeConfig.xml.
Stop services (if running) on K2 Media Servers. .
On a redundant K2 SAN stop the Server Monitor Service. On a
non-redundant K2 SAN stop the MetaData service.
From the control point PC, open the
K2Config
application and launch Storage Utility.
In Storage Utility make sure both old RANKs and new RANKs are
displayed.
In Storage Utility, select
Tools | Expand File System By Bandwidth and
answer
Yes to confirm.
A dialog box opens asking if you want to restripe existing media
after bandwidth expansion. Proceed as follows:
Click
Yes in most cases. This is the typical
response. In any case this does no harm.
Click
No only if you are sure you do not need to
restripe existing media, such as in the following cases:
You have very little
existing media so the fact that it cannot use the new stripe group does not
impact future media operations or capacity.
Your existing media
is to be deleted soon so you don’t care if it uses the new stripe group.
The first of a series of informational screens opens.
Work through the informational screens.
When prompted to retry, if you are not sure if the process
started, you can retry to be sure. Doing so does not cause problems.
The expansion process runs. A dialog box displays progress
Wait for the process to complete. On a large system this can take
over 30 minutes.
A “…succeeded…” message is displayed when done. Click
OK
and Storage Utility closes.
The
K2Config
application displays a message informing you to restart servers. Click
OK.
Make sure Storage Utility is closed before proceeding.
If directed, modify RTIOS.
Depending on your use of the expanded file system, you might need
to change the RTIOS value. This value can be calculated only by Grass Valley
Support. Do this step only under the direction of Grass Valley Support.
As directed, use a text editor to modify the SNFS configuration
file on K2 Media Servers (both primary and backup) with the role of media file
system/database server.
Note: Don’t use the SNFS configuration tool to modify the system
configuration. Doing so causes unexpected changes in the configuration file,
resulting in a failure of the expansion process.
Restart all K2 Media Servers.
Make sure to first start servers with the role of media file
system/metadata server.
When the server that takes the role of FTP server starts, one of
the following happens:
If you answered “Yes”
to restripe existing media in the step above, the Restripe Utility
automatically launches and begins restriping media.
If you answered “No”
to restripe existing media in the step above, the Restripe Utility does not
launch.
In the K2Config application, do the following for each K2 Media Server
with role of iSCSI bridge or LAN Gateway to verify that you see the correct
number of drives:
On the iSCSI
Bridge Server Configuration or LAN Gateway Server
Configuration page, click View Target Drives
and proceed as follows:
If you see all
drives, both old and new, no further sub-steps are necessary. Skip to the next
step in this procedure.
If some drives are
listed as unexposed, continue with the remaining sub-steps in this step.
Click
Check.
Restart the K2 Media Server.
Repeat this step to make sure you now see the correct number
of drives.
Monitor the Restripe Utility.
On a file system with a large amount of existing media, this can
take days.
Note: Do not stop the FTP server once the restripe process begins.
Record system information
Make sure you keep diagrams and other on-site documentation
up to date.