<?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: Query on Mirrored boot disk failure in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250461#M547384</link>
    <description>As per the above torston comment!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;it's exactly like that!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Deeos</description>
    <pubDate>Thu, 05 Aug 2010 13:35:59 GMT</pubDate>
    <dc:creator>Deeos</dc:creator>
    <dc:date>2010-08-05T13:35:59Z</dc:date>
    <item>
      <title>Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250455#M547378</link>
      <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;Pls clear my doubt,&lt;BR /&gt;&lt;BR /&gt;1. In a running server if primary boot mirrored disk failed,then server will restart or not?&lt;BR /&gt;2. what will happen to running server If alternate boot disk of mirrored vg00 failed&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance&lt;BR /&gt;Ragesh</description>
      <pubDate>Thu, 05 Aug 2010 11:09:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250455#M547378</guid>
      <dc:creator>Rg_4</dc:creator>
      <dc:date>2010-08-05T11:09:44Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250456#M547379</link>
      <description>1) No, it using the other disk&lt;BR /&gt;&lt;BR /&gt;2) if the other disk is still dead? &lt;BR /&gt;Your server cannot run without a boot disk.&lt;BR /&gt;&lt;BR /&gt;if 1 disk remains working, your server will continue, no matter which disk is died.</description>
      <pubDate>Thu, 05 Aug 2010 11:31:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250456#M547379</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-08-05T11:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250457#M547380</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hi:&lt;BR /&gt;&lt;BR /&gt;Other considerations:&lt;BR /&gt;&lt;BR /&gt;Three corollaries to the mirroring recommendation are:&lt;BR /&gt;&lt;BR /&gt;1. Use the strict allocation policy for all mirrored logical volumes. Strict allocation forces mirrors to occupy different disks. Without strict allocation, you can have multiple mirror copies on the same disk; if that disk fails, you will lose all your copies. The allocation policy is controlled with the â  s option of the lvcreate and lvchange commands. By default, strict allocation is enabled.&lt;BR /&gt;&lt;BR /&gt;2. To improve the availability of your system, keep mirror copies of logical volumes on separate I/O busses if possible. With multiple mirror copies on the same bus, the bus controller becomes a single point of failureâ  if the controller fails, you lose access to all the disks on that bus, and thus access to your data. If you create physical volume groups and set the allocation policy to PVG-strict, LVM helps you avoid inadvertently creating multiple mirror copies on a single bus. For more information about physical volume groups, refer to lvmpvg(4).&lt;BR /&gt;&lt;BR /&gt;3. Consider using one or more free disks within each volume group as spares. If you configure a disk as a spare, then a disk failure causes LVM to reconfigure the volume group so that the spare disk takes the place of the failed one. That is, all the logical volumes that were mirrored on the failed disk are automatically mirrored and resynchronized on the spare, while the logical volume remains available to users. You can then schedule the replacement of the failed disk at a time of minimal inconvenience to you and your users. Sparing is particularly useful for maintaining data redundancy when your disks are not hot-swappable, since the replacement process may have to wait until your next scheduled maintenance interval.&lt;BR /&gt;&lt;BR /&gt;rgs,</description>
      <pubDate>Thu, 05 Aug 2010 11:38:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250457#M547380</guid>
      <dc:creator>rariasn</dc:creator>
      <dc:date>2010-08-05T11:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250458#M547381</link>
      <description>1. No, server will use another disk without any hamper!&lt;BR /&gt;&lt;BR /&gt;2. No matter of primary or alternete disk failure, your one of the mirrored disk should active for any fault tolerance!&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Deeos</description>
      <pubDate>Thu, 05 Aug 2010 11:40:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250458#M547381</guid>
      <dc:creator>Deeos</dc:creator>
      <dc:date>2010-08-05T11:40:12Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250459#M547382</link>
      <description>boot up with hpux -lq&lt;BR /&gt;&lt;BR /&gt;if a disk fails either the mirror or primary you will get a LVM message in the syslog.  &lt;BR /&gt;&lt;BR /&gt;Then fix it !&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Aug 2010 13:15:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250459#M547382</guid>
      <dc:creator>Emil Velez</dc:creator>
      <dc:date>2010-08-05T13:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250460#M547383</link>
      <description>It continues to run even if the system is booted without "-lq".&lt;BR /&gt;&lt;BR /&gt;But you need to use "hpux -lq" if you want to reboot the server with a dead disk installed.</description>
      <pubDate>Thu, 05 Aug 2010 13:20:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250460#M547383</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-08-05T13:20:47Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250461#M547384</link>
      <description>As per the above torston comment!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;it's exactly like that!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Deeos</description>
      <pubDate>Thu, 05 Aug 2010 13:35:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250461#M547384</guid>
      <dc:creator>Deeos</dc:creator>
      <dc:date>2010-08-05T13:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Mirrored boot disk failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250462#M547385</link>
      <description>Thx</description>
      <pubDate>Mon, 08 Nov 2010 13:21:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/query-on-mirrored-boot-disk-failure/m-p/5250462#M547385</guid>
      <dc:creator>Rg_4</dc:creator>
      <dc:date>2010-11-08T13:21:35Z</dc:date>
    </item>
  </channel>
</rss>

