(Issue) Upgrade from Sun Enterprise Volume Manager to Veritas Volume Manager

(Issue) Upgrade from Sun Enterprise Volume Manager to Veritas Volume Manager

Post by humfy1.. » Sun, 25 Feb 2001 10:57:11



Hi,

           We run Solaris 2.6 in our E3500 server.  We want to upgrade our
Sun
   Enterprise Volume Manager 2.5 to Veritas Volume Manager 2.5.6 only. Yes,
   I know it's pretty old version but we need it for testing purposes.
   We have two disk groups, rootdg (i.e.,root disk/mirror disk) and oradg
   (i.e., application disk).
   The root was encapsulated under Sun Enterprise VM 2.5.

            So far, our system is up and I was able to :

        -  Un-encapsulate the root disk

        Filesystem            kbytes    used   avail capacity  Mounted on
        /dev/dsk/c0t0d0s0    2252713  906395 1301264    42%    /
        /dev/dsk/c0t0d0s6    2010712  787274 1163117    41%    /usr
        /proc                      0       0       0     0%    /proc
        fd                         0       0       0     0%    /dev/fd
        /dev/dsk/c0t0d0s1    1502843  370438 1072292    26%    /var
        swap                 3758288      24 3758264     1%    /tmp

        -  Remove all Sun Enterprise Volume Manager 2.5 packages

        -  Install all Veritas Volume Manager 2.5.6 packages

              However, I do not see any VM processes appearing after reboot.
   Here are the  error message after the "vxdctl enable" command :

   # vxdctl enable
   vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration
   copies
        No valid disk found containing disk group; transactions are disabled.
   vxvm:vxdctl: ERROR: enable failed: Error in disk group configuration
copies
   #

   I tried to issue "vxrelocd root & " by hand.
   The vxrelocd and vxnotify appear for a minute and then disappear.  I don't
   see our root device in the list under "vxdiskadm".  We tried
rebooting the
   server again but none of the Veritas VM daemons started up.

   QUESTIONS :

   What could we do to bring the root & other disks back to under Veritas
VM
   2.5.6 control ??
   Is there a compatability  issue with the private region for disks under
Sun
   VM vs Veritas VM ??  How do one
   workaround it, if any ??
   How do one starts up the Veritas Volume Manager 2.5.6 daemons ??

   Thanks much,

   Bill

 -----  Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web  -----
  http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups
   NewsOne.Net prohibits users from posting spam.  If this or other posts