<?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 Shadowset Member Problem in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212467#M26927</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have rx3600 attached with MSA30 via SCSI Cables. O/S is installed on MSA on DKA0 Disk. O/S is not loading and gives error  &lt;BR /&gt; &lt;BR /&gt;%SYSBOOT-F-LDFAIL, unable to load SYS$PUBLIC_VECTORS.EXE, status = 0000008C&lt;BR /&gt; &lt;BR /&gt;There is a mirror disk DKD0, I boot the server from there using fs4: filesystem &lt;BR /&gt;through EFI Shell. Server booted successfully. &lt;BR /&gt; &lt;BR /&gt;My Questions is that did both DKA0 and DKD0 are synchronized or not. If I boot the server from (DKA0 / fs0:) did it boot successfully or not. Mean, both DKA0 or DKD0 are synchronized now or not.</description>
    <pubDate>Thu, 03 Dec 2009 12:25:41 GMT</pubDate>
    <dc:creator>Farooq Saleem</dc:creator>
    <dc:date>2009-12-03T12:25:41Z</dc:date>
    <item>
      <title>Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212467#M26927</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have rx3600 attached with MSA30 via SCSI Cables. O/S is installed on MSA on DKA0 Disk. O/S is not loading and gives error  &lt;BR /&gt; &lt;BR /&gt;%SYSBOOT-F-LDFAIL, unable to load SYS$PUBLIC_VECTORS.EXE, status = 0000008C&lt;BR /&gt; &lt;BR /&gt;There is a mirror disk DKD0, I boot the server from there using fs4: filesystem &lt;BR /&gt;through EFI Shell. Server booted successfully. &lt;BR /&gt; &lt;BR /&gt;My Questions is that did both DKA0 and DKD0 are synchronized or not. If I boot the server from (DKA0 / fs0:) did it boot successfully or not. Mean, both DKA0 or DKD0 are synchronized now or not.</description>
      <pubDate>Thu, 03 Dec 2009 12:25:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212467#M26927</guid>
      <dc:creator>Farooq Saleem</dc:creator>
      <dc:date>2009-12-03T12:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212468#M26928</link>
      <description>$ exit (%x8C)&lt;BR /&gt;%SYSTEM-F-DRVERR, fatal drive error&lt;BR /&gt;&lt;BR /&gt;It appears that DKA0 is faulty. I would assume it has been dropped from the shadowset.</description>
      <pubDate>Thu, 03 Dec 2009 13:17:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212468#M26928</guid>
      <dc:creator>Richard Brodie_1</dc:creator>
      <dc:date>2009-12-03T13:17:51Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212469#M26929</link>
      <description>DKA0 and DKD0 both are member of shadow set</description>
      <pubDate>Thu, 03 Dec 2009 13:52:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212469#M26929</guid>
      <dc:creator>Farooq Saleem</dc:creator>
      <dc:date>2009-12-03T13:52:59Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212470#M26930</link>
      <description>Further more, If i wants to remove DKA0 from the shadow set, then what command should i run.&lt;BR /&gt;&lt;BR /&gt;My purpose is that, first i remove the DKA0 from the shadow set and the make it member of shadow set again, so that date from DKD0 copied to DKA0.</description>
      <pubDate>Thu, 03 Dec 2009 13:55:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212470#M26930</guid>
      <dc:creator>Farooq Saleem</dc:creator>
      <dc:date>2009-12-03T13:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212471#M26931</link>
      <description>Farooq,&lt;BR /&gt;&lt;BR /&gt;What do you mean by "There is a mirror disk DKD0"&lt;BR /&gt;&lt;BR /&gt;Mirror usually means a controller based duplicate (raid 1).  But you are also talking about shadowing, and that usually means host based synchronization of multiple disk copies.&lt;BR /&gt;&lt;BR /&gt;I am a bit hesitant to make any recommendations, because the shadowing question you ask is pretty basic, and doing the wrong thing can do a lot of damage.&lt;BR /&gt;&lt;BR /&gt;You need to provide more info, for example show the output of &lt;BR /&gt;&lt;BR /&gt;$ show device /full dka0&lt;BR /&gt;$ show device /full dkd0&lt;BR /&gt;&lt;BR /&gt;Jon&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Dec 2009 15:01:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212471#M26931</guid>
      <dc:creator>Jon Pinkley</dc:creator>
      <dc:date>2009-12-03T15:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212472#M26932</link>
      <description>What to do?  How does shadowing work?  How to replace a failed disk?  Answers to all these questions and more are available in this document:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/732FINAL/DOCUMENTATION/PDF/aa-pvxmj-te.PDF" target="_blank"&gt;http://h71000.www7.hp.com/doc/732FINAL/DOCUMENTATION/PDF/aa-pvxmj-te.PDF&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;At its simplest (and barring cases where the disk error here is secondary to an error elsewhere in the configuration), you're going to replace the disk, MOUNT it into the shadowset, and wait for shadowing to copy the data over.&lt;BR /&gt;&lt;BR /&gt;The basic command looks something like this:&lt;BR /&gt;&lt;BR /&gt;MOUNT /CONFIRM /SYSTEM DSAu: /SHADOW=($n$DKA0) VolumeLabel&lt;BR /&gt;&lt;BR /&gt;You'll need to customize that command to reflect your local system environment.&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Dec 2009 15:03:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212472#M26932</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-12-03T15:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212473#M26933</link>
      <description>And oh yeah, if you "miss" here and mis-specify a command, you'll clobber your data.&lt;BR /&gt;&lt;BR /&gt;How current are your backups of your disks?</description>
      <pubDate>Thu, 03 Dec 2009 15:05:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212473#M26933</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-12-03T15:05:03Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212474#M26934</link>
      <description>Dear Jon,&lt;BR /&gt;&lt;BR /&gt;My mistake, there is no hardware raid controller. this is host based synchronization or shadowing.</description>
      <pubDate>Thu, 03 Dec 2009 15:14:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212474#M26934</guid>
      <dc:creator>Farooq Saleem</dc:creator>
      <dc:date>2009-12-03T15:14:38Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212475#M26935</link>
      <description>Since this is evidently the system disk, and you claim that DKA0 and DKD0 are in a shadowset, please provide output from:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;$ sho dev/ful sys$sysdevice&lt;BR /&gt;&lt;BR /&gt;$ mcr sysgen show shadow_sys_disk&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Dec 2009 15:27:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212475#M26935</guid>
      <dc:creator>Jon Pinkley</dc:creator>
      <dc:date>2009-12-03T15:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212476#M26936</link>
      <description>If both DKA0 and DKD0 are currently members of the shadowset (as show device sys$sysdevice will show is true or not), then you can use &lt;BR /&gt;&lt;BR /&gt;$ analyze/disk/shadow sys$sysdevice&lt;BR /&gt;&lt;BR /&gt;to see if your disks are consistent.&lt;BR /&gt;&lt;BR /&gt;See help analyze/disk/shadow for a more detailed description, and the shadowing manual (also you need the manual update from 8.2 new features or the HBMM patch for 7.3-2)&lt;BR /&gt;&lt;BR /&gt;Shadowing is can be useful, but like fire, it can do a lot of damange if it isn't treated with respect.  Getting a shadow copy with the wrong master member is non-recoverable (unless you have backups on some other media).</description>
      <pubDate>Thu, 03 Dec 2009 15:39:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212476#M26936</guid>
      <dc:creator>Jon Pinkley</dc:creator>
      <dc:date>2009-12-03T15:39:38Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212477#M26937</link>
      <description>Thankyou Hoff and John for helping me.&lt;BR /&gt;&lt;BR /&gt;Special Thanks to Hoff for sharing such a nice document, it contains answers to all my questions. If it is possible to give more points, i will give you 100.</description>
      <pubDate>Thu, 03 Dec 2009 16:51:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212477#M26937</guid>
      <dc:creator>Farooq Saleem</dc:creator>
      <dc:date>2009-12-03T16:51:15Z</dc:date>
    </item>
    <item>
      <title>Re: Shadowset Member Problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212478#M26938</link>
      <description>I will issue dismount command for DKA0 and then mount it again as shadow set member.</description>
      <pubDate>Thu, 03 Dec 2009 16:54:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/shadowset-member-problem/m-p/5212478#M26938</guid>
      <dc:creator>Farooq Saleem</dc:creator>
      <dc:date>2009-12-03T16:54:03Z</dc:date>
    </item>
  </channel>
</rss>

