Transferring a Storage Asset

Many storage solutions support HA configurations in Sun xVM Ops Center. Different storage solutions require different procedures. You must determine the procedures that are required to transfer the storage asset that stores the /var/opt/sun/xvm directory structure in your particular storage solution.

This example procedure assumes that the mountpoint property of the example ZFS file system is set to legacy, to resolve an issue regarding when ZFS and LOFS mounts take place in the system boot process. The legacy value indicates that the legacy mount and umount commands, and the /etc/vfstab file, will control mounting and unmounting this ZFS file system. Other storage solutions typically use these legacy commands and the /etc/vfstab file to control mounting and unmounting operations. Refer to Release Notes for information about the LOFS race condition issue.

Perform the following procedure on the secondary Enterprise Controller.

To Transfer a Storage Asset to the Secondary Enterprise Controller

Caution – The following example procedure is based on the example Solaris OS-based storage solution that is described in Configuring Storage for High Availability. You must determine what specific procedures to use, depending on the storage solution that you have implemented.

1. If it is required for your particular storage solution, physically attach the storage asset to the secondary Enterprise Controller.
   
2. Transfer the storage asset that stores the /var/opt/sun/xvm directory structure to the secondary Enterprise Controller.
   For example, if you use ZFS to store the /var/opt/sun/xvm directory structure, you can import the ZFS pool that contains /var/opt/sun/xvm:

   # zpool import
     pool: OpsCenter
       id: 16117101211372343022
    state: ONLINE
   action: The pool can be imported using its name or numeric identifier.
   config:
   
           OpsCenter    ONLINE
             mirror     ONLINE
               c1t65d0  ONLINE
               c1t66d0  ONLINE
   
   # zpool import OpsCenter
   #
   

   The zpool import command with no argument shows the list of ZFS pools that you can import. The zpool import OpsCenter command imports the OpsCenter pool.
   

3. Verify that the ZFS file system exists and that its mount point is set to legacy.
   For example:

   # zfs list
   NAME            USED  AVAIL  REFER  MOUNTPOINT
   OpsCenter       382M   134G  1.50K  none
   OpsCenter/xvm   382M   134G   382M  legacy
   #
   

   In this example, the OpsCenter/xvm file system contains the Sun xVM Ops Center data from the primary Enterprise Controller, and its mount point is set to legacy.
   

4. Edit the /etc/vfstab file and add an entry for the ZFS file system above the three lofs entries for /etc/opt/SUNWuce, /var/opt/SUNWuce, and /opt/SUNWuce.
   For example:

   (output omitted)
   OpsCenter/xvm   -       /var/opt/sun/xvm        zfs     -       yes     -
   /var/opt/sun/xvm/uce/etc.opt    -       /etc/opt/SUNWuce        lofs    -       yes     -
   /var/opt/sun/xvm/uce/var.opt    -       /var/opt/SUNWuce        lofs    -       yes     -
   /var/opt/sun/xvm/uce/opt        -       /opt/SUNWuce    lofs    -       yes     -
   

   In this example, the device to mount is OpsCenter/xvm, the mount point is /var/opt/sun/xvm, the file system type is zfs, and the mount at boot option is set to yes.
   

5. Mount the new file system, and then verify that it is mounted.
   For example:

   # mount /var/opt/sun/xvm
   # mount
   (output omitted)
   /var/opt/sun/xvm on OpsCenter/xvm read/write/setuid/devices/exec/xattr/atime/dev=4010002 on Mon Feb 23 09:51:55 2009