<?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 Mirror Synchronization in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472035#M555477</link>
    <description>Thanks for your answers. My question doesn't have to do with BDRA resynchronization, I know LVs are the objects getting in synch.&lt;BR /&gt;&lt;BR /&gt;My question has to do with what drive in this situation becomes the master copy for synchronizing the LVs using the default mirror policies?&lt;BR /&gt;&lt;BR /&gt;Does the primary boot disk always become the master in a two-way boot mirror regardless like in this case it contains a slightly old representation of the data?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Manuel</description>
    <pubDate>Mon, 03 Aug 2009 14:52:51 GMT</pubDate>
    <dc:creator>Manuel Urena</dc:creator>
    <dc:date>2009-08-03T14:52:51Z</dc:date>
    <item>
      <title>Boot Mirror Synchronization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472032#M555474</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I've encountered an interesting scenario while doing some experimentation on a Test System.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The system is an RP7400 and this is the sequence of events:&lt;BR /&gt;&lt;BR /&gt;- The system has two internal mirrored boot disks in vg00.&lt;BR /&gt;- I shut the system down took out the primary boot disk and replaced it with a new drive.&lt;BR /&gt;- Powered the system back on and because the primary boot disk is a new drive the system booted off the alternate bootpath.&lt;BR /&gt;- I proceeded to resynchronize vg00 (vgcfgrestore, mkboot the new drive... etc..)&lt;BR /&gt;- Then to test if everything was fine I rebooted the system again, now the system booted off the primary boot disk (which had the new resynchronized disk).&lt;BR /&gt;- Then I shut the system down again and then I replaced the new drive (primary boot disk) with the old drive I took out at the very beginning.&lt;BR /&gt;&lt;BR /&gt;I noticed the system booting off the old drive without too much issues (The system printed "Resynchronized volume group /dev/vg00" during boot time) and there doesn't seem to be any stale PEs at the moment. But I kept receiving VXFS errors on the syslog.&lt;BR /&gt;&lt;BR /&gt;What is the strategy that Mirror/UX uses to resynchronize disks in this case? Which drive is used as the master copy?&lt;BR /&gt;&lt;BR /&gt;I am afraid that now that the spare drive has boot files and a BDRA it may cause issues if I use it as a replacement in a production system.&lt;BR /&gt;&lt;BR /&gt;Thanks for your help,&lt;BR /&gt;&lt;BR /&gt;Manuel&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Aug 2009 14:35:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472032#M555474</guid>
      <dc:creator>Manuel Urena</dc:creator>
      <dc:date>2009-08-03T14:35:12Z</dc:date>
    </item>
    <item>
      <title>Re: Boot Mirror Synchronization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472033#M555475</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;The mirror /UX never synchronise the disks. It will synchronise the LV. &lt;BR /&gt;&lt;BR /&gt;PVRA is never synchronised.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sooraj</description>
      <pubDate>Mon, 03 Aug 2009 14:44:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472033#M555475</guid>
      <dc:creator>SoorajCleris</dc:creator>
      <dc:date>2009-08-03T14:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Boot Mirror Synchronization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472034#M555476</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;There are mirror consistancy and recovery policies for this. And again you may try to run vgsynch and lvsynch manually also.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sooraj&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Aug 2009 14:46:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472034#M555476</guid>
      <dc:creator>SoorajCleris</dc:creator>
      <dc:date>2009-08-03T14:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: Boot Mirror Synchronization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472035#M555477</link>
      <description>Thanks for your answers. My question doesn't have to do with BDRA resynchronization, I know LVs are the objects getting in synch.&lt;BR /&gt;&lt;BR /&gt;My question has to do with what drive in this situation becomes the master copy for synchronizing the LVs using the default mirror policies?&lt;BR /&gt;&lt;BR /&gt;Does the primary boot disk always become the master in a two-way boot mirror regardless like in this case it contains a slightly old representation of the data?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Manuel</description>
      <pubDate>Mon, 03 Aug 2009 14:52:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472035#M555477</guid>
      <dc:creator>Manuel Urena</dc:creator>
      <dc:date>2009-08-03T14:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: Boot Mirror Synchronization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472036#M555478</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;For finding out why the system booted from the alternate boot path first time, you may check the syslog ,dmesg.But unfortunatly I think you have restarted the system too many times so I dont think your OLD syslog will be there. &lt;BR /&gt;&lt;BR /&gt;Still as it booted again from the same disk, that disk may be giving intermitted problem.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sooraj</description>
      <pubDate>Mon, 03 Aug 2009 14:57:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472036#M555478</guid>
      <dc:creator>SoorajCleris</dc:creator>
      <dc:date>2009-08-03T14:57:01Z</dc:date>
    </item>
    <item>
      <title>Re: Boot Mirror Synchronization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472037#M555479</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;from my understanding the disk booted is the 'master' as you call it. this then updates the alt disk&lt;BR /&gt;&lt;BR /&gt;what you have done would not normally be done, but you have probably updated the old alt with info from the old primary disk.&lt;BR /&gt;&lt;BR /&gt;effectively going backwards?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Andy&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Aug 2009 21:22:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-mirror-synchronization/m-p/4472037#M555479</guid>
      <dc:creator>Andrew Rutter</dc:creator>
      <dc:date>2009-08-04T21:22:57Z</dc:date>
    </item>
  </channel>
</rss>

