Problem
I need more information on installing and using the Virtual Disk Manager 1.0.0 on SCO OpenServer Release 5.0.0.
Cause
RAID (Redundant Array of Inexpensive Disks) and the Virtual Disk
Manager (VDM) are new features in SCO OpenServer Release 5 Product
Family. This information is a general introduction only; see the
Operating System Administrator's Guide (hardcopy or online) and
the Performance Guide for more details.CONTENTS OF VIRTUAL DISK MANAGER SOFTWARE PACKAGE:
PRODUCT: Virtual Disk Manager
WHAT: Provides software support for RAID (Redundant
Array of Inexpensive Disks) configurations
CURRENT REL: 1.0.0
AVAILABLE: 5/23/95
RUNS ON: SCO OpenServer base products
# OF DISKS: (1) 3.5" disk (release supplement)
OTHER: (1) COLA (licensing card)
(1) Product licensing and registration handbookSCO Virtual Disk Manager Release 1.0.0 is part of the SCO
OpenServer layered products. It is not included with SCO
OpenServer's base operating systems. It must be purchased,
installed, and licensed separately. You will then have the
option to configure virtual disks through the
ScoAdmin==>Filesystem==>Virtual Disk Manager graphical
interface.The VDM product requires only 0.5MB of disk space (520399 bytes)
to install. The RAM requirements depend on the type and number
of virtual disks configured. The more RAID 1, 4, and 5 virtual
disks configured, the more memory the system requires. On a
lightly loaded system with few virtual disks, approximately 500KB
is needed; on a fully configured, busy server an extra megabyte
of memory is required.NOTE: A fast CPU (Pentium) is required to see much performance gain from using virtual disk arrays.
GENERAL PRODUCT INFORMATION:RAID is a storage technique to attain higher reliability and
performance by spreading data across a series of disks known
as a logical disk. VDM is used to configure and maintain these
logical (or virtual) disks.The major benefit of RAID is increased data reliability by
protecting against loss due to a single disk failure. RAID
also protects against loss of availability due to disk related
failure.If implemented properly, RAID can increase the integrity of data, allow for more flexibility in storage management, and with adequate planning, improve overall system performance. Another benefit of the technology is the ability to repair and recover data blocks in the event of a read or a write encountering bad blocks or data corruption on one or more physical disks.
Parts of one or more physical disks can be defined as one or more virtual disk. RAID storage systems can also generally be administered without taking the virtual disk offline, especially when using the "hot spare" capabilities (see below).
RAID TERMINOLOGY:The VDM software is a virtual disk driver that works between the application and operating system's filesystem code and the physical disks:
-----------------------------------
| Application |
-----------------------------------
| System Call Processing |
-----------------------------------
| Filesystem, | Raw I/O |
| Buffer cache | Path |
-----------------------------------
| Virtual Disk Driver |
-----------------------------------
| Physical Disk Driver |
-----------------------------------
| Physical Disk |
-----------------------------------Any disks that currently run on SCO systems can be a part of a virtual disk.
Part of understanding what the RAID levels and virtual disk types are, is understanding some basic terminology:
Piece - An area of contiguous disk space allocated to a virtual
disk. That is, a "piece" of a virtual disk can be a whole disk,
a partition on a disk, or some definable subset of a partition.Disk Array - An array of pieces defined to act as one logical disk.
Cluster size - A configurable virtual "block" size, the size of the data chunks written to the pieces in an array.
Stripe/Data Stripe - A concept of spreading disk reads and writes across all the disk pieces in an array; the number of pieces in an array multiplied by the cluster size gives the length of one "stripe" of data.
Parity - Redundancy (or error-correction) information generated during writes to certain virtual disk types; parity is the exclusive, OR of all the data blocks in a stripe.
VDM currently supports several virtual disk types:
Simple - A virtual disk with the same structure as an ordinary partition in terms of placement and physical continuity of data blocks. Simple disks do not have a cluster size since write requests are not handled by the virtual disk driver, instead they are passed straight to the physical disk driver.
Concatenated - A virtual disk which spans two or more physical disks, allowing logical disk size to be larger than any single physical disk on the system.
Striped (RAID 0) - An array of disk pieces each written in
succession, so data is distributed across every piece in the
array before writing to the first piece again. There is no
parity information generated for RAID 0 arrays.Mirrored (RAID 1) - Two piece virtual disk where the blocks of one disk are replicated exactly ("mirrored") onto the second.
Striped, undistributed parity (RAID 4) - Striped disk array with one of the disk pieces designated as the parity piece.
Striped, distributed parity (RAID 5) - Striped disk array with parity information distributed between all the pieces in the array.
Variations and derivations of these RAID levels are possible,
including duplexing and three-way mirrors. Two of the most common
definitions available are:Striped mirror (RAID 10) - A mirror of two striped virtual disks.
Striped array of arrays (RAID 53) - A virtual disk consisting of two or more RAID 5 (or RAID 4) arrays striped into one large virtual disk.
KNOWN FEATURESThe VDM allows many configuration options and can do most
maintenance functions while virtual disks are online. Virtual
disks are scalable and physical disks can be added and removed
as desired.The RAID level of a disk can "migrate" to another type.
No special hardware is necessary. Virtual disks can be composed
of any supported disk types and host adapters, and disks of any
size can be incorporated.Hot spares can be defined as another piece in an array. If one
disk fails, the spare will be brought online and reconstructed
from the data and parity on the working disks.Repair of virtual disks which have outdated parity can be done in the background while the disk stays online and functional.
KNOWN LIMITATIONSFilesystems on a virtual disk cannot "grow" or "shrink" in size
automatically. Pieces added or removed from a virtual disk will
usually require the filesystem to be recreated manually and data
to be restored from backups.Hot swapping of disks, where one physical disk is removed from an array and another is put in its place, is not yet available. This is a popular RAID feature and may be available as part of an Extended Feature Supplement (EFS) in a future release of the product.
Root and swap are limited to RAID 1 (mirroring) only; there is
no striping available on root and swap. Currently, the boot
filesystem cannot be mirrored, but an upcoming EFS may allow this.Virtual disks are not configurable during operating system install time.
See also
SCO OpenServer 5 Operating System System Administration Guide; SCO OpenServer 5 Operating System Performance Guide.