Online Data Manager (ODM) overview and installation

Quick installation

The Quick Installation option is the easiest to use. For each controller, Quick Installation gives you the option of either initializing or encapsulating all disks. If you want to encapsulate some disks on a given controller and initialize others, use Custom Installation instead.

Quick installation allows you to initialize disks on a controller, even if valid partitions are found on those disks. However, you should avoid selecting the initialize option for any disks containing valid data.

With encapsulation, the /etc/vfstab and /etc/swaptab files are updated to ensure that filesystems previously mounted on disk partitions will be mounted on volumes instead.

To use the Quick Installation option:

  1. Select menu item 1 Quick Installation from the vxinstall main menu.

    vxinstall asks you a series of questions for each controller and disk it finds connected to your system. When a default response is displayed in parentheses, press <Enter> to accept that default. At any of the vxinstall prompts, you can select q to completely abandon the initialization and start over.

    All disks are encapsulated or initialized (according to your instructions) at the end of the vxinstall procedure. If you quit vxinstall before it enters its final phase of actually initializing or encapsulating the disks, all disks will be left as they were before vxinstall started.

  2. At the following prompt, indicate whether to encapsulate your boot disk (this example assumes your boot disk is named c0b0t0d0):
       The c0b0t0d0 disk is your Boot Disk. You can not add
       it as a new disk. If you encapsulate it, you will make
       your root filesystem and other system areas on the
       Boot Disk into volumes. This is required if you wish
       to mirror your root file system or system swap area.

    Encapsulate Boot Disk [y,n,q,?] (default: n)

    NOTE: If you are mirroring your swap device, we recommend that you set aside a dedicated dump slice to store possible system dumps. Otherwise, the system may not detect the presence of a system dump on the swap slice.

    vxinstall now goes through each controller and asks you how to handle the disks contained on that controller. vxinstall begins this process for each controller by identifying the controller and generating a list of its disks:

       Generating list of attached disks on c1....
       The Volume Manager has detected the following disks
       on controller c1:
       c1b0t0d0 c1b0t1d0 c1b0t2d0 c1b0t3d0 c1b0t4d0

    Hit RETURN to continue.

    If any disks are listed in the /etc/vx/disks.exclude file, they are listed here separately as excluded disks.

  3. At the following prompt, indicate whether you want to initialize all the disks on the controller.
       Volume Manager Quick Installation For Controller c1 Menu:

    Initialize all disks on this controller? (destroys data on these disks) [y,n,q,?] (default: n)

    If you enter n, vxinstall assumes that you want to encapsulate all disks on the controller instead and displays the following:

       Volume Manager will now try to encapsulate all the
       disks on this controller.  Disks not having valid
       partitions will be initialized.

    Hit RETURN to continue.

  4. At the following prompt, indicate whether you want default disk names to be assigned to all of the disks on the controller.
       Use default disk names for these disks? [y,n,q,?] (default: y)

    If you enter y, vxinstall automatically assigns and lists default disk names for each disk:

       The c1b0t0d0 disk will be given disk name disk01
       The c1b0t1d0 disk will be given disk name disk02
       The c1b0t2d0 disk will be given disk name disk03
       The c1b0t3d0 disk will be given disk name disk04

    Hit RETURN to continue.

    If encapsulation was selected, this list also includes the following message for each disk that can be encapsulated

       The c1b0t0d0 disk has been configured for encapsulation.

    or the following message for empty disks that will be initialized instead of encapsulated:

       The c3b0t2d0 disk appears to be empty.
       Adding as a new disk.

    If you enter n, vxinstall prompts you for a disk name for each disk on the controller individually:

       Enter disk name for c1b0t0d0 [<name>,q,?] (default: disk01)

    For each disk, respond with the desired disk name and press <Enter>.

  5. When all of the disks on the current controller have been named, press <Enter> and repeat Steps 3 and 4 for the remaining controllers on your system.

    When you have completed the vxinstall procedure for all controllers on your system, vxinstall displays a summary of the disks you have designated for initialization (New Disk) or encapsulation (Encapsulate) on each controller:

       The following is a summary of your choices.
       c0b0t5d0 New Disk
       c1b0t0d0 New Disk
       c1b0t1d0 New Disk
       c1b0t2d0 New Disk
       c2b0t2d3 New Disk
       c3b0t0d0 Encapsulate
       c3b0t1d0 Encapsulate
       c3b0t2d0 New Disk
       Is this correct [y,n,q,?] (default: y)

    This is your last chance to review and alter your choices about how to handle any of the disks to be placed under Volume Manager control.

Next topic: Custom installation
Previous topic: Initializing the Volume Manager

© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004