GRASS VALLEY K2 SAN, Installation And Service Manual

Page: 314 / 346

About full/background bind
When binding RAID disks, you can choose to do either a full bind or a background bind. Background
bind is recommended. These binding processes are described as follows:
• Full bind — During this process, the K2 SAN must be in the offline mode. While the full bind
process is underway, disks are not available for data access of any kind. On a large SAN, the
full bind process can take many hours, so you should plan ahead for this process. For example,
binding 750 Gig SATA drives can take up to 3 days.
• Background bind — During this process, the K2 SAN can be in a restricted online mode. Disks
are available for data access, but the overall performance of the RAID storage is significantly
reduced. While the background bind process is underway, you can initiate media access on your
SAN for limited testing of operations, such as record, play, and transfer, but do not run 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
Prerequisites 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 SAN must be offline.
• All iSCSI clients and K2 clients in the K2 SAN must be shut down.
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.
314 K2 SAN Installation and Service Manual 2014 01 27
Administering and maintaining the K2 SAN