4 Replies Latest reply on Feb 12, 2013 10:00 PM by 908067

    jumpstart solaris 8 and veritas file system

      Hi guys,

      I need to clone a a Solaris 8 that has Veritas file system. As far as I know, the license is stick to hostid, so in theory Veritas will not start on the new machine.
      Is there a way to avoid this license issue? I can't modify the source system in any way (production server). I don't mind if the destiantion system has UFS, I just need a solution to do it.

      Any comments or suggestions are welcome.

      Thank you!
        • 1. Re: jumpstart solaris 8 and veritas file system
          Check that new server support Solaris8.

          You have possible two way:
          Buy new license from Symantec. ( New owner of Veritas).
          And it's resolve license issue.

          Use ufs on cloned server.

          Step for clone:
          1. Stop all aplication on production.
          2. Make backup of all file systems of production server. ( For example - use cpio for create backup)

          3. Boot new server from CD-ROM in single mode.
          4. Label boot disk as requre, create requred FS, restore it.
          5. Install Bootblock on new boot disk
          6. Edit /etc/vfstab for change FS from fxfs to UFS
          7. In case new server different type from original- rebuild device tree.
          8. Try boot. Check and fix errors if it present.

          • 2. Re: jumpstart solaris 8 and veritas file system
            In the old days (version 5.0 and earlier) , the license used to bound to the host id.

            Now, licenses are mostly per site or multiple licenses on a single license number....
            latest versions even support keyless licenses (where you accept the responsibility to show Symantec your licenses if they come around to look at it)
            If you install a keyless license, you will just get a message in the syslog every now-and-again, but you wil have full functionality.

            What I would suggest doing the following:

            On the current machine, run #vxlicrep -e

            This will show you what license you do have ....

            Now a bit of reading is required, as we need to see if the license is actually node locked .....

            Here is an example (License number is obviously been "blocked out")


            License Key = 3EZH-VD8O-XXXX-XXXX-XXXX-XXXX-X
            Product Name = VERITAS File System <--------------- specifically for the filesystem
            Serial Number = 1009
            License Type = PERMANENT
            OEM ID = 889
            Point Product = YES
            Node Lock Flag = 0 <----------- not node locked !!!!

            This means that the same license can be used on the new machine.

            Worst case senario, you will have to go onto the machine once the system starts up and run the command

            # vxlicinst


            Lastly, you can always speak to your Symantec representative to make sure that you have the correct license or to obtain one (or even a temprary one) to get you going.

            Hope that helps
            • 3. Re: jumpstart solaris 8 and veritas file system
              Thank you both for your answers!

              I am not an veritas expert (if it wasn't obvious already :) ), so I would be pleased to be able to get rid of veritas FS on the destination server..I wonder if doing a flash archive install, using jumpstart, would help me do that..I found some Oracle doc stating that veritas config info is not gathered by flar, but it's not very clear if it will still deploy on another type of fs (UFS)...
              • 4. Re: jumpstart solaris 8 and veritas file system

                I managed to install the flar on a solaris 8 branded zone , but it was not exactly what I needed.

                When I try to jumpstart the flar on a physical box, everything goes fine until I need to reboot the system (well, first I had to get rid of veritas and this link helped me: http://unixunitedprof.forumandco.com/t35-removing-solaris-from-vxvm-control ) I get the following error:
                {0} ok boot -ar
                Boot device: /pci@1f,4000/scsi@3/disk@0,0:a  File and args: -ar
                Enter filename [kernel/sparcv9/unix]:
                Enter default directory for modules [/platform/SUNW,Ultra-80/kernel /platform/sun4u/kernel /kernel /usr/kernel]:
                Name of system file [etc/system]:
                SunOS Release 5.8 Version Generic_117350-62 64-bit
                Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
                root filesystem type [ufs]:
                Enter physical name of root device
                Cannot assemble drivers for root /pci@1f,4000/scsi@3/disk@0,0:a
                Cannot mount root on /pci@1f,4000/scsi@3/disk@0,0:a fstype ufs
                panic[cpu0]/thread=10408000: vfs_mountroot: cannot mount root
                0000000010407970 genunix:vfs_mountroot+70 (1043e800, 0, 0, 10477832, 80, 14)
                  %l0-3: 000000001043e800 0000000010441fa0 00000000ff000000 000000001043ea88
                  %l4-7: 0000000000000000 0000000010413a20 00000000000c1bf3 0000000000001bf3
                0000000010407a20 genunix:main+8c (10410230, 2000, 10407ec0, 10408030, fff2, 100543ec)
                  %l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000f6c
                  %l4-7: 0000000010431688 000000001047cd68 00000000000da530 0000000000000530
                skipping system dump - no dump device configured
                Resetting ...
                Any suggestions are appreciated. The source and destination machines are different in HW (source is Ultra Enterprise E3500, destination is Ultra 80)

                Thank you!