Grass Valley K2 Storage System Instruction Manual v.3.2 Sep.24 2007 - Manual (Page 749)

September 7, 2007 K2 Storage System Instruction Manual 749
Bind RANK
media access at full bandwidth. The background bind process is useful when doing
initial system installation and configuration, as it does not require the long wait
time required for full bind. You can have RAID disks binding while you move on
to other tasks that require RAID media access.
With either type of binding process, you should bind multiple RANKs
simultaneously, to reduce the overall time required to bind disks.
Bind RANK
Binding disk modules formats them into a logical units called RANKs. The disks that
make up a RANK are accessed as a contiguous disk space. Disk modules must be
bound before they can be part of the video storage file system.
You can use the Storage Utility to bind disk modules as RAID 1, RAID 3, RAID 5,
or as hot spare RANKs, depending on the storage needs of your system.
For simplicity, the Storage Utility only allows binding the first available (at the top of
the Available Disks list) contiguous disk modules into RANKs. After binding, disk
modules become slot specific and cannot be moved to other disk module slots.
Refer to “About RANKs and LUNs in Storage Utility” in Chapter 15, Overview of K2
Storage Tools.
The requirements for this procedure are as follows:
• You must access Storage Utility (via the K2 System Configuration application
login) with permissions equivalent to K2 administrator or higher.
• When you access Storage Utility, the K2 Storage System must be offline.
• All iSCSI clients and K2 Media Clients in the K2 Storage System must be shut
down.
To bind a RANK, do the following:
1. In the tree view, right-click the Unbound node and select Bind . (Peer controllers
that share the same set of disks are automatically selected as a pair.)