<?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 Service Guard &amp;amp; EMC BCV's in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-amp-emc-bcv-s/m-p/2629938#M710355</link>
    <description>I am using EMC's Timefinder software to do backups of an oracle database on a SG cluster. Once the BCV volumes are synchronised with the originals, they are then re-imported onto the cluster by running a vgchange -c n, a vgchgid and then vgimport with a new vg name. My problem is this: If I wish to restore from this copy, what steps do I need to do on the cluster. Once the restore is complete, the volume group ID will be different to the originals (&amp;amp; what's in lvmtab)as we have run a vgchgid.&lt;BR /&gt;&lt;BR /&gt;My thoughts were...&lt;BR /&gt;1. run vgcfgrestore onto the disks once the restore was complete.&lt;BR /&gt;OR&lt;BR /&gt;2. vgexport the original volumes, vgimport using the same names, then vgchange -c y the originals &amp;amp; then vgchgid the BCV's again so the VGID's aren't duplicated once more.&lt;BR /&gt;&lt;BR /&gt;If anyone has experience with this or has any ideas it would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks, Glen.</description>
    <pubDate>Wed, 12 Dec 2001 03:28:45 GMT</pubDate>
    <dc:creator>Glen Hyatt</dc:creator>
    <dc:date>2001-12-12T03:28:45Z</dc:date>
    <item>
      <title>Service Guard &amp; EMC BCV's</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-amp-emc-bcv-s/m-p/2629938#M710355</link>
      <description>I am using EMC's Timefinder software to do backups of an oracle database on a SG cluster. Once the BCV volumes are synchronised with the originals, they are then re-imported onto the cluster by running a vgchange -c n, a vgchgid and then vgimport with a new vg name. My problem is this: If I wish to restore from this copy, what steps do I need to do on the cluster. Once the restore is complete, the volume group ID will be different to the originals (&amp;amp; what's in lvmtab)as we have run a vgchgid.&lt;BR /&gt;&lt;BR /&gt;My thoughts were...&lt;BR /&gt;1. run vgcfgrestore onto the disks once the restore was complete.&lt;BR /&gt;OR&lt;BR /&gt;2. vgexport the original volumes, vgimport using the same names, then vgchange -c y the originals &amp;amp; then vgchgid the BCV's again so the VGID's aren't duplicated once more.&lt;BR /&gt;&lt;BR /&gt;If anyone has experience with this or has any ideas it would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks, Glen.</description>
      <pubDate>Wed, 12 Dec 2001 03:28:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-amp-emc-bcv-s/m-p/2629938#M710355</guid>
      <dc:creator>Glen Hyatt</dc:creator>
      <dc:date>2001-12-12T03:28:45Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard &amp; EMC BCV's</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-amp-emc-bcv-s/m-p/2629939#M710356</link>
      <description>How quick is a 'symmir -restore' command? If you unmount both file systems and perform the restore this way, you can continue to use the Standard Volumes and their BCV in the normal way. EMC have a new set of microcode for the Array that provides mega-quick splits and synchs, and possibly restores.&lt;BR /&gt;&lt;BR /&gt;Are you planning to disassociate the BCVs with the Standard Devices before remounting them?&lt;BR /&gt;&lt;BR /&gt;Personally, the shortest route is to unmount the Standard Volumes and remount the BCV Volumes on the regular mount points (ie leave the Volume Groups as they are). This involves the least number of OS changes, and will make the data on the BCV available to the Application.  You may incur some procedural overhead in this (remember to update the /etc/fstab, and to prevent resynchs while running on the BCV Disks), but this can be scripted fairly easily.&lt;BR /&gt;&lt;BR /&gt;Share and Enjoy! Ian</description>
      <pubDate>Wed, 12 Dec 2001 09:29:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-amp-emc-bcv-s/m-p/2629939#M710356</guid>
      <dc:creator>Ian Dennison_1</dc:creator>
      <dc:date>2001-12-12T09:29:33Z</dc:date>
    </item>
    <item>
      <title>Re: Service Guard &amp; EMC BCV's</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-amp-emc-bcv-s/m-p/2629940#M710357</link>
      <description>hi,&lt;BR /&gt;Once you are done restoring from the BCVs, you unmount all the fs and deactivate the volume groups existing on BCVs. Re-establish the BCVs with Standard. As part of re-establishing, the changed blocks on BCVs ( due to vgchgid and vgimport with different name)are dumped with the content from standard device. BCV device are also written back all the blocks which changed on the std since the BCV was split.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;pash&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Jun 2002 01:46:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-amp-emc-bcv-s/m-p/2629940#M710357</guid>
      <dc:creator>Pashupati Kumar</dc:creator>
      <dc:date>2002-06-28T01:46:31Z</dc:date>
    </item>
  </channel>
</rss>

