<?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: Volume group considerations in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753246#M784495</link>
    <description>&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Volume groups are extended by adding one or more physical volumes (disks)&lt;BR /&gt;&lt;BR /&gt;After the physical volumes have been successfully added to the volume&lt;BR /&gt;group, the disk space they contain can be allocated to logical&lt;BR /&gt;volumes. The LVs can be existing and you can increase the SIZE or you can create new LVs also.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 17 Mar 2006 03:20:55 GMT</pubDate>
    <dc:creator>Sivakumar TS</dc:creator>
    <dc:date>2006-03-17T03:20:55Z</dc:date>
    <item>
      <title>Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753243#M784492</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What are the reasons of extending volume group?  &lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Kenrick</description>
      <pubDate>Fri, 17 Mar 2006 02:36:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753243#M784492</guid>
      <dc:creator>Kenrick Sy</dc:creator>
      <dc:date>2006-03-17T02:36:56Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753244#M784493</link>
      <description>Hi&lt;BR /&gt;this operation is performed for example to add mirror devices or extend volume group capacity. &lt;BR /&gt;&lt;BR /&gt;Have a look at Â§6 "Administering a System:&lt;BR /&gt;Managing Disks and Files" on &lt;A href="http://docs.hp.com/en/B2355-90950/B2355-90950.pdf" target="_blank"&gt;http://docs.hp.com/en/B2355-90950/B2355-90950.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 17 Mar 2006 02:49:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753244#M784493</guid>
      <dc:creator>Antonio Cardoso_1</dc:creator>
      <dc:date>2006-03-17T02:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753245#M784494</link>
      <description>To allocate additional physical volume to get more disk space. Read vgextend man page for good documentation.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu</description>
      <pubDate>Fri, 17 Mar 2006 02:49:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753245#M784494</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-03-17T02:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753246#M784495</link>
      <description>&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Volume groups are extended by adding one or more physical volumes (disks)&lt;BR /&gt;&lt;BR /&gt;After the physical volumes have been successfully added to the volume&lt;BR /&gt;group, the disk space they contain can be allocated to logical&lt;BR /&gt;volumes. The LVs can be existing and you can increase the SIZE or you can create new LVs also.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 17 Mar 2006 03:20:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753246#M784495</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2006-03-17T03:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753247#M784496</link>
      <description>Thanks for all your reply.  &lt;BR /&gt;&lt;BR /&gt;What are the reasons of configuring additional volume group?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Kenrick</description>
      <pubDate>Fri, 17 Mar 2006 03:48:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753247#M784496</guid>
      <dc:creator>Kenrick Sy</dc:creator>
      <dc:date>2006-03-17T03:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753248#M784497</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Configuring multiple volume groups provides you ease of administration. You can have seperate VGs for different applications or for different  type of data within one application itself.&lt;BR /&gt;&lt;BR /&gt;A major advantage also will be if there is some   difficult times and you need to restore backup, then restoring a small VG will be fast as compared to the large ones.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Fri, 17 Mar 2006 03:53:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753248#M784497</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2006-03-17T03:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753249#M784498</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;it all depends upon the system requirements.&lt;BR /&gt;&lt;BR /&gt;it could be you need specific vg's/lvol's for certain apps or databases.&lt;BR /&gt;&lt;BR /&gt;you may just want an easier way for adding more disk space.&lt;BR /&gt;&lt;BR /&gt;it could be for easier disk and file management&lt;BR /&gt;&lt;BR /&gt;it could also be to make backups easier, specifying just one vg, rather than all vg's&lt;BR /&gt;&lt;BR /&gt;Many reasons, but depends upon what you want to achieve.&lt;BR /&gt;&lt;BR /&gt;if you want to learn more read the links already provided on disk and file management.&lt;BR /&gt;&lt;BR /&gt;Andy&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 17 Mar 2006 04:00:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753249#M784498</guid>
      <dc:creator>Andrew Rutter</dc:creator>
      <dc:date>2006-03-17T04:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753250#M784499</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;   One of the most important factor is in Cluster environment. One of the attribute of the Cluster package is it's VG. We tend to create  one VG per package. In doing so, the package switch can be independent of other packages. If the packages would have shared the same VG, it becomes inevitable that all the packages sharing the same VG, be switched simultaneosly. So in clustered environment, it is more flexible having multiple VG's, one dedicated to each package.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Senthil Kumar .A</description>
      <pubDate>Fri, 17 Mar 2006 04:03:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753250#M784499</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2006-03-17T04:03:39Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753251#M784500</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;VG - LVM can achieve four important advantages over raw physical partitions:&lt;BR /&gt;&lt;BR /&gt;01. Logical volumes can be resized while they are mounted and accessible by the database or file system.&lt;BR /&gt;&lt;BR /&gt;02. Data from one (potentially faulty or damaged) physical device may be relocated to another device that is newer, faster or more resilient, while the original volume remains online and accessible &lt;BR /&gt;&lt;BR /&gt;03. Logical volumes can be constructed by aggregating physical devices to increase performance (via disk striping) or redundancy (via disk mirroring and I/O multipathing) &lt;BR /&gt;&lt;BR /&gt;04. Logical volume snapshots can be created to represent the exact state of the volume at a certain point-in-time, allowing accurate backups to proceed simultaneously with regular system operation &lt;BR /&gt;&lt;BR /&gt;rgds,&lt;BR /&gt;&lt;BR /&gt;Subbu.&lt;BR /&gt;</description>
      <pubDate>Fri, 17 Mar 2006 05:17:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753251#M784500</guid>
      <dc:creator>Subramaniyan.S</dc:creator>
      <dc:date>2006-03-17T05:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753252#M784501</link>
      <description>hello,&lt;BR /&gt;&lt;BR /&gt;Look at this thread :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=993422" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=993422&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;my small contibution should be according to  backup, when you want to optimize the access on tape. We have seen that on an application like Legato networker it's better to backup 10 lvols of 16 Go than a big one of 160 Go. You can then do parallel writing on drives and save a lot of time..&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Pat</description>
      <pubDate>Fri, 17 Mar 2006 07:10:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753252#M784501</guid>
      <dc:creator>Patrice Le Guyader</dc:creator>
      <dc:date>2006-03-17T07:10:47Z</dc:date>
    </item>
    <item>
      <title>Re: Volume group considerations</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753253#M784502</link>
      <description>Well, in plain words u extend a volume group to get more space.&lt;BR /&gt;U add another disk to ur volume group and then u keep on adding them as u want more disk space. &lt;BR /&gt;Ur volume group first spans on some disks, then u want to mirror them in a disk array using xp512. So, the volume group is what disks belong to, they are referred to not by their names but by their volume group name. Like c1t2d9 and c1t2d7 belong to volume group vg02. And thats just the beginning of the story........</description>
      <pubDate>Mon, 20 Mar 2006 16:20:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-considerations/m-p/3753253#M784502</guid>
      <dc:creator>khilari</dc:creator>
      <dc:date>2006-03-20T16:20:27Z</dc:date>
    </item>
  </channel>
</rss>

