<?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: Diff Between vgimport and vgcfgbackup in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-between-vgimport-and-vgcfgbackup/m-p/3435729#M623913</link>
    <description>Vgexport is used to completely remove the /dev/vgxx/* files on a host and also remove the entries in /etc/lvmtab. Vgexport -p (preview mode) is used primarily to create map files for later vgimports on the same or another host. The most important thing to remember about vgexport is that is does not alter the contents of the LVM disks themselves just the data ABOUT the disks on the host computer. Vgimport is used to import these disks on the same or another hosts.&lt;BR /&gt;&lt;BR /&gt;Vgcfgbackup is a command which is automatically run by many LVM commands. It write the LVM data structure information to a regular file. This data only consist of the LVM layout but not about any other contents of the disk. For example, vgcfgbackup does not backup any data stored in an LVOL or a filesystem. Vgcfgrestore can use one of the files created by vgcfgrestore to write the LVM metadata on a new disk. For example, when you are replacing an LVM disk, you can use vfcfgrestore to write all the LVM data to the disk instead of doing a pvcreate.</description>
    <pubDate>Thu, 02 Dec 2004 22:21:35 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2004-12-02T22:21:35Z</dc:date>
    <item>
      <title>Diff Between vgimport and vgcfgbackup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-between-vgimport-and-vgcfgbackup/m-p/3435728#M623912</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I am bit confused on the concept of vgimport/vgexport and vgcfgrestore/vgcfgbackup.&lt;BR /&gt;&lt;BR /&gt;kindly give me the differences between them.&lt;BR /&gt;&lt;BR /&gt;and what scanario we use these commands.. &lt;BR /&gt;it will be a great help for me.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance&lt;BR /&gt;GOvinda G,</description>
      <pubDate>Thu, 02 Dec 2004 21:53:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diff-between-vgimport-and-vgcfgbackup/m-p/3435728#M623912</guid>
      <dc:creator>Anitha_3</dc:creator>
      <dc:date>2004-12-02T21:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: Diff Between vgimport and vgcfgbackup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/diff-between-vgimport-and-vgcfgbackup/m-p/3435729#M623913</link>
      <description>Vgexport is used to completely remove the /dev/vgxx/* files on a host and also remove the entries in /etc/lvmtab. Vgexport -p (preview mode) is used primarily to create map files for later vgimports on the same or another host. The most important thing to remember about vgexport is that is does not alter the contents of the LVM disks themselves just the data ABOUT the disks on the host computer. Vgimport is used to import these disks on the same or another hosts.&lt;BR /&gt;&lt;BR /&gt;Vgcfgbackup is a command which is automatically run by many LVM commands. It write the LVM data structure information to a regular file. This data only consist of the LVM layout but not about any other contents of the disk. For example, vgcfgbackup does not backup any data stored in an LVOL or a filesystem. Vgcfgrestore can use one of the files created by vgcfgrestore to write the LVM metadata on a new disk. For example, when you are replacing an LVM disk, you can use vfcfgrestore to write all the LVM data to the disk instead of doing a pvcreate.</description>
      <pubDate>Thu, 02 Dec 2004 22:21:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/diff-between-vgimport-and-vgcfgbackup/m-p/3435729#M623913</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-12-02T22:21:35Z</dc:date>
    </item>
  </channel>
</rss>

