Académique Documents
Professionnel Documents
Culture Documents
Veritas Volume Manager is a storage management application by symantec , which allows you to manage physical disks as logical devices called volumes. VxVM uses two types of objects to perform the storage management 1. Physical objects - are direct mappings to physical disks 2 . Virtual objects - are volumes, plexes, subdisks and diskgroups. a. Disk groups are composed of Volumes b. Volumes are composed of Plexes and Subdisks c. Plexes are composed of SubDisks d. Subdisks are actual disk space segments of VxVM disk ( directly mapped from the physical disks)
1. Physical Disks
Physical disk is a basic storage where ultimate data will be stored. In Solaris physical disk names uses the convention like c#t#d# where c# refers to controller/adapter connection, t# refers to the SCSI target Id , and d# refers to disk device Id. Below figure illustrates how the disk name changes depending on the connection. Physical disks could be coming from different sources within the servers e.g. Internal disks to the server , Disks from the Disk Array and Disks from the SAN.
configured unknown
connected
unconfigured unknown <== disk not configured unconfigured unknown < == disk not configured
# cfgadm -c configure c1::dsk/c1t0d0 # cfgadm -c configure c1::dsk/c1t0d0 # cfgadm -al Ap_Id c0 c0::dsk/c0t0d0 c0::rmt/0 c1 c1::dsk/c1t0d0 c1::dsk/c1t1d0 # devfsadm #echo|format <== now you should see all the disks connected to the server Additional Procedure : Click here to check the procedure to add Internal FC-AL disks disk disk disk tape scsi-bus Type scsi-bus Receptacle Occupant connected Condition
configured unknown
connected connected
connected
connected connected
configured unknown <= Disk configured now configured unknown <= Disk configured now
Using the traditional operating system-dependent format c#t#d# Using an operating system-independent format that is based on enclosure names
c#t#d# Naming Scheme Traditionally, device names in VxVM have been represented in the way that the operating system represents them. For example, Solaris and HP-UX both use the format c#t#d# in device naming, which is derived from the controller, target, and disk number. In VxVM version 3.1.1 and earlier, all disks are named using the c#t#d# format. VxVM parses disk names in this format to retrieve connectivity information for disks. Enclosure-Based Naming Scheme With VxVM version 3.2 and later, VxVM provides a new device naming scheme, called enclosure-based naming. With enclosure-based naming, the name of a disk is based on the logical name of the enclosure, or disk array, in which the disk resides.
error indicates that the disk has neither been initialized nor encapsulated by VxVM. The disk is uninitialized. online indicates that the drive has been initialized or encapsulated. online invalid indicated that disk is visible to VxVM but not controlled by VxVM
If disks are visible with format command but not visible with vxdisk list command, run below command to scan the new disks for VxVM # vxdctl enable Now you should see new disks with the status of Online Invalid 2. Initialize each disk with vxdisksetup command #/etc/vx/bin/vxdisksetup -i <disk_address> after running this command vxdisk list should see the status as online for all the newly initialized disks
The Diskgroup named Diskgroup_o1 is created using 4 different VM disks named as vxdisk_0x, vxdisk_oy, vxdisk_oz and vxdisk_oa The diskfgroup Diskgroup_01 was configured with 4 different volumes i.e. 1. Concat_vol 2. striped_vol 3. mirror_vol and 4. raid5_vol Concat_vol is a concatenation volume with single plex i.e. con_plex01 inside,
and con_plex01 was build up using 4 subdisks of different size Striped_vol is a striped volume with single plex i.e. stripe_plex01 inside, and stripe_plex01 was build up using 4 subdisks of same size
mirror_vol is a mirrored volume with two plexes named mplex01 and mplex02 inside, each plex is copy of other. Both the plexes formed with different subdisks of either same size or different size.
raid5_vol is a raid5 ( striped with parity) volume which build up using 3 different plexes formed with the subdisks of 3 different VM disks.
Volumes
6. Create filesystem on top of volumes using mkfs or newfs, and you can create either VXFS filesystem or UFSfilesystem