Other Topic Library Versions

Configure the media file system for bandwidth expansion

  1. If Aurora media is present, modify VolumeConfig.xml.
  2. 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.
  3. From the control point PC, open the K2Config application and launch Storage Utility.
  4. In Storage Utility make sure both old RANKs and new RANKs are displayed.
  5. In Storage Utility, select Tools | Expand File System By Bandwidth and answer Yes to confirm.
  6. 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.
  7. 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
  8. Wait for the process to complete. On a large system this can take over 30 minutes.
  9. A “…succeeded…” message is displayed when done. Click OK and Storage Utility closes.
  10. The K2Config application displays a message informing you to restart servers. Click OK.
  11. Make sure Storage Utility is closed before proceeding.
  12. 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.
  13. 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.
  14. In the K2Config application, do the following for each K2 Media Server with role of iSCSI bridge to verify that you see the correct number of drives:
    1. On the iSCSI Bridge 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.
    2. Click Check.
    3. Restart the K2 Media Server.
    4. Repeat this step to make sure you now see the correct number of drives.
  15. 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.
    1. Record system information Make sure you keep diagrams and other on-site documentation up to date.

Copyright © 2016 Grass Valley Canada. All rights reserved. K2 Summit 9.6 gvtp_20160520_13:06:36