<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Boot disks in SAN in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854849#M653105</link>
    <description>HPUX Enterprise OE includes:&lt;BR /&gt;&lt;BR /&gt;Online JFS (aka Full VxFS)&lt;BR /&gt;GlancePlus Pak&lt;BR /&gt;HPOV Performance Agents (aka MeasureWare)&lt;BR /&gt;MirrorDisk/UX&lt;BR /&gt;&lt;BR /&gt;Plus of course the base Veritas Volume Manager 3.5m -- that comes with Free Mirroring but only on rootDG.&lt;BR /&gt;&lt;BR /&gt;But if your Bootdisk (on a SAN) is already a protected LUN (ie. RAID5 or RAID10 on your SAN Array) -- why bother with MirrorDisk/UX?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 03 Jun 2004 07:28:30 GMT</pubDate>
    <dc:creator>Zinky</dc:creator>
    <dc:date>2004-06-03T07:28:30Z</dc:date>
    <item>
      <title>Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854831#M653087</link>
      <description>Hello guys,&lt;BR /&gt;&lt;BR /&gt;my question wishes some replies from your great experience on HP-UX systems.&lt;BR /&gt;&lt;BR /&gt;What are issues to have boot disks (boot disk + mirror) in SAN (Storage Area Network)?&lt;BR /&gt;&lt;BR /&gt;I think about a slow boot (slower than boot disks inside the machine) and performance issues on network.&lt;BR /&gt;It also could be another point of failure for Disk Array.&lt;BR /&gt;&lt;BR /&gt;Other hints according to your experience?&lt;BR /&gt;&lt;BR /&gt;Thanks and best regards,&lt;BR /&gt;Ettore</description>
      <pubDate>Wed, 26 May 2004 04:04:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854831#M653087</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2004-05-26T04:04:20Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854832#M653088</link>
      <description>I haven't done this and I understand it is quite a new facility.  However, in my opinion, I would much much prefer to have a local disk to boot off.  If your machine isn't attached to the SAN, you can't boot it.  I admit if all your data is on the SAN annd the SAN isn't available there isn't much point in booting it but I just like being able to boot.</description>
      <pubDate>Wed, 26 May 2004 04:19:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854832#M653088</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2004-05-26T04:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854833#M653089</link>
      <description>Ettore,&lt;BR /&gt;&lt;BR /&gt;Same here, no experience. It can be usefull if you have more than one identical server in case of desaster recovery.&lt;BR /&gt;I would prefer local disks for swap.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;&lt;BR /&gt;Gideon</description>
      <pubDate>Wed, 26 May 2004 04:30:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854833#M653089</guid>
      <dc:creator>G. Vrijhoeven</dc:creator>
      <dc:date>2004-05-26T04:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854834#M653090</link>
      <description>Using fiber there should be less network speed issues.&lt;BR /&gt;Maybe the whole network could be a point of failure (eg: cables, NIC)&lt;BR /&gt;You may want to implement a redundant boot nic.&lt;BR /&gt;eg.&lt;BR /&gt;&lt;BR /&gt;     MirroredDiskArray&lt;BR /&gt;      |            |    &lt;BR /&gt;      |            |&lt;BR /&gt; Controller1-Controller2&lt;BR /&gt;      |    \  /    |&lt;BR /&gt;      |     \/     |&lt;BR /&gt;      |     /\     |&lt;BR /&gt;      |    /  \    |&lt;BR /&gt;  SANswitch1  SANswitch2&lt;BR /&gt;      |            |&lt;BR /&gt;      |            |&lt;BR /&gt;     NIC1         NIC2&lt;BR /&gt;      |            |&lt;BR /&gt;         Server&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Any comments are welcome.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Peace, R&amp;gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 26 May 2004 04:33:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854834#M653090</guid>
      <dc:creator>Roberto Polli</dc:creator>
      <dc:date>2004-05-26T04:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854835#M653091</link>
      <description>these f*ing html blew up spaces from my diag but it should be readable.&lt;BR /&gt;&lt;BR /&gt;Swap space issues are meaningful but you may use local swap.&lt;BR /&gt;&lt;BR /&gt;Maybe you can have problems upgrading NIC firmware or nic driver. Don't know how is singel-user booting tru san-storage but the server should see the fiber like a scsi device (but I'm not sure about it!!!)&lt;BR /&gt;Peace ,r</description>
      <pubDate>Wed, 26 May 2004 04:39:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854835#M653091</guid>
      <dc:creator>Roberto Polli</dc:creator>
      <dc:date>2004-05-26T04:39:02Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854836#M653092</link>
      <description>For some systems (like Windows) one puts the system disk onto the SAN so that it can be replicated by the storage array to a desaster recovery site where an identical spare server is located.&lt;BR /&gt;&lt;BR /&gt;Running the system disks on the SAN is a hot topic for OpenVMS and Tru64 Unix systems, because both can use a common system disk within a cluster. It is less of a problem, because the AlphaServer console has good boot support and diagnostic tools.&lt;BR /&gt;&lt;BR /&gt;It limits the system management a little bit, because patches are rolled out only once. The downside, of course is, that you are now depended on one copy of the system disk, but we all know that breakfast is not free ;-)&lt;BR /&gt;&lt;BR /&gt;You could use value-added services on the storage array like snapshots or clones to protect your data or make it available for tests. Not every operating system has a powerful volume manager.&lt;BR /&gt;&lt;BR /&gt;A local disk with a pre-installed operating system and up-to-date drivers is still a nice thing. It adds additional diagnostics for some systems and you don't have to pull your system up from CD-ROM - I have seen cases where the drivers on the CD-ROM were too old and I could no longer access a storage array with recent firmware.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Roberto,&lt;BR /&gt;if you attach your drawing as a .TXT file there is less reason to curse ;-)</description>
      <pubDate>Wed, 26 May 2004 06:59:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854836#M653092</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-05-26T06:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854837#M653093</link>
      <description>We have over 200 "systems" booting from the SAN, basically because we have over 200 virtual partitions across 50 N-class servers. Some older equip (like K's) didn't work, so we scrapped them from booting off the SAN. &lt;BR /&gt;&lt;BR /&gt;You need to check with your SAN switch, SAN disk, and server providers to determine the interoperibility issues. &lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Wed, 26 May 2004 07:43:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854837#M653093</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2004-05-26T07:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854838#M653094</link>
      <description>Ettore,&lt;BR /&gt;&lt;BR /&gt;I am currently prototyping SecurePath 3.0D - which has support for boot,swap and dump on SAN devices(including EVA). Despite it being withdrawn twice already, I am finding it remarkably robust and fast too. We will be rolling it to production very soon once we get an Okay from HP on SecurePath 3.0D being once more on G.A.&lt;BR /&gt;&lt;BR /&gt;Harry, &lt;BR /&gt;&lt;BR /&gt;What SAN environment are you booting off your servers? DO you use SecurePath/AutoPath or simply PV links?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 26 May 2004 09:38:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854838#M653094</guid>
      <dc:creator>Zinky</dc:creator>
      <dc:date>2004-05-26T09:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854839#M653095</link>
      <description>Nelson,&lt;BR /&gt;&lt;BR /&gt;emc/McData switches with EMC symm's and clariions.&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Wed, 26 May 2004 09:43:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854839#M653095</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2004-05-26T09:43:10Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854840#M653096</link>
      <description>Harry,&lt;BR /&gt;&lt;BR /&gt;And HP "supports" this environment?&lt;BR /&gt;&lt;BR /&gt;I suppose you use PVLINKS for Path protection?&lt;BR /&gt;</description>
      <pubDate>Wed, 26 May 2004 09:45:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854840#M653096</guid>
      <dc:creator>Zinky</dc:creator>
      <dc:date>2004-05-26T09:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854841#M653097</link>
      <description>Although you can have the boot disks inside the SAN,I would prefer to boot from internal disks. because the  SAN could have depending of your configuration more points of failure.  &lt;BR /&gt;Before choice SAN you should revise your San enviroment to see the possible points of failure. (switch,disk,etc..)&lt;BR /&gt;&lt;BR /&gt;E.</description>
      <pubDate>Wed, 26 May 2004 11:48:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854841#M653097</guid>
      <dc:creator>Emilio Brusa</dc:creator>
      <dc:date>2004-05-26T11:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854842#M653098</link>
      <description>Well we will possibly be "brave" enough to proceeed since we have a redundant SAN... Half the SAN components, HBA's, Cabling, Core Switches can be allowed to fail. Of course Disk arrays are not supposed to Fail ;-)&lt;BR /&gt;</description>
      <pubDate>Wed, 26 May 2004 12:15:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854842#M653098</guid>
      <dc:creator>Zinky</dc:creator>
      <dc:date>2004-05-26T12:15:43Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854843#M653099</link>
      <description>Just don't tell that the disk arrays ;-)</description>
      <pubDate>Wed, 26 May 2004 12:30:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854843#M653099</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-05-26T12:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854844#M653100</link>
      <description>Good morning guys.&lt;BR /&gt;&lt;BR /&gt;Nelson,&lt;BR /&gt;I agree with you about redundanted environment. Of course with good attention boot disks in SAN is possibile and it works.&lt;BR /&gt;Even, from your words and descriptions, it seems that boot disks in SAN is better than boot disks inside the machine!&lt;BR /&gt;Really do you think this?&lt;BR /&gt;&lt;BR /&gt;Altogether I agree with Uwe about his first post. He talked about Tru64; Trucluster on Tru64 (and maybe in future on HP-UX!) works in a way that all disks are shared (boot disks too). That is a functionality of Trucluster and (of course) is not a problem to share boot disks (even about that I can be critic!).&lt;BR /&gt;But on HP-UX Service Guard just shares data disks.&lt;BR /&gt;Definitively  I think that it is not a good idea to configure boot disks in SAN (thus shared boot disks). Even redundanted environment has too many points of failure. Also (not as last) the thought that anyone handles Disk Array (for example to configure volume groups on other HP-UX systems attached to Disk Array) can harm my boot disks.&lt;BR /&gt;&lt;BR /&gt;The only one advantage to configure boot disks in SAN is economic side. Is it worth to do that?&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Ettore</description>
      <pubDate>Thu, 27 May 2004 03:42:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854844#M653100</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2004-05-27T03:42:43Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854845#M653101</link>
      <description>Ettore,&lt;BR /&gt;&lt;BR /&gt;OpenVMS and Tru64 Unix require a separate license to enable mirroring. It is just a question if you buy a license for each server -or- a separate backplane RAID controller to mirror your boot disks -or- use the mirror functionality of your SAN-based storage array that you already have paid for.&lt;BR /&gt;&lt;BR /&gt;How is this on HP-UX? I can't really say I have experience with it, but following the forums it sounds like LVM is 'standard'.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Allow me a small correction? OpenVMS allows booting multiple cluster memebers from one single shared system disk per hardware architecture - in a Tru64 Unix cluster each member needs a small boot disk containing the kernel and configuration data, the remainder it then on one common disk.</description>
      <pubDate>Thu, 27 May 2004 07:25:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854845#M653101</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-05-27T07:25:28Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854846#M653102</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;yes, LVM is standard, mirror needs a license on HP-UX too.&lt;BR /&gt;&lt;BR /&gt;Thanks for your explanation about OpenVMS and Tru64; corrections/clarifications always are welcome! :-)&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Ettore</description>
      <pubDate>Thu, 27 May 2004 07:43:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854846#M653102</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2004-05-27T07:43:58Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854847#M653103</link>
      <description>Ettore.&lt;BR /&gt;The new machines like rp8420,rp3410 with enterpise OE, include the mirror license now.&lt;BR /&gt;&lt;BR /&gt;E.</description>
      <pubDate>Wed, 02 Jun 2004 15:39:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854847#M653103</guid>
      <dc:creator>Emilio Brusa</dc:creator>
      <dc:date>2004-06-02T15:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854848#M653104</link>
      <description>Hi Emilio,&lt;BR /&gt;&lt;BR /&gt;are you sure about that?&lt;BR /&gt;I think that mirror license has to be purchased apart. If you have a machine where mirror is already installed (with license) then I think that HP configured it for you but normally it is not so.&lt;BR /&gt;&lt;BR /&gt;Otherwise can you provide a document or anything to sustain your information?&lt;BR /&gt;&lt;BR /&gt;Thanks and best regards,&lt;BR /&gt;Ettore</description>
      <pubDate>Thu, 03 Jun 2004 03:59:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854848#M653104</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2004-06-03T03:59:23Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854849#M653105</link>
      <description>HPUX Enterprise OE includes:&lt;BR /&gt;&lt;BR /&gt;Online JFS (aka Full VxFS)&lt;BR /&gt;GlancePlus Pak&lt;BR /&gt;HPOV Performance Agents (aka MeasureWare)&lt;BR /&gt;MirrorDisk/UX&lt;BR /&gt;&lt;BR /&gt;Plus of course the base Veritas Volume Manager 3.5m -- that comes with Free Mirroring but only on rootDG.&lt;BR /&gt;&lt;BR /&gt;But if your Bootdisk (on a SAN) is already a protected LUN (ie. RAID5 or RAID10 on your SAN Array) -- why bother with MirrorDisk/UX?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Jun 2004 07:28:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854849#M653105</guid>
      <dc:creator>Zinky</dc:creator>
      <dc:date>2004-06-03T07:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Boot disks in SAN</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854850#M653106</link>
      <description>Hi everybody,&lt;BR /&gt;&lt;BR /&gt;it is important to clear all things:&lt;BR /&gt;&lt;BR /&gt;Emilio,&lt;BR /&gt;you said:&lt;BR /&gt;&amp;gt;The new machines like rp8420,rp3410 with enterpise OE, include the mirror license now.&lt;BR /&gt;&lt;BR /&gt;It is exact for an half: MirrorDisk/UX is bundled (of course with license) in OS HP-UX Enterprise OE for the version 11.11.&lt;BR /&gt;Anyway MirrorDisk/UX doesn't depend on model of machine (like rp8420,rp3410).&lt;BR /&gt;Then if you say that&lt;BR /&gt;&lt;BR /&gt;'The new machines like rp8420,rp3410 with enterpise OE, include the mirror license now.'&lt;BR /&gt;&lt;BR /&gt;it is important to specify the version of HP-UX and (of course) Operating Environment.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Nelson,&lt;BR /&gt;question was submitted from Uwe. It is not about my problem. You can find the question of Uwe above.&lt;BR /&gt;Anyway when you said&lt;BR /&gt;&lt;BR /&gt;'HPUX Enterprise OE includes:&lt;BR /&gt;&lt;BR /&gt;Online JFS (aka Full VxFS)&lt;BR /&gt;GlancePlus Pak&lt;BR /&gt;HPOV Performance Agents (aka MeasureWare)&lt;BR /&gt;MirrorDisk/UX'&lt;BR /&gt;&lt;BR /&gt;it is right as for Emilio but it is the truth for HP-UX 11.11 no 11.00.&lt;BR /&gt;Also: MirrorDisk/UX is bundled in that Operating Environment, that is Enterprise OE, not in other OEs. Infact in 11.11 was introduced a new hierarchy of Operating Environment (the following is valid for servers):&lt;BR /&gt;&lt;BR /&gt;HP-UX 11i Base OE&lt;BR /&gt;&lt;BR /&gt;HP-UX 11i Internet OE, bundled with it:&lt;BR /&gt;Â°Unlimited user licenses,Web QoS,JavaVM,Apache websvr,E-speak,Ignite-UX,All networking drivers,EMS,LDAP.&lt;BR /&gt;&lt;BR /&gt;HP-UX 11i Enterprise OE, it is Internet OE plus the following applications:&lt;BR /&gt;Â°PRM,MirrorDisk/UX,OnLineJFS,GlancePlus,HA Monitors.&lt;BR /&gt;&lt;BR /&gt;HP-UX 11i Mission Critical OE, it is Enterprise and Internet OEs plus the following applications:&lt;BR /&gt;Â°MC/ServiceGuard,WLM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;CONCLUSION:&lt;BR /&gt;MirrorDisk/UX with its license is included in HP-UX 11i Enterprise OE or higher OE, no in base or Internet OE.&lt;BR /&gt;&lt;BR /&gt;Therefore your affirmations are good for an half because it is important to specify which HP-UX version and which Operating Environment we are talking about.&lt;BR /&gt;&lt;BR /&gt;Hope this clarifies all doubts.&lt;BR /&gt;Welcome will be other informations.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Jun 2004 09:25:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-disks-in-san/m-p/4854850#M653106</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2004-06-03T09:25:01Z</dc:date>
    </item>
  </channel>
</rss>

