Veritas/DiskSuite

I am working on a study on Veritas Volume Manager and Solstice DiskSuite.
Do you have any information on these products : I'd like to have advantages and defaults of each of them. I have link on document on Web but I'd like to have user's point of view.
Thanks in advance for your help.

Hi,
You've already got volume manager, so why not use it? If you install ODS as well as VXVM, you're just complicating the setup of the machine.
You've got veritas already installed, just use this!

Similar Messages

  • D1000

    We have a D1000 disk array already configured with 8 x 9GB disks. We need to add more space
    and are about to order 2 x 18GB disks. Is there any problem with mixing disks of different
    sizes within a D1000 array?
    All the best
    Peter Wickett

    Since this is "Just a Box Of Disks" there should be no problem mixing drive sizes. Due consideration will have to be given if using any type of mirroring software, Veritas, DiskSuite, etc..

  • Solstice DiskSuite or Veritas Volume Manager

    With regards to Solaris 8,
    I plan to use DiskSuite to create a few 0+1 volumes for our new database server. Any reason for me to consider Veritas Volume Manager instead?
    We have an E5000 running Solaris 2.6 with Veritas Volume Manager 3.2, we are only using it for 0+1 volumes(vxfs). No snaphosts, fast I/O or any other bells and whilste of VM are being used.

    apologies my original post was incorrectly posted to the wrong forum.

  • DiskSuite or Veritas Volume Manager

    With regards to Solaris 8,
    I plan to use DiskSuite to create a few 0+1 volumes for our new database server. Any reason for me to consider Veritas Volume Manager instead?
    We have an E5000 running Solaris 2.6 with Veritas Volume Manager 3.2, we are only using it for 0+1 volumes(vxfs). No snaphosts, fast I/O or any other bells and whilste of VM are being used.

    Hi,
    You've already got volume manager, so why not use it? If you install ODS as well as VXVM, you're just complicating the setup of the machine.
    You've got veritas already installed, just use this!

  • Solstice DiskSuite 4.2.1 Installation

    Hi,
    I have a SUN fire 880 system running Solaris 8 and 72GBX10 Disk.
    right now 8 disk are configured in Veritas Volume Manager and one disk has root and other file system and one more disk is still free so I am planning to mirror root disk with free disk in ( Solstice DiskSuite 4.2.1) please advice me
    My Qustion is
    1>Is it possible ???
    2>From where I can get Solstice DiskSuite 4.2.1 packages???.
    Thanks in advance..
    Bhupal

    Yes, but some versions of VxVM require a 'rootdg' remain. You may or may not prefer to simply use VxVM to mirror root.
    The packages are on disk2 of the installation media in the EA folder.
    Darren

  • Backup MaxDB 7.7.06.09 to Veritas Netbackup 6.5 fails

    We want to backup MaxDB to Veritas Netbackup server.
    According documentation found about this topic the backup is configured
    by creating 3 files: bsi.env, initWDO.par (for backint for MaxDB) and
    initWDO.utl (for backint for Oracle). The contents of these files are shown below.
    When running the backup, it seems that backint for MaxDB ends with return code 2,
    the error message received is:
      -24920,ERR_BACKUPOP: backup operation was unsuccessful
      The backup tool failed with 2 as sum of exit codes.
    Unfortunately no further errors/warnings are shown that points in any direction
    what's going wrong here.
    We start the backup via the following dbmcli-command:
    dbmcli -u control,****** -d WDO -uUTL control,****** backup_start BACKData_WDO
    (for the time being without xuser entries, first make sure the backup is ok)
    The files dbm.ebl, dbm.prt and several others do not show any additional details/hints.
    It seems as if the "save data quick" to the named pipe is ok, the sql-code returns "0".
    After this the backint for MaxDB should read the named pipe and write it to stage-files,
    but backint (for MaxDB) ends with return code 2.
    Any idea what might go wrong here?
    With kind regards,
    R. Hoogeveen
    The Netherlands
    File bsi.env:
    =========
    BACKINT                /sapdb/WDO/db/bin/backint
    INPUT                  /tmp/backint4maxdb_WDO.in
    OUTPUT                 /tmp/backint4maxdb_WDO.out
    ERROROUTPUT            /tmp/backint4maxdb_WDO.err
    PARAMETERFILE          /sapdb/data/wrk/WDO/initWDO.par
    TIMEOUT_SUCCESS        600
    TIMEOUT_FAILURE        300
    ORIGINAL_RUNDIRECTORY  /sapdb/data/wrk/WDO
    File initWDO.par:
    =============
    STAGING AREA:                  /tmp/stageWDO 1 GB
    FILES PER BACKINT CALL:        1
    BACKINT:                       /usr/openv/netbackup/bin/backint
    PARAMETERFILE OF BACKINT:      /sapdb/data/wrk/WDO/initWDO.utl
    HISTORY FILE:                  /sapdb/data/wrk/WDO/backint_history_WDO.log
    INPUTFILE FOR BACKINT:         /tmp/backint4ora_WDO.in
    OUTPUTFILE FOR BACKINT:        /tmp/backint4ora_WDO.out
    ERRORFILE FOR BACKINT:         /tmp/backint4ora_WDO.err
    MAXIMAL DELAY OF BACKINT CALL: 30
    File initWDO.utl:
    =============
    switch_list /tmp/.switch_WDO.lis
    switch_sem /tmp/.switch_WDO.sem
    switch_log /tmp/.switch_WDO.log
    drives 1
    client wdocsz01
    server backfire
    policy sap_WDO

    Lars,
    The /tmp/backint4maxdb.err file tells me:
    Backint for Oracle was unsuccessful.
    (Unfortunately that was all information in this file.)
    The backint4ora.in file tells me:
    /tmp/stageWDO.0
    (looks ok to me, also at the time backint4ora was started the stage file was created with non-zero size)
    The backint4ora.out file tells me:
    ERROR: incorrect format or option in .utl file (-p)
    (this seems as if the -p option is not recognized by the backint4ora executable)
    When I run this executable manually as user sdb it shows me the commandline that I should use, including the -p option.
    One strange thing I notice is that the order of the options is different from the commandline that is executed.
    (in the usage it shows -p as almost last parameter, the command executed has -p in the middle; I will see if I can execute the backint4ora command manually, since I have the stage file available, I have copied it during the process)
    The backint4ora.err file is empty.
    The commandline of the dbmcli command I execute shows me another interesting error message,
    this might also be the source of all problems here.
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    Could not get external backup ID's from the backup tool.
    I tried to retrieve the external backup id's manually for medium BACKDataWDO, it show me OK without any external backup id's.
    I am not sure, but I think this is correct since no successfull backup was created yet with external backup tool.
    Can it also be that the parameter "history file" from the initWDO.par file is set wrong?
    Currently it is set to "/sapdb/data/wrk/WDO/backint_history_WDO.log" (see above also), but I can imagine
    that this should be set to the dbm.knl or dbm.ebf file ??
    With kind regards,
    Roger Hoogeveen

  • How to install & confgiure Oracle9i on Veritas Cluster Server

    Hi,
    I want to know how to install oracle9i on Veritas Cluster Server having OS as Solaris 9. Also How to configure oracle in VCS so that it can be failover.
    I really appreciate the replies.
    Thanks,
    Shrikant

    I want to install following component
    Oracle 9i form server & report server
    Oracle HTTP Server in SSL mode
    Oracle As Web Cache
    Regards
    Arvind

  • SAP R/3 4.7 migration using Veritas PDC solution

    Hi,
    I would like to do a heterogeneous system copy.
    My current environment:-
    OS= IBM AIX
    DB=Oracle 9i
    DB size=6TB
    Storage= Veritas Storage foundation suite (Portable Data Container)
    Target system:-
    OS=HPUX
    DB=Oracle 9i
    DB size=6TB
    Storage= Veritas Storage foundation suite (Portable Data Container)
    Instead of using SAP tool (SAPINST,migmon, R3ta) to export/import the SAP system.
    Can I make use of the VERITAS -PDC solution? Whereby I will do a snapshot of the Oracle datafile.
    And then do some veritas pdc conversion to HPUX . And present the datafile to HPUX (target system).
    Is this supported by SAP? What is the impact if SAP say it is not supported method to do migration?
    I saw a document say it is not supported, but it is dated 2005.
    Thanks.
    Best Regards,
    CK chai
    Does anyone

    The first thing you should be aware of:
    If you do heterogeneous migrations you must have a certified migration consultant on-site, otherwise you loose support for problem occurring through the migration and for the target system (see http://service.sap.com/osdbmigration --> FAQ).
    The only "supported official" way is doing an R3load export and import.
    You can use other ways (e. g. also transportable tablespaces with Oracle 10g) but the responsibility of doing that is in the hand of the migration consultant.
    Markus

  • Veritas volume manager for solaris 10

    Hi All
    which version veritas volume manager will support solaris 10 06/06.
    can you just update a link for reference
    Regards
    RPS

    Hello,
    we are currently using solaris 9 with veritas volume manager 3.5.So i would like to know if i upgrade to solaris 10 06/06.whether i can use 3.5 or not.
    Using the Veritas (Symantec) support site, I have found the following document
    VERITAS Storage Solutions 3.5 Maintenance Pack 4 for Solaris
    http://seer.support.veritas.com/docs/278582.htm
    The latest supported version listed for VxVM 3.5 with MP4 applied is Solaris 9. That means the answer is NO.
    I understand that searching the Veritas knowledge base might be tough and time consuming, but it's their product ...
    Michael

  • Veritas volume manager on Solaris 10(X86)

    is it possible to install veritas volume manager on solaris 10 (x86) ?

    You should check the supported operating system matrix for Storage Foundation to see what they support. But yes, Solaris x64 is supported. I don't think they support 32-bit x86.
    Darren

  • What is Veritas HA, and How to verify that Veritas HA system is "lights on"

    Hi, Friends:
    I have two questions,
    1.What is Veritas HA?
    2.How to verify that Veritas HA system is "lights on"?
    thank you very much,
    Jerry

    Veritas HA = Veritas High Availability.
    http://www.google.com/search?q=veritas+HA&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

  • How to backout a Recommended Patch cluster deployment in Solstice disksuite

    Hello Admin's,
    I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
    concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
    1) Will shutdown the applications and the databases on the server:
    2) Will capture the output of the following commands :
    df -k
    ifconfig -a
    contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
    metastat -p
    netstat -rn
    prtvtoc /dev/rdsk/c1t0d0s0
    prtvtoc /dev/rdsk/c1t1d0s0
    3) We bring the system to the ok prompt
    4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
    =======================================================================================
    user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
    /dev/dsk
    Filesystem kbytes used avail capacity Mounted on
    /dev/md/dsk/d10 8258597 3435895 4740117 43% /
    lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
    lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
    bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
    d10: Mirror
    Submirror 0: d11
    State: Okay
    Submirror 1: d12
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 16779312 blocks
    d11: Submirror of d10
    State: Okay
    Size: 16779312 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s0 0 No Okay
    d12: Submirror of d10
    State: Okay
    Size: 16779312 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s0 0 No Okay
    user1@myserver>
    ===================================================================================
    ok nvalias backup_root <disk path>
    Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
    ok printenv boot-device
    boot-device= disk net
    ok setenv boot-device disk backup_root net
    boot-device= disk backup_root net
    In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
    ok boot backup_root
    user1@myserver>metadb -i
    flags first blk block count
    a m p luo 16 1034 /dev/dsk/c1t0d0s7
    a p luo 1050 1034 /dev/dsk/c1t0d0s7
    a p luo 2084 1034 /dev/dsk/c1t0d0s7
    a p luo 16 1034 /dev/dsk/c1t1d0s7
    a p luo 1050 1034 /dev/dsk/c1t1d0s7
    a p luo 2084 1034 /dev/dsk/c1t1d0s7
    o - replica active prior to last mddb configuration change
    u - replica is up to date
    l - locator for this replica was read successfully
    c - replica's location was in /etc/lvm/mddb.cf
    p - replica's location was patched in kernel
    m - replica is master, this is replica selected as input
    W - replica has device write errors
    a - replica is active, commits are occurring to this replica
    M - replica had problem with master blocks
    D - replica had problem with data blocks
    F - replica had format problems
    S - replica is too small to hold current data base
    R - replica had device read errors
    user1@myserver>df -k
    Filesystem kbytes used avail capacity Mounted on
    /dev/md/dsk/d10 8258597 3435896 4740116 43% /
    /dev/md/dsk/d40 2053605 929873 1062124 47% /usr
    /proc 0 0 0 0% /proc
    fd 0 0 0 0% /dev/fd
    mnttab 0 0 0 0% /etc/mnttab
    /dev/md/dsk/d30 2053605 937231 1054766 48% /var
    swap 2606008 24 2605984 1% /var/run
    swap 6102504 3496520 2605984 58% /tmp
    /dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
    /dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
    user1@myserver>metastat d40
    d40: Mirror
    Submirror 0: d41
    State: Okay
    Submirror 1: d42
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194828 blocks
    d41: Submirror of d40
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s4 0 No Okay
    d42: Submirror of d40
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s4 0 No Okay
    user1@myserver>metastat d30
    d30: Mirror
    Submirror 0: d31
    State: Okay
    Submirror 1: d32
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194828 blocks
    d31: Submirror of d30
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s3 0 No Okay
    d32: Submirror of d30
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s3 0 No Okay
    user1@myserver>metastat d50
    d50: Mirror
    Submirror 0: d51
    State: Okay
    Submirror 1: d52
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 10487070 blocks
    d51: Submirror of d50
    State: Okay
    Size: 10487070 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s5 0 No Okay
    d52: Submirror of d50
    State: Okay
    Size: 10487070 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s5 0 No Okay
    user1@myserver>metastat -p
    d10 -m d11 d12 1
    d11 1 1 c1t0d0s0
    d12 1 1 c1t1d0s0
    d20 -m d21 d22 1
    d21 1 1 c1t0d0s1
    d22 1 1 c1t1d0s1
    d30 -m d31 d32 1
    d31 1 1 c1t0d0s3
    d32 1 1 c1t1d0s3
    d40 -m d41 d42 1
    d41 1 1 c1t0d0s4
    d42 1 1 c1t1d0s4
    d50 -m d51 d52 1
    d51 1 1 c1t0d0s5
    d52 1 1 c1t1d0s5
    d60 -m d61 d62 1
    d61 1 1 c1t0d0s6
    d62 1 1 c1t1d0s6
    user1@myserver>pkginfo -l SUNWmdg
    PKGINST: SUNWmdg
    NAME: Solstice DiskSuite Tool
    CATEGORY: system
    ARCH: sparc
    VERSION: 4.2.1,REV=1999.11.04.18.29
    BASEDIR: /
    VENDOR: Sun Microsystems, Inc.
    DESC: Solstice DiskSuite Tool
    PSTAMP: 11/04/99-18:32:06
    INSTDATE: Apr 16 2004 11:10
    VSTOCK: 258-6252-11
    HOTLINE: Please contact your local service provider
    STATUS: completely installed
    FILES: 150 installed pathnames
    6 shared pathnames
    19 directories
    1 executables
    7327 blocks used (approx)
    user1@myserver>
    =======================================================================================
    5) After successfully testing the above we will bring the system to the single user mode
    # reboot -- -s
    6) Detach the following sub-mirrors :
    # metadetach -f d10 d12
    #metadetach -f d30 d32
    #metadetach -f d40 d42
    #metadetach -f d50 d52
    # metastat =====> (to check if the submirror�s are successfully detached)
    7) Applying patch on the server
    After patch installation is complete will be rebooting the server to single user mode
    # reboot -- -s
    confirming if patch installation was successful (uname �a) .
    8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
    Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
    # metattach d12 d10
    # metattach d30 d32
    #metattach d40 d42
    # metattach d50 d52
    # metastat d10 =====> (to check the submirror is successfully reattached)
    user1@myserver>uname -a ; cat /etc/release ; date
    SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
    Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
    Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
    Assembled 12 December 2002
    Mon Apr 14 17:10:09 BST 2008
    -----------------------------------------------------------------------------------------------------------------------------

    Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
    I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
    They try to generate those every 6 months, but the schedule often slips.
    The two most recent were sol10 11/06 and sol10 8/07.

  • CSM with Veritas HA geographic redundancy fails over without visible reason

    Hello.
    Cisco Security Manager shuts down and Veritas fails it over to another site, I have no idea why. It is clean installation without elements.
    In Veritas engine log I found this:
    2013/02/06 12:52:22 VCS INFO V-16-2-13001 (KV-CSM-01-1) Resource(APP_CSManager): Output of the completed operation (monitor) 60012-202: The following process is not running     Process= NameServer     State  = Administrator has shut down this server     Pid    = 0     RC     = 143     Signo  = 0     Start  = 2/6/2013 12:35:58 PM     Stop   = 2/6/2013 12:52:05 PM     Core   = Not applicable     Info   = Server started by admin request
    Veritas CSM resource log:
    2013/02/06 12:52:22 VCS ERROR V-16-2-13067 Thread(3916) Agent is calling clean for resource(APP_CSManager) because the resource became OFFLINE unexpectedly, on its own.
    CSM syslog:
    Feb 06 12:52:08 127.0.0.1 100: <30>   dmgt[9004]: 3021(I):Died method called for process (NameServer, pid=9700).Feb 06 12:52:08 127.0.0.1 100: <30>   dmgt[9004]: 3021(I):Died method called for process (EDS, pid=8444).
    Eds.log is attached.
    NameServer.log is empty.
    As we can see from monitor.pl (csm agent script), EDS and NameServer are critical processes to run CSM.
    What I should do to prevent such behaviour?

  • XML Reports end with WARNING Status, Using Virtual Hostname by Veritas HA

    Dear Experts,
    We have upgraded our Application from 11.5.10.2 to R12, 12.1.3. Now in the Upgraded Application we are unable to open/view any of the XML based Concurrent Reports. All the XML Concurrent Reports are ending in Status WARNING.
    When we click on the View Out put, we are just getting the XML code and not the XML based reports.
    The log file of Out Put Postprocessor shows the following errors:
    ================================================
    5/28/13 12:40:20 PM] [STATEMENT] [960882:RT4152834] Get Output Type
    [5/28/13 12:40:20 PM] [STATEMENT] [960882:RT4152834] XML file name: /mnt/oracle/ERPROD/inst/apps/ERPROD_erp-lh-dr/logs/appl/conc/out/o4152834.out
    [5/28/13 12:40:20 PM] [STATEMENT] [960882:RT4152834] XML file is on node: ERP-LH-DR
    [5/28/13 12:40:20 PM] [UNEXPECTED] [960882:RT4152834] java.sql.SQLException: Exhausted Resultset
    at oracle.jdbc.driver.OracleResultSetImpl.getString(OracleResultSetImpl.java:1224)
    at oracle.apps.fnd.cp.util.CpUtil.getCanonicalLocalNode(CpUtil.java:127)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:244)
    at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)
    [5/28/13 12:40:20 PM] [960882:RT4152834] Completed post-processing actions for request 4152834.
    And error like below:
    The error we are getting from the Application log files are related to Hostname. Following is the abstract from the Output Post Processor log.
    [5/29/13 2:56:02 PM] [UNEXPECTED] [960900:RT4155505] java.sql.SQLException: Exhausted Resultset
    at oracle.jdbc.driver.OracleResultSetImpl.getString(OracleResultSetImpl.java:1224)
    at oracle.apps.fnd.cp.util.CpUtil.getCanonicalLocalNode(CpUtil.java:127)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:244)
    at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)
    ===============================================================
    Concurrent Manger Log files shows the following error:
    ===========================================================
    Executing request completion options...
    Output file size:
    430455
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 4158856 on node ERP-LH-DR at 30-MAY-2013 18:53:38.
    Post-processing of request 4158856 failed at 30-MAY-2013 18:53:38 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    ------------- 2) PRINT   -------------
    Not printing the output of this request because post-processing failed.
    Finished executing request completion options.
    Concurrent request completed
    ==========================================================
    **Please suggests:**
    **1- Is there any way to make these XML reports work with Veritas HA, using Virtual hostname**
    **2- Can we identify or pin point from where the Out Put Postprocessor is setting the Physical Hostname.**
    Regards
    Ali Ammar

    Hi,
    The metalink note Output Post Processor Fails Due to java.sql.SQLException: Exhausted Resultset [ID 740529.1], is not related to us, we have already verified that. In our case the Application is running on Virtual Hostname and this virtual hostname is taken care by Veritas Library, ACC.
    Secondly the FND_NODES also shows the Virtual hostname as the application is configured on Virtual Hostname. So in our case its not seems to be comming from the FND_NODES tables, rather it seems that some of the Java files/class is picking it by the OS command uname -a.
    So if we can find that class or environment file of java, we can export the Virtual Hostname as we used it in configuration. Please note that the Concurrent Manager and Application listener are also working fine on the Virtual Hostname, by using the Veritas library.
    Solaris:
    LD_PRELOAD_32=/usr/lib/secure/libvuname.so
    VHOSTNAME=<virtual hostname>
    Please suggest.
    Best Regards
    Ali Ammar.

  • DiskSuite and Live Upgrade 2.0

    I have two Solaris 7 boxes running DiskSuite to mirror the O/S disk onto another drive.
    I need to upgrade to Solaris 8. In the past I have used Live Upgrade to do so, when I have enough free disk space to partition an existing disk or to use a unused disk for the Solaris 8 system files.
    In this case, I do not have sufficient free space on the boot disk. So, what is the best approach? It seems that I would have to:
    1. unmirror the file system
    2. install Solaris 8 onto the old mirror drive using LU 2.0
    3. make the old mirror drive the boot drive
    4. re-establish mirroring, being sure that it goes the right way from the Solaris 8 disk to the old boot disk
    Comments, suggestions?

    I recently built a system (specs below) and installed this card (MSI GF4 Ti4200 VTD8X MS8894, 128MB DDR), and when I try to use Live Update 2 (version 3.33.000, from the CD that came with the card), I get the same message:
    "Warning!!! Your Display Card does not support MSI Live Update 2 function.  Note: MSI Live Update 2 supports the Display Cards of MSI only."
    I'm using the drivers/BIOS that came on the CD: Driver version 6.13.10.4107, BIOS version 4.28.20.05.11.  I see on the nVidia site that they have the 4109 drivers out now, should I try those?  ?(
    I have also made sure to do the suggested modifications to IE (and I don't have PC-cillin installed):
    "Note: In order to operate this application properly, please note the following suggests.
    -Set the IE security setting 'Download signed ActiveX controls' to [Enable] or [Prompt]. (System default is [Prompt]).
    -Disable 'WebTrap' of PC-cillin(R) or any web based anti-virus application when executing MSITM Live Update 2TM.
    -Update Microsoft® Windows® Installer"
    I downloaded a newer version of LIveUpdate (3.35.000), and installed it (after completely uninstalling the old version), and got the same results.  Nothing on my system is currently overclocked.
    Help!
    System specs:
    -Soyo SY-KT400 DRAGON Ultra (Platinum Edition) with latest BIOS & Chipset Drivers
    -AMD Athlon XP Thoroughbred 2100+
    -MSI GF4 Ti4200 VTD8X (MS-8894)
    -WD Caviar Special Edition 80 GB HDD, 8 MB Cache
    -512 MB Crucial PC2700 DDR (one stick, in DIMM #1)
    -TDK 40/12/48 CD R/RW
    -Daewoo 905DF Dynaflat 19" Monitor
    -Windows XP Home Edition, SP1/all other updates current
    -On-Board CMedia 6-channel audio
    -On-Board VIA 10/100 Ethernet
    -Altec-Lansing ATP3 Speakers

Maybe you are looking for