GRASS VALLEY K2 - Expanding the Media File System by Capacity

10. If you have Macintosh systems accessing the K2 SAN, you should check that the SNFS file
system volume is configured correctly on the Macintosh systems.
11. Place the K2 SAN back online.
Expanding the media file system by capacity
Prerequisites are as follows:
• The system must have one LUN per RANK. Expansion by capacity is not supported on systems
with multiple LUNs per RANK.
• The expansion chassis that you add to your K2 SAN must have unbound, unlabeled disks.
NOTE: This procedure should only be attempted under the supervision of qualified Grass
Valley support personnel. Contact your Grass Valley representative for assistance.
If you need to increase the storage capacity of your K2 SAN, you can do so by adding one or more
Expansion Chassis, up to the maximum number of chassis allowed for your level of storage.
1. Rack the Expansion Chassis.
2. If a redundant K2 SAN, do the following:
a) Verify that MPIO is updated to the latest version on all shared storage K2 clients.
b) Put the system into an “original primary” state. This means that for all redundant devices
(switches, servers, RAID controllers, etc.) the current device acting as primary is the one that
was initially configured as primary when the system was originally installed.
3. On the K2 Media Server with the role of primary media file system/metadata server, save a copy
of the following files to a different location:
D:\snfs\config\default.cfg (on some systems this file is named gvfs_hostname.cfg, where
hostname is the name of the SNFS file system server.)
D:\snfs\config\cvlabels
4. Power down the K2 SAN, including RAID storage devices.
5. Power up the RAID storage devices. Verify that they stabilize in an operational state with no
errors indicated.
6. Power down RAID storage devices.
7. Cable and configure the Expansion Chassis.
8. Power up the RAID storage devices. Verify that they stabilize in an operational state with no
errors indicated.
9. Start up the K2 SAN.
10. Bind the RANKs in the Expansions Chassis using Background Bind.
11. When binding is complete, put the K2 SAN in an offline state as follows:
a) You must access Storage Utility (via the K2Config application login) with permissions
equivalent to K2 administrator or higher.
b) When you access Storage Utility, the K2 SAN must be offline.
c) All iSCSI clients and K2 clients in the K2 SAN must be shut down.
12. Restart all K2 Media Servers. Do not use the standard startup processes here. Just start up the
server(s) and wait until the Windows desktop appears. Especially do not use Server Control
Panel or start Failover Monitor.
02 February 2012 K2 SAN Installation and Service Manual 313
Administering and maintaining the K2 SAN