Beginner’s Lesson – VERITAS Volume Manager for Solaris


I have started ( aka in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' You can connect me at -

Loading Facebook Comments ...

52 Responses

  1. Rex di Bona says:

    Very nice, but… why would you want to use VxVM on Solaris anyway?
    SVM is cheaper (free), and (from my tests), in every case faster than the equivalent VxVM layout. With soft partitons SVM no longer requires fixed partitions.
    Or, with ZFS you have no need for the brain spasms that are required for using VxVM and a whole lot more besides. In my opinion, given Soalris 10 is now over 6 years old VxVM for Solaris is a strictly legacy product only.

  2. Sanjay Kumar Verma says:

    Good One!!

    Please keep posted on the same.

  3. ramdev says:

    Rex, your point is very valid. my post is basically for those sa who are still supporting decade old enterprise networks. for example the financial firms cannot have the luxury of moving all their applications out of this legacy configuration ( solaris + vxvm) , and the support team who work there still need the expertise on those configurations. :)

  4. ramdev says:

    @Sanjay- you will see more related posts , for sure.

  5. Carlito says:

    Nice lesson. Do you know where I can download Veritas volume manager for Solaris. Thanks.

  6. Raul says:

    Thank you!!!!!!!!

  7. Mohammad says:

    Hi Ram Kumar,

    very good lesson for veritas beginers..

  8. Naresh says:

    Hi ,
    can you please give a complete notes or pdf any link for veritas VM .I like this post, same like this do u have any book or videos please send me the link 

  9. Yogesh Raheja says:

    @Rex, their are still some advantages of VXVM over SVM. Specially in VCS where VXVM is highly recommended and required to support VCS. Though its complete business policy by Symantec :). On the other hand ZFS is much powerful but still it will take some time to grab the market demand. Till that time VXVM will remain dominent aas far as Solaris is concerned.

  10. Naresh says:

    Hi Ram

    can u post anything regarding VERITAS NET BACKUP


  11. Viru says:

    HI Ram,

    Please post more about VXVM ,,, This lesson is very good for new starter..

  12. Yogesh Raheja says:

    Hi Viru, You can get lots of posts on VXVM under Veritas Tab. Also we will keep posting more on VXVM. :).

  13. Ramdev says:

    Hello Viru, Actually Yogesh referring to below page … just have a look at beginners lessons

  14. Rajeswari says:

    Can you please explain the relation between offset value and disk alignment number.

    what does it mean • Subdisks should be cylinder aligned.

    • Ramdev says:

      Hi Rajeswari,

      what does it mean • Subdisks should be cylinder aligned.
      >> Diskalign/nodiskalign is a layout feature used while performing Vxassist operations. When we say Subdisks are cylinder aligned ( default option), subdisks will be created beginning on cylinder boundaries and they will be extended to match the end of a cylinder.

      Can you please explain the relation between offset value and disk alignment number.
      >> I will explain you if you have specific example.

  15. pramath says:

    Please explain Most and Common Troubleshooting Processes and easy methods, Disaster recovery at various instances in VXVM (Real Time Scenarios) if available.

  16. Yogesh Raheja says:

    @Pramath, kindly refer below link and let us know if you want solution of any problem which encountered:

  17. Mushtaq says:

    Hi , 

    i want to confirm which disk is used by oracle , which disk falls under vxvm and which disk is utilised by the OS only. 

    vxvm list shows different names 
    solaris shows different. 

    any advise to confirm . 

    my environment have , 

    solaris 10 > vxvm > vcs > oracle 

    thanks in advance.

  18. Mushtaq says:

    further explanation : 

    one one system : 
    root@aurhselux115# vxdisk list
    DEVICE       TYPE            DISK         GROUP        STATUS
    Disk_0       auto:cdsdisk    zonedisk     zonedg       online
    Disk_2       auto:cdsdisk    –            –            online udid_mismatch
    Disk_6       auto            –            –            error
    Disk_7       auto            –            –            error
    Disk_8       auto            –            –            error
    Disk_9       auto:none       –            –            online invalid
    Disk_10      auto:cdsdisk    –            –            online
    Disk_11      auto:cdsdisk    –            –            online
    Disk_12      auto:cdsdisk    –            –            online

    On second system 
    root@aurhselux116# vxdisk list
    DEVICE       TYPE            DISK         GROUP        STATUS
    Disk_0       auto:cdsdisk    –            –            online
    Disk_1       auto            –            –            error
    Disk_2       auto:cdsdisk    –            –            online udid_mismatch
    Disk_4       auto            –            –            error
    Disk_5       auto:none       –            –            online invalid
    Disk_6       auto:none       –            –            online invalid
    Disk_7       auto:none       –            –            online invalid
    Disk_8       auto:none       –            –            online invalid

    both are under vxvm / vcs  , want to identify what is there on which disk , anyway from the header etc we can identify ? 

    thanks again.

  19. Mushtaq says:

    how to compare between , vxdisk list and format command to confirm ? which disk we are talking about ? any idea thanks

  20. Yogesh Raheja says:

    @Mushtaq, below is the explanation to your query:

    There are mainly three types of layout of disk in vxvm:

    Sliced Disk layout:
    private and public region slices are on separate partitions (usually slices 3 & 4). This type of disk is not suitable for moving between different O/S’s but are suitable for boot partitions. OS disk under veritas are of Sliced layout

    CDS (Cross-platform Data Sharing):
    private and public regions are one slice (usually slice 7). This type is suitable for moving between different O/S’s but not suitable for boot partitions. So this cannot be used for OS disk.

    Private and public are the same partition but continuous (usually slice 3).

    Firstly dont be confused in format or vxdisk outputs. Format will show you total no. of disks recongnised by your OS irrespective of veritas/emc/local disks. If veritas is installed then vxdisk list is the command which is ths major command to identify the disks are under Veritas or Not.

    Now considering your example, check the TYPE & STATUS FIELD:

    Disk_0, Type: auto:cdsdisk, FIELD: online —> Means the disk is under veritas and is online.

    Disk_9 Type: auto:none FIELD: online invalid –> Means the disk is under OS but not under Veritas (online invalid)

    Disk_2 Type: auto:cdsdisk FIELD: online udid_mismatch –> Means the disk is under veritas, usually you will see udid_mismatch in EMC disks.

    • Ramdev says:

      @yogesh – those are useful tips.

      @musthaq – I guess you are asking this question either to configure, unconfigure or to perform the maintenance on the disk.

      as long as the question is related to isolating the veritas disks with OS it is pretty straight forward. what every appears as “online invalid” that is not taken care by veritas. And again there is an exception, there are cases that we add EMC disks and leave them for later configurations. And if you are not the one who configured the disk, then you should be little careful to differentiate an new and unconfigured vxdisk from an OS disk.

      The few checks that i recommend in addition to ” format or vxdisks ” are :

      >> df output to check what filesystems are using what disks
      >> metastat -p output to check what disks are occupied by SDS
      >> check the iostat -xdn to see whether the disk making any io read/write, and this is useful if you see any disks are in use by oracle / sybase as raw devices.
      >> finally prttvtoc on the disk to check if the layout is familiar to me.

  21. Praveen says:

    Hi Ramdev,

    i m regularly watching your articles. It is very nice and insteresing to read. I m working as linux sysadmin. i want to learn vertias in our home, but reading such article i can gain knowlodge withour any practicals. i m seriously searching for articles which gives clear installation of vertias in linux machine. But i didnt find any doc related to installation. can you please provides me the such a article or any link for installation of vertias in linux 32 bit machine.


  22. AIX ADMIN says:

    Hi Rex di Bona,

    Storage is costly and depending on the need u can keep prod (critical) data / devlopment (less critical) data on different storage such as hitachi/emc and netapp respectively.they are all integrated by veritas in such a way that different os/ hw platform and storages can coexists and the same command can be used in all the flavours and get rids of compatibility issues of vendor o.s’s using their own technologies and systems as all of them can use it.

  23. Bruce Shaw says:

    This is OK for simple disks. How about the situation where you’re attaching to a SAN using Veritas multipathing instead of Solaris’. I need to add more disk. I’ve currently got two LUNs presented but 50+ disks in my list for “format”. When I get the extra LUN, I’m going to get even more. How do I sort out which belongs to what?

  24. Ramdev says:

    Hi Bruce, In case of  large number disks we just have to do some prework to map the each filesystem to corresponding veritas disk and then to the actual native disk mentioned in the format command. This is a mandatory pre-check task during the storage migrations. Probably i should add some notes on this part, Thanks for raising the question.

  25. Laxxi says:

    Hi, The above article is really very comprehendable..but as i went through the doc, i got few doubts like

    1) role of Disk group. 2)are plexeses made of subdisks of disks under same diskgroup. 3) a pictorial representation would be more helpful.


  26. Ramdev says:

    DiskGroups are used to group the all related physical disks with similar purpose  ( e.g. one disk group for sybase database volumes, one fro oracle database volume, once for application data …etc),

    Whenever we think about any veritas logical components i.e. subdisk, plex, volume , they all should come from same disk group.  because these components cannot span across multiple diskgroups.

  27. Laxxi says:

    thnaks Ram!!

  28. Nav says:

    I have a sparc box with root disks encapsulated. It has free space.

    Is it ok to create a new volume on already encapsulated disk. It is running vertias 4.x. I need to create more swap space and wondering if it is ok to create new volume on the encapsulated rootdg. Any precautions to take while doing this? OR is it just same like how you create a new volume on vxvm/vxfs.

    The other option i have is to create a huge swapfile on the SAN lun [vxfs].

    Any input is appreciated?

    • Ramdev says:

      Hi Nav, We cannot shrink or grow the volumes which are created before the encapsulation. But, for the creation of new volumes it should be fine as long as you have sufficient space.

  29. Santosh says:

    I want to install Veritas in solaris at my pc. Please let me know from which site i will get veritas software

  30. Hema says:

    ver useful… Thanx..

  31. Rajkamal says:

    Actually, it would have been more helpful if you could explain with command on how to create the layout you provided in the example figure:

    Like how to create / name those disks with vxdisk_0x, vxdisk_0y, vxdisk_0z,vxdisk_0a and then how to initialize with command (vxdisksetup), add them to dg etc. It will be good.

  32. Ramdev says:

    Hi Raj, I believe you are talking about the topic about this continuation post…..

  33. shiva says:

    hey it may be silly question but i’m not understanding what is difference b/w snap object and snap volume , dco object and dco volume

  34. shiva says:

    what is diff b/w snap object and snap volume ,dco object and dco volume

  35. LAKSHMI says:

    When we a add a new device to Veritas,, which commands like vxconfigd, vxdctl init or vxdctl enable are needed to execute to identify the new device.
    Please let me know , I’m bit confused at this point

  36. Ramdev says:

    Lakshmi, –

    Few basic things to understand here –

    1 . The vxconfigd communicates configuration changes to the kernel and modifies configuration information stored on disk. Startup scripts usually invoke vxconfigd at system boot time. The vxconfigd daemon must be running for VxVM to operate properly.
    2. The vxdctl utility manages the state of the volume configuration daemon, vxconfigd.
    3. Each system will have a volboot file that contains contains a host ID that VxVM uses to establish ownership of physical disks

    About your question

    >>> vxdctl init – Reinitializes the volboot file with a new host ID , and that required only once during initial setup of the vxvm.

    >>> vxdctl enable – import all disk groups, and rebuild the volume device node directories. And This operation causes vxconfigd to scan for any disks that were newly added since vxconfigd was last started.

    And above two command assumes that you vxconfigd actively running in your server, and if it is not running they will alert you to start vxconfigd before you actually use the vxdctl commands. You can also check the vxconfigd status with below command

    # vxdctl mode
    If mode: enabled, then vxconfigd running
    if mode: not-running , then This message indicates that vxconfigd is not running:

    then you can start vxconfigd with

    # vxconfigd

  37. Amit Sharma says:

    Very Clear & easy Doc for beginners. Really appreciated to the way of presentation of SVM & VXVM.
    very nice mapping of physical disks and VX disks.

    do you have any next step of the Doc ? for further studies.

    Cheers \\ Amit Sharma

  38. Suman Das says:

    if we create a volume with four disk like your eample how many disk failure are tollerable?

    • Ramdev says:

      Hi Suman, it depends on what kind of volume you are going to create? if you chose Raid-1 or Raid-5, it can only tolerate max 1. disk

  39. Sarang Sangram says:

    unable to pictures and diagram. please help

  1. August 10, 2011

    […] have already covered the first Learning Objective from the post  ”Veritas Volume Manager for System Adminstrators ” […]

  2. September 15, 2015

    […] Beginner’s Lesson – VERITAS Volume Manager for Solaris […]

  3. September 18, 2015

    […] Read – VxVM Beginner’s Lesson […]

Leave a Reply

Your email address will not be published.

[contact-form to='' subject='New Learning Request Submitted'][contact-field label='Name' type='name' required='1'/][contact-field label='Email' type='email' required='1'/][contact-field label='Learning Request' type='textarea' required='1'/][contact-field label='Are you Looking for ' type='radio' required='1' options='Paid Training,Free Training'/][/contact-form]

What is your Learning Goal for Next Six Months ? Talk to us